[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_49262 ]
Peter Lynch commented on MNG-678:
---------------------------------
Certain parts of this issue are similar to one I am experiencing, although the
resulting error message is a little different. I successfully deployed the
xmlbeans plugin to an internal maven repo that sits on a Linux Redhat9 box. It
works the first time no problem. Then executing the same 'mvn deploy' command
with the same configuration again, to the same repo results in the following
failure :
[INFO]
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
----------------------------------------------------------------------------
[INFO] Error deploying artifact: Did receive proper ACK: '1'
[INFO]
----------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: Did receive proper ACK: '1'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:544)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying
artifact: Did receive proper ACK: '1'
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:159)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
... 16 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: Did receive proper ACK: '1'
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:148)
... 18 more
Caused by: org.apache.maven.wagon.TransferFailedException: Did receive proper
ACK: '1'
at
org.apache.maven.wagon.providers.ssh.ScpWagon.checkAck(ScpWagon.java:203)
at org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:140)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
... 19 more
[INFO]
----------------------------------------------------------------------------
IF I go and delete the deployed artifact in the remote repo and try again it
works. If I then try to redeploy it fails as above again. If the same artifact
is present it will continually fail. This is using maven 2.0 final.
> scp intermittently failing deploying artifact
> ---------------------------------------------
>
> Key: MNG-678
> URL: http://jira.codehaus.org/browse/MNG-678
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Versions: 2.0-alpha-3
> Environment: JDK 1.5, Red Hat 9
> Reporter: Joe Futrelle
> Assignee: Brett Porter
> Fix For: 2.0.1
>
>
> Some of the time, deploying artifacts fails during the scp transfer. The
> bottom of the stack trace is reproduced below. If I run the m2 deploy enough
> times, it succeeds; not sure why.
> This is not an unknown issue with Jsch; apparently client code can cause
> behavior like this if it doesn't dispose of connections properly. Possibly a
> plugin that's runs before the deploy phase is messing up the connection state
> somehow?
> Caused by: org.apache.maven.wagon.TransferFailedException: Error occured
> while deploying 'ncsa/gsbt/1.0-SNAPSHOT/gsbt-1.0-20050728.190330-38.pom.sha1'
> to remote repository: scp://chasm.ncsa.uiuc.edu//home/futrelle/m2/repository
> at
> org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:331)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:167)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:91)
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:73)
> ... 17 more
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Channel.connect(Unknown Source)
> at
> org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:271)
> ... 20 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
