Artifactory Error Writing To Server
threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ artifactory server requirements IOException: error writing to server Hi all, hoping someone
Artifactory Server Name
can help shed some light on this problem I'm having. We use Ant and artifactory symbol server Ivy to publish build artifacts to Artifactory, with this stuff being run on a Hudson server. We have about 30 projects that are
Artifactory Connection Reset
built and published throughout the day. But for the past week or two, I've been getting intermittent errors when Ivy tries to publish the artifacts up to the Artifactory server. It's usually (but not always) the same project which fails, and it doesn't always fail. Most java.io.ioexception error writing to server of the time, I can log into Hudson immediately after seeing it fail, manually kick off another build and it works fine. The error that is reported by Ivy looks like this: java.io.IOException: Error writing to server at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:583) at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:595) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1198) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379) at org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:225) at org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82) at org.apache.ivy.util.FileUtil.copy(FileUtil.java:148) at org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:84) at org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130) at org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:234) at org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:216) at org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:281) at org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:260) at org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:172) ... FWIW, the project that fails most often is the one that
Repository Component/s: None Affects Version/s: 2.3.2 Fix Version/s: None Type: Bug Priority: Normal Reporter: Chad Cotter Assignee: Yossi Shaul Resolution: Won't Fix Votes: 0 Labels: None Attachments: pom.xml settings.xml Description "Allow Anonymous Access" general setting causes maven to NOT send user credentials when uploading artifacts. This is a problem because we would like to allow http://forums.jfrog.org/IOException-error-writing-to-server-td6345612.html anonymous users read access to our repo but only allow authenticated users to upload artifacts. Everything works fine if I remove anonymous access to just our single repo, but this is not a feasible solution in our environment. settings.xml: repo-release ... ... https://www.jfrog.com/jira/si/jira.issueviews:issue-html/RTFACT-4120/RTFACT-4120.html 600000 repo-snapshot ... ... 600000 Error message: Using Wagon implementation lightweight from default mapping for protocol https [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] User-Agent configuration found. [DEBUG] Connecting to repository: 'apollo-snapshot' with url: 'https://artifactory.apollogrp.edu/artifactory/libs-snapshot-local/'. [DEBUG] Using Wagon implementation lightweight from default mapping for protocol https [INFO] repository metadata for: 'snapshot edu.apollogrp.community.jive:web:1.1.18-SNAPSHOT' could not be found on repository: apollo-snapshot, so will be created [DEBUG] Using Wagon implementation lightweight from default mapping for protocol https [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] User-Agent configuration found. [DEBUG] not adding permissions to wagon connection Uploading: https://artifactory.apollogrp.edu/artifactory/libs-snapshot-local//edu/apollogrp/community/jive/web/1.1.18-SNAPSHOT/web-1.1.18-20110407.234817-1.war [DEBUG] Error writing to server java.io.IOException: Error writing to server at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:468) at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:480) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1070) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318) at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185) at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon
the JDK URL classes for uploading). As an alternative, you can https://www.mail-archive.com/artifactory-users@lists.sourceforge.net/msg01600.html publish to Artifactory directly from Hudson (or better, Jenkins :) https://www.mail-archive.com/artifactory-users@lists.sourceforge.net/msg01606.html using the Jenkins Artifactory plugin + get all the other benefits of using the build integration features of Artifactory for Ivy, such as: avoiding partial publishing, collecting traceable build info, etc. On Mon, May 9, 2011 at 11:34 PM, error writing Phillip Rhodes wrote: > Hi all, hoping someone can help shed some light on this problem I'm having. > We use Ant and Ivy to publish build artifacts to Artifactory, with this > stuff being run on a Hudson server. We have about 30 projects that are > error writing to built and published throughout the day. But for the past week or two, I've > been getting intermittent errors when Ivy tries to publish the artifacts up > to the Artifactory server. It's usually (but not always) the same project > which fails, and it doesn't always fail. Most of the time, I can log into > Hudson immediately after seeing it fail, manually kick off another build and > it works fine. > > The error that is reported by Ivy looks like this: > > java.io.IOException: Error writing to server > at > sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:583) > at > sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:595) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1198) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379) > at > org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:225) > at > org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82) > at org.apache.ivy.util.FileUtil.copy(FileUtil.java:148) > at > org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:84) > at > org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:234) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:216) > at > org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:281) > at > org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:260) >
files > (related to the use of the JDK URL classes for uploading). > As an alternative, you can publish to Artifactory directly from Hudson (or > better, Jenkins :) using the Jenkins Artifactory plugin ci.org/display/JENKINS/Artifactory+Plugin> + get all the other benefits of > using the build integration Some digging around turned up the suggestion that configuring Ivy to use Commons HttpClient might help, so I did that, and I do find that the issue is cropping up less frequently now. It has not gone away entirely however. HttpClient does at least expose the underlying socketexception however, which is: java.net.SocketException: Connection reset by peer: socket write error I'm not a TCP guru, but I understand that the "connection reset by peer" bit is telling me that the Artifactory server has closed its side of the socket connection, while Ivy is still writing. Does anyone know if there's anything that can be done to improve this? Is there a timeout/ buffer size setting on the server side that's configurable, or perhaps a Java system setting that would affect this? Any other thoughts or suggestions? Thanks, Phillip Rhodes Redwood Software ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Artifactory-users mailing list Artifactory-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/artifactory-users Previous message View by thread View by date Next message [Artifactory-users] IOException: error writing to server Phillip Rhodes Re: [Artifactory-users] IOException: error writing to ... Yoav Landman Re: [Artifactory-users] IOException: error writing... Phillip Rhodes Re: [Artifactory-users] IOException: error wri... Car