[ 
http://jira.codehaus.org/browse/MDEPLOY-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215532#action_215532
 ] 

Benjamin Bentmann commented on MDEPLOY-120:
-------------------------------------------

bq. it appears that Maven 2.2.0 is trying to upload data beyond the end of the 
file.
When authentication is involved, the data is effectively sent twice, first 
without and second with credentials. This makes the progress meter show upload 
of twice the file size.

> Unable to deploy large file into Nexus 1.5.0 from Windows Server 2003 
> Enterprise
> --------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-120
>                 URL: http://jira.codehaus.org/browse/MDEPLOY-120
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Bug
>          Components: deploy:deploy-file
>    Affects Versions: 2.5
>         Environment: Nexus Server:
> Nexus 1.5.0 OSS running on Linux 2.6.9-42.0.10.ELsmp #1 SMP Fri Feb 16 
> 17:17:21 EST 2007 i686 i686 i386 GNU/Linux
> Maven client OS:
> Windows Server 2003 Enterprise with all security updates applied
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)
> Output from mvn -v:
> Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
> Java version: 1.6.0_14
> Java home: D:\jdk1.6.0_14\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 2003" version: "5.2" arch: "x86" Family: "windows"
>            Reporter: Keith Wedinger
>            Priority: Blocker
>         Attachments: mavenuploadfiles.zip
>
>
> Attached to this issue are the files I am using to deploy a large file to my 
> Nexus repository.  The file being deployed is an EXE file whose size is 
> 22,413,688 bytes.  During deployment, the upload times out after several 
> minutes with the stack trace below which I captured by running mvn with the 
> -X argument.  Deploying smaller files does appear to work but I have not done 
> enough testing to determine the threshold when deployment fails.  There is no 
> proxy between the client OS and the Nexus server.  The steps to reproduce 
> this on my system are below.
> 1.  Download and unzip mavenuploadfiles.zip onto a Windows Server 2003 
> Enterprise system.
> 2.  Run mavenupload.cmd to get the syntax for this command script.  The 
> syntax message is self-explanatory.
> The ZIP file also contains my copy of settings.xml, the Maven settings file I 
> am using.
> If you believe this is a Nexus 1.5.0 issue, please let me know and I will 
> open the appropriate bug for Nexus OSS 1.5.0.
> STACK TRACE BEGIN:
> ------------------
> Error writing to server
> [INFO] 
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying 
> artifact: Error transferring file
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>       at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>       at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>       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:592)
>       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: Error transferring file
>       at 
> org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:240)
>       at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>       ... 17 more
> Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: 
> Error deploying artifact: Error transferring file
>       at 
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121)
>       at 
> org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:236)
>       ... 19 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Error transferring 
> file
>       at 
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:213)
>       at 
> org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:413)
>       at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392)
>       at 
> org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365)
>       at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
>       at 
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317)
>       at 
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227)
>       at 
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
>       ... 20 more
> Caused by: java.io.IOException: Error writing to server
>       at 
> sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:438)
>       at 
> sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:450)
>       at 
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:981)
>       at 
> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
>       at 
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
>       ... 27 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

        

Reply via email to