[ 
https://jira.codehaus.org/browse/MDEPLOY-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332887#comment-332887
 ] 

Jigar Joshi commented on MDEPLOY-167:
-------------------------------------

not a deploy plugin issue, closing it

Going to assume that nexus web end point manages synchronization to write to 
disk (until it fails again)

Thanks!
                
> Occasionally deploy fails "Failed to deploy metadata: Could not transfer 
> metadata "
> -----------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-167
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-167
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>          Components: deploy:deploy
>    Affects Versions: 2.7
>         Environment: maven 3.1-SNAPSHOT at revision:1521204, nexus-2.6.2-01, 
> jdk 1.6.37
>            Reporter: Jigar Joshi
>            Priority: Minor
>
> Maven deploy fails occasionally with following error message
> {code}
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to deploy 
> metadata: Could not transfer metadata 
> {code}
>  - user has permission to connect to nexus with scp all the time
>  - nexus is running all the time
>  - nexus isn't running out of disk space
> According to this thread 
> :http://mail-archives.apache.org/mod_mbox/maven-users/201101.mbox/%3c1294417752462-3332094.p...@n5.nabble.com%3E
> It could be related to legacy format of metadata, which could be the case, 
> tried passing
> {code}
> -Dmaven.metadata.legacy=true
> {code}
> still it fails occasionally
> {code}
> Caused by: org.apache.maven.wagon.TransferFailedException: Error occurred 
> while deploying '<removed>/maven-metadata.xml' to remote repository: 
> scp://<removed>/home/<removed>/sonatype-work/nexus/storage/snapshots: 
> Unexpected end of data
> build 13-Sep-2013 13:17:15            at 
> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon.handleIOException(ScpWagon.java:416)
> build 13-Sep-2013 13:17:15            at 
> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon.finishPutTransfer(ScpWagon.java:108)
> build 13-Sep-2013 13:17:15            at 
> org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:423)
> build 13-Sep-2013 13:17:15            at 
> org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:402)
> build 13-Sep-2013 13:17:15            at 
> org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:376)
> build 13-Sep-2013 13:17:15            at 
> org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
> build 13-Sep-2013 13:17:15            at 
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:811)
> build 13-Sep-2013 13:17:15            ... 22 more
> build 13-Sep-2013 13:17:15    Caused by: java.io.IOException: Unexpected end 
> of data
> build 13-Sep-2013 13:17:15            at 
> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon.checkAck(ScpWagon.java:130)
> build 13-Sep-2013 13:17:15            at 
> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon.finishPutTransfer(ScpWagon.java:100)
> {code}
>  
> (some of) other posts about this issue:
>  - 
> http://forums.jfrog.org/Maven-fails-to-deploy-occationally-Could-not-transfer-metadata-quot-Access-denied-to-quot-error-td6713183.html
>  - http://mojo.10943.n7.nabble.com/Problem-to-release-perform-td40059.html
> I would be ready to provide more helpful information if required

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to