You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Dan Armbrust <da...@gmail.com> on 2011/05/08 17:22:04 UTC
Re: Uploading large files?
Hmm. Back to the the original problem of my thread.
Now, I'm trying to upload a 700 MB file through the web form, and all I get is:
Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.
Part way through the transfer.
Are their any other hidden limits that i need to adjust?
I'm rather new to the whole maven world... but hasn't anybody ever
tried this with large files before? Is my use case that unusual?
Thanks,
Dan
Re: Uploading large files?
Posted by Dan Armbrust <da...@gmail.com>.
On Tue, Aug 2, 2011 at 12:55 PM, Not Zippy <no...@gmail.com> wrote:
> Generally there is a cap to the amount of data that is allowed to be
> posted (via http) to a server. For example tomcat has maxSavePostSize
> (http://tomcat.apache.org/tomcat-5.5-doc/config/http.html)
>
> Nz
Have already been through that battle :)
I'm successfully posting 1GB + files through the web interface.
Perhaps there is something similar for webdav... but that would be a
strange limitation for webdav to have, since it is intended to handle
files.
Re: Uploading large files?
Posted by Not Zippy <no...@gmail.com>.
Generally there is a cap to the amount of data that is allowed to be
posted (via http) to a server. For example tomcat has maxSavePostSize
(http://tomcat.apache.org/tomcat-5.5-doc/config/http.html)
Nz
On Tue, Aug 2, 2011 at 12:49 PM, Dan Armbrust
<da...@gmail.com> wrote:
> Well, this is interesting.
>
> A little background.
> I have an admin account on the archiva server. The password is
> "expired", but I don't want to change it. So I haven't changed it,
> and I ignore the change requests. It still lets me use the GUI. As a
> side note, Archiva really shouldn't be enforcing arbitrary password
> policies, IMHO. Forced password changes are silly even in high
> security places. And this isn't high security....
>
> Anyway. When I was trying to use maven to upload before, it was
> giving me a 401 error. I (correctly) assumed that it was doing this
> because my password was expired.
>
> So I created a new account. I made it a "Repository-Manager".
>
> And then I tried uploading small files using this new account, and it
> worked fine.
>
> However, when I try to upload a large file, I get the broken pipe at
> an arbitrary point, and the server reports:
>
> myip - - [02/Aug/2011:17:02:27 +0000] "PUT
> /archiva/repository/apelon-data//com/apelon/va/ihtsdo/wb/snomed/snomed-data/2010.07.31-build1-sct-en-vtmvmp-non-human-2-versioni-junk/snomed-data-2010.07.31-build1-sct-en-vtmvmp-non-human-2-versioni-junk.zip
> HTTP/1.1" 401 0 "-" "Apache-Maven/2.2 (Java 1.6.0_25; Linux
> 2.6.31-23-generic) maven-artifact/2.2.1"
>
> And also:
> 2011-08-02 13:02:27,500 [btpool0-39] INFO
> org.apache.maven.archiva.security.ArchivaServletAuthenticator -
> Authorization Denied
> [ip=myip,permission=archiva-upload-repository,repo=apelon-data] : no
> matching permissions
>
> So, somewhere along the way when uploading a large file it would
> appear Archiva gets confused and loses the credentials.
>
> Probably not related, but I have also noticed that the GUI upload
> suffers from a design flaw with large uploads here too - when the
> upload takes longer than the default session timeout, the session
> times out before the upload completes. The upload will be processed
> successfully - but the user doesn't know this - because the update
> never comes back to the browser saying that it finished. In fact, the
> browser stays stuck, waiting for the page to finish loading forever...
> which leads me to suspect that you may have a socket leak on your end
> when you expire a session while a request is still being processed.
>
Re: Uploading large files?
Posted by Brett Porter <br...@apache.org>.
On 30/08/2011, at 7:12 AM, Dan Armbrust wrote:
> As time goes on, the files I'm trying to upload to archiva only get bigger.
>
> I seemed to have reached a point (1.1 GB) where nothing works. The
> HTTP upload has quit working for me (though, I suppose it is possible
> I hit that hard coded limit again, I'm not sure what the sysadmin set
> it to when I had them change it)... and webdav doesn't really work at
> all for anything beyond small files.
>
> It would appear I'm going to have to try to trick maven into hosting
> the file.... I was thinking something along the lines of:
>
> 1) Upload a tiny file using the correct name / path / version etc.
>
> 2) find the file on the host OS and manually replace the file on disk
> with the correct file.
>
> 3) delete all of the generated checksum files
>
> 4) ??
There's no need to do all that - if you can get the file into the right location on the host OS then Archiva will find it on its next scan, and can be configured to repair the metadata. But probably the best thing to do is get this in a way that Maven can still do it:
1) run the build on the repository server
2) a mounted filesystem it can deploy to
3) deploy over scp/sftp
I still believe the http should work, but it's hard to diagnose this way, as you've said - and at that size you definitely want it deploying from an extremely close network location anyway.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: Uploading large files?
Posted by Dan Armbrust <da...@gmail.com>.
As time goes on, the files I'm trying to upload to archiva only get bigger.
I seemed to have reached a point (1.1 GB) where nothing works. The
HTTP upload has quit working for me (though, I suppose it is possible
I hit that hard coded limit again, I'm not sure what the sysadmin set
it to when I had them change it)... and webdav doesn't really work at
all for anything beyond small files.
It would appear I'm going to have to try to trick maven into hosting
the file.... I was thinking something along the lines of:
1) Upload a tiny file using the correct name / path / version etc.
2) find the file on the host OS and manually replace the file on disk
with the correct file.
3) delete all of the generated checksum files
4) ??
Anyone have any ideas what else I may need to finish tricking maven
into working?
Unfortunately, it is difficult for me to just try stuff, as I don't
have direct access to the machine in question, and am going to have to
proxy all of these instructions through to the sys admin behind the
firewall (ack)
Dan
Re: Uploading large files?
Posted by Brett Porter <br...@apache.org>.
On 03/08/2011, at 3:49 AM, Dan Armbrust wrote:
> However, when I try to upload a large file, I get the broken pipe at
> an arbitrary point, and the server reports:
>
> myip - - [02/Aug/2011:17:02:27 +0000] "PUT
> /archiva/repository/apelon-data//com/apelon/va/ihtsdo/wb/snomed/snomed-data/2010.07.31-build1-sct-en-vtmvmp-non-human-2-versioni-junk/snomed-data-2010.07.31-build1-sct-en-vtmvmp-non-human-2-versioni-junk.zip
> HTTP/1.1" 401 0 "-" "Apache-Maven/2.2 (Java 1.6.0_25; Linux
> 2.6.31-23-generic) maven-artifact/2.2.1"
>
> And also:
> 2011-08-02 13:02:27,500 [btpool0-39] INFO
> org.apache.maven.archiva.security.ArchivaServletAuthenticator -
> Authorization Denied
> [ip=myip,permission=archiva-upload-repository,repo=apelon-data] : no
> matching permissions
This is likely not what it looks like - there's usually one of these first as the request is sent without credentials, then in response to the 401 the credentials are sent. There's some discussion about using preemptive auth here: http://jira.codehaus.org/browse/WAGON-277, and there's been a bit of recent work on Wagon that is not yet included in released Maven.
The other deployment method you can try is dav:http://.… with an extension added for wagon-webdav-jackrabbit 1.0.
Regards,
Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: Uploading large files?
Posted by Dan Armbrust <da...@gmail.com>.
Well, this is interesting.
A little background.
I have an admin account on the archiva server. The password is
"expired", but I don't want to change it. So I haven't changed it,
and I ignore the change requests. It still lets me use the GUI. As a
side note, Archiva really shouldn't be enforcing arbitrary password
policies, IMHO. Forced password changes are silly even in high
security places. And this isn't high security....
Anyway. When I was trying to use maven to upload before, it was
giving me a 401 error. I (correctly) assumed that it was doing this
because my password was expired.
So I created a new account. I made it a "Repository-Manager".
And then I tried uploading small files using this new account, and it
worked fine.
However, when I try to upload a large file, I get the broken pipe at
an arbitrary point, and the server reports:
myip - - [02/Aug/2011:17:02:27 +0000] "PUT
/archiva/repository/apelon-data//com/apelon/va/ihtsdo/wb/snomed/snomed-data/2010.07.31-build1-sct-en-vtmvmp-non-human-2-versioni-junk/snomed-data-2010.07.31-build1-sct-en-vtmvmp-non-human-2-versioni-junk.zip
HTTP/1.1" 401 0 "-" "Apache-Maven/2.2 (Java 1.6.0_25; Linux
2.6.31-23-generic) maven-artifact/2.2.1"
And also:
2011-08-02 13:02:27,500 [btpool0-39] INFO
org.apache.maven.archiva.security.ArchivaServletAuthenticator -
Authorization Denied
[ip=myip,permission=archiva-upload-repository,repo=apelon-data] : no
matching permissions
So, somewhere along the way when uploading a large file it would
appear Archiva gets confused and loses the credentials.
Probably not related, but I have also noticed that the GUI upload
suffers from a design flaw with large uploads here too - when the
upload takes longer than the default session timeout, the session
times out before the upload completes. The upload will be processed
successfully - but the user doesn't know this - because the update
never comes back to the browser saying that it finished. In fact, the
browser stays stuck, waiting for the page to finish loading forever...
which leads me to suspect that you may have a socket leak on your end
when you expire a session while a request is still being processed.
Re: Uploading large files?
Posted by Dan Armbrust <da...@gmail.com>.
On Tue, Aug 2, 2011 at 8:59 AM, Brett Porter <br...@apache.org> wrote:
> Can you try using httpclient on the Maven end instead?
>
Hmm, different behavior. When the upload starts, the bit counter
actually works properly now (it doesn't with the default 'wagon' - it
goes way to fast)
But it would appear that somewhere around ~66 MB into the upload I get:
Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500)
Java version: 1.6.0_25
Java home: /opt/Linux/jdk_x64_1.6.0_25/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.31-23-generic" arch: "amd64" Family:
"unix"
[DEBUG] Broken pipe
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon$RequestEntityImplementation.writeRequest(AbstractHttpClientWagon.java:160)
at hidden.org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495)
at hidden.org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973)
at hidden.org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
at hidden.org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at hidden.org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at hidden.org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at hidden.org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:446)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:330)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
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)
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)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
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:597)
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)
[DEBUG] Using Wagon implementation httpclient from settings for server
apelon-data
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Broken pipe
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
deploying artifact: Broken pipe
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
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:597)
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: Broken pipe
at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:244)
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: Broken pipe
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121)
at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:240)
... 19 more
Caused by: org.apache.maven.wagon.TransferFailedException: Broken pipe
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:336)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
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.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon$RequestEntityImplementation.writeRequest(AbstractHttpClientWagon.java:160)
at hidden.org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495)
at hidden.org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973)
at hidden.org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
at hidden.org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at hidden.org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at hidden.org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at hidden.org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:446)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:330)
... 24 more
I believe that the server is on a windows box... but I'm not positive.
I've requested a dump of the logs from it, but it might take a while
to get them.
Re: Uploading large files?
Posted by Brett Porter <br...@apache.org>.
Can you try using httpclient on the Maven end instead?
http://maven.apache.org/guides/mini/guide-wagon-providers.html
Also, what operating system is Maven on, and what OS is Archiva on?
Regards,
Brett
On 02/08/2011, at 11:45 AM, Dan Armbrust wrote:
>> And this is weird. with the -X flag, the command is taking _much_
>> longer to execute... so long that I suspect it might actually work.
>> Why on earth would the -X flag change the behavior....
>
> Ran for 16 minutes with the debug flag on, then failed.
> Fails in about 20 seconds without the debug flag on.
>
> The debug flag gives the same output on the error as the stack trace
> posted before. Nothing new, unfortunately.
>
> [INFO] [deploy:deploy-file {execution: default-cli}]
> [DEBUG] Using Wagon implementation lightweight from default mapping
> for protocol http
> [DEBUG] Checking for pre-existing User-Agent configuration.
> [DEBUG] Adding User-Agent configuration.
> [DEBUG] not adding permissions to wagon connection
> Uploading: http:// <validpath> .zip
> [DEBUG] Error writing to server
> java.io.IOException: Error writing to server
> at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:578)
> at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:590)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1193)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
> at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
> 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)
> 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)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
> 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:597)
> 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)
> [DEBUG] Using Wagon implementation lightweight from default mapping
> for protocol http
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Error transferring file
>
> 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.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
> 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:597)
> 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:244)
> 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:240)
> ... 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:578)
> at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:590)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1193)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
> at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
> ... 27 more
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: Uploading large files?
Posted by Dan Armbrust <da...@gmail.com>.
> Ran for 16 minutes with the debug flag on, then failed.
> Fails in about 20 seconds without the debug flag on.
>
hmm. The 15 minute thing seems to have been a fluke with my network
connection. My other long-running network dependent task also hung /
failed at about the same time. Stupid cable modem. Sigh.
The debug flag now runs as I would expect, and makes no difference to
the deploy failure.
Re: Uploading large files?
Posted by Dan Armbrust <da...@gmail.com>.
> And this is weird. with the -X flag, the command is taking _much_
> longer to execute... so long that I suspect it might actually work.
> Why on earth would the -X flag change the behavior....
Ran for 16 minutes with the debug flag on, then failed.
Fails in about 20 seconds without the debug flag on.
The debug flag gives the same output on the error as the stack trace
posted before. Nothing new, unfortunately.
[INFO] [deploy:deploy-file {execution: default-cli}]
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol http
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] not adding permissions to wagon connection
Uploading: http:// <validpath> .zip
[DEBUG] Error writing to server
java.io.IOException: Error writing to server
at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:578)
at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:590)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1193)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
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)
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)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
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:597)
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)
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol http
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Error transferring file
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.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
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:597)
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:244)
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:240)
... 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:578)
at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:590)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1193)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
... 27 more
Re: Uploading large files?
Posted by Dan Armbrust <da...@gmail.com>.
Probably not a lot of help here:
[INFO] 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.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
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:597)
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:244)
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:240)
... 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:578)
at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:590)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1193)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
... 27 more
And this is weird. with the -X flag, the command is taking _much_
longer to execute... so long that I suspect it might actually work.
Why on earth would the -X flag change the behavior....
Re: Uploading large files?
Posted by Brett Porter <br...@apache.org>.
Is there any more trace provided - particularly an exception? Perhaps -e on the command line, or if not then -X, would help?
- Brett
On 02/08/2011, at 10:05 AM, Dan Armbrust wrote:
> My on again-off again issues with uploading have come back again.
>
> I was trying to upload another large file to archiva, and the web
> interface just barely, sort of, sometimes works for that.
>
> So I tried to do it the right way, and use maven.
>
> I made a little pom file for the zip I wanted to upload.
>
> Made a little settings.xml file with the credentials.
>
> Ran something like this:
>
> mvn -s settings.xml deploy:deploy-file -Dfile=bigBinaryFile.zip
> -DrepositoryId=my-repository
> -Durl=http://my-server:8080/archiva/repository/my-repository
> -DgeneratePom=false -DpomFile=pom.xml
>
> And maven simply pukes out (roughly):
>
> [INFO] [deploy:deploy-file {execution: default-cli}]
> Uploading:... bigBinaryFile.zip
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Error transferring file
>
> Error writing to server
>
>
> And the uploading portion goes _way_ to fast - I know there is no
> possible way that it actually transferred the file. Yet, the bit
> counter from maven (during the upload) claims that it has.
>
> Any idea why this doesn't work? It does work with small test files.
>
> mvn version: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500)
> Archiva version 1.3.4
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: Uploading large files?
Posted by Dan Armbrust <da...@gmail.com>.
My on again-off again issues with uploading have come back again.
I was trying to upload another large file to archiva, and the web
interface just barely, sort of, sometimes works for that.
So I tried to do it the right way, and use maven.
I made a little pom file for the zip I wanted to upload.
Made a little settings.xml file with the credentials.
Ran something like this:
mvn -s settings.xml deploy:deploy-file -Dfile=bigBinaryFile.zip
-DrepositoryId=my-repository
-Durl=http://my-server:8080/archiva/repository/my-repository
-DgeneratePom=false -DpomFile=pom.xml
And maven simply pukes out (roughly):
[INFO] [deploy:deploy-file {execution: default-cli}]
Uploading:... bigBinaryFile.zip
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Error transferring file
Error writing to server
And the uploading portion goes _way_ to fast - I know there is no
possible way that it actually transferred the file. Yet, the bit
counter from maven (during the upload) claims that it has.
Any idea why this doesn't work? It does work with small test files.
mvn version: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500)
Archiva version 1.3.4
Re: Uploading large files?
Posted by Mark Struberg <st...@yahoo.de>.
I remember that there was some 1 or 2 GByte limit because the http client used by mavens wagon-http only has a 32bit variable for the package length or something of that kind. Something in that direction (would need to grab the sources).
So this is most probably not really an archiva limit but a maven one.
LieGrue,
strub
--- On Sun, 5/8/11, Brett Porter <br...@apache.org> wrote:
> From: Brett Porter <br...@apache.org>
> Subject: Re: Uploading large files?
> To: users@archiva.apache.org
> Date: Sunday, May 8, 2011, 7:18 PM
> In general, browsers don't deal that
> well with uploading such large files.
>
> If it's a regular occurrence, I'd recommend using the mvn
> deploy:deploy-file command instead [1].
>
> If it's a once off setup task, I'd recommend copying this
> file onto the filesystem of the repository by hand and
> letting Archiva discover and scan it. You'll probably find
> it easier to deal with large files using your conventional
> tools.
>
> HTH,
> Brett
>
> [1] http://maven.apache.org/plugins/maven-deploy-plugin/usage.html
>
> On 09/05/2011, at 1:22 AM, Dan Armbrust wrote:
>
> > Hmm. Back to the the original problem of my
> thread.
> >
> > Now, I'm trying to upload a 700 MB file through the
> web form, and all I get is:
> >
> > Error 101 (net::ERR_CONNECTION_RESET): The connection
> was reset.
> >
> > Part way through the transfer.
> >
> > Are their any other hidden limits that i need to
> adjust?
> >
> > I'm rather new to the whole maven world... but hasn't
> anybody ever
> > tried this with large files before? Is my use
> case that unusual?
> >
> > Thanks,
> >
> > Dan
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
>
Re: Uploading large files?
Posted by Mark Struberg <st...@yahoo.de>.
I remember that there was some 1 or 2 GByte limit because the http client used by mavens wagon-http only has a 32bit variable for the package length or something of that kind. Something in that direction (would need to grab the sources).
So this is most probably not really an archiva limit but a maven one.
LieGrue,
strub
--- On Sun, 5/8/11, Brett Porter <br...@apache.org> wrote:
> From: Brett Porter <br...@apache.org>
> Subject: Re: Uploading large files?
> To: users@archiva.apache.org
> Date: Sunday, May 8, 2011, 7:18 PM
> In general, browsers don't deal that
> well with uploading such large files.
>
> If it's a regular occurrence, I'd recommend using the mvn
> deploy:deploy-file command instead [1].
>
> If it's a once off setup task, I'd recommend copying this
> file onto the filesystem of the repository by hand and
> letting Archiva discover and scan it. You'll probably find
> it easier to deal with large files using your conventional
> tools.
>
> HTH,
> Brett
>
> [1] http://maven.apache.org/plugins/maven-deploy-plugin/usage.html
>
> On 09/05/2011, at 1:22 AM, Dan Armbrust wrote:
>
> > Hmm. Back to the the original problem of my
> thread.
> >
> > Now, I'm trying to upload a 700 MB file through the
> web form, and all I get is:
> >
> > Error 101 (net::ERR_CONNECTION_RESET): The connection
> was reset.
> >
> > Part way through the transfer.
> >
> > Are their any other hidden limits that i need to
> adjust?
> >
> > I'm rather new to the whole maven world... but hasn't
> anybody ever
> > tried this with large files before? Is my use
> case that unusual?
> >
> > Thanks,
> >
> > Dan
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
>
Re: Uploading large files?
Posted by Brett Porter <br...@apache.org>.
In general, browsers don't deal that well with uploading such large files.
If it's a regular occurrence, I'd recommend using the mvn deploy:deploy-file command instead [1].
If it's a once off setup task, I'd recommend copying this file onto the filesystem of the repository by hand and letting Archiva discover and scan it. You'll probably find it easier to deal with large files using your conventional tools.
HTH,
Brett
[1] http://maven.apache.org/plugins/maven-deploy-plugin/usage.html
On 09/05/2011, at 1:22 AM, Dan Armbrust wrote:
> Hmm. Back to the the original problem of my thread.
>
> Now, I'm trying to upload a 700 MB file through the web form, and all I get is:
>
> Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.
>
> Part way through the transfer.
>
> Are their any other hidden limits that i need to adjust?
>
> I'm rather new to the whole maven world... but hasn't anybody ever
> tried this with large files before? Is my use case that unusual?
>
> Thanks,
>
> Dan
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter