You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Maven User <ma...@gmail.com> on 2011/07/21 21:09:53 UTC

Re: Deploy large files

We are also seeing this but with the webdav portion of wagon -

We don't have any special configuration at all - any suggestions?  This is
crippling us at the moment :-/

cause : Error uploading site
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:deploy
(default-deploy) on project common: Error uploading site
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
	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.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
	at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:126)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:73)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:283)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site
	at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:271)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
	... 27 more
Caused by: org.apache.maven.wagon.TransferFailedException: Read timed out
	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.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:188)
	at org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:182)
	at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:257)
	... 29 more
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:129)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
	at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
	at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
	at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
	at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
	at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
	at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
	at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
	at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
	at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
	at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:446)
	at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:330)
	... 33 more

Re: Deploy large files

Posted by Hervé BOUTEMY <he...@free.fr>.
yes, we'll release m-site-p 3.0 shortly, with a hard work to fill the gap

We're pretty confident about features and doc, which should be quite exaustive 
about the few little changes that could not be avoided

please help us testing it in the final step and these difficulties should belong 
to the past

Regards,

Hervé

Le vendredi 22 juillet 2011, Benson Margulies a écrit :
> Hopefully site 3.0 will pull this together.
> 
> On Fri, Jul 22, 2011 at 2:50 PM, Maven User <ma...@gmail.com> wrote:
> > Sorry Benson - it's been pretty frustrating in general working with maven
> > 3 (I wasn't the adopter here, just the maintainer).
> > 
> > Didn't mean to take it out on the list like that - my apologies.
> > 
> > I love the speed of maven 3 but liked the "just works" nature of maven
> > 2(.2.1).
> > 
> > Thanks again all for the feedback, I appreciate it!
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Deploy large files

Posted by Benson Margulies <bi...@gmail.com>.
Hopefully site 3.0 will pull this together.

On Fri, Jul 22, 2011 at 2:50 PM, Maven User <ma...@gmail.com> wrote:
> Sorry Benson - it's been pretty frustrating in general working with maven 3
> (I wasn't the adopter here, just the maintainer).
>
> Didn't mean to take it out on the list like that - my apologies.
>
> I love the speed of maven 3 but liked the "just works" nature of maven
> 2(.2.1).
>
> Thanks again all for the feedback, I appreciate it!
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Deploy large files

Posted by Maven User <ma...@gmail.com>.
Sorry Benson - it's been pretty frustrating in general working with maven 3
(I wasn't the adopter here, just the maintainer).

Didn't mean to take it out on the list like that - my apologies.

I love the speed of maven 3 but liked the "just works" nature of maven
2(.2.1).

Thanks again all for the feedback, I appreciate it!

Re: Deploy large files

Posted by Benson Margulies <bi...@gmail.com>.
As a heavy user of site, your view that maven '3' isn't real yet is
entirely understandable.

On Fri, Jul 22, 2011 at 11:43 AM, Maven User <ma...@gmail.com> wrote:
> Ok, maybe I'm misunderstanding - but initially, I thought the goal of maven3
> was that it should have been a direct replacement with backward
> compatibility.
>
> For companies who rely heavily on site generation/deployment, this truly
> isn't the case.
>
> There are a lot of flaming hoops to jump through for this kind of thing.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Deploy large files

Posted by Maven User <ma...@gmail.com>.
Ok, maybe I'm misunderstanding - but initially, I thought the goal of maven3
was that it should have been a direct replacement with backward
compatibility.

For companies who rely heavily on site generation/deployment, this truly
isn't the case.

There are a lot of flaming hoops to jump through for this kind of thing.

Re: Deploy large files

Posted by Benson Margulies <bi...@gmail.com>.
I don't think that you're being quite fair here.

When 3.0-beta-3 was released, the default assumption was that the next
release would be beta-4. So any bugs fixed got marked 'fixed in beta
4'. Typically, a JIRA spends at least some weeks, if not months,
marked 'fixed' in a release that isn't released yet, because it's
waiting for its cohort of bugs to be fixed or for a volunteer to be
available to run the release.

In this particular case, there is a level of additional confusion
because of the policy decision that we don't need a beta-4.

I'm not sure I'm entirely prepared to dispute your overall
characterization of maven 3 -- depending on which features you care
most about.


On Fri, Jul 22, 2011 at 10:32 AM, Maven User <ma...@gmail.com> wrote:
> Impressive.
>
> Maven 3 should still be labeled a beta release...
>
> Thanks Benson for the heads up, I appreciate it.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Deploy large files

Posted by Maven User <ma...@gmail.com>.
Impressive.

Maven 3 should still be labeled a beta release...

Thanks Benson for the heads up, I appreciate it.

Re: Deploy large files

Posted by Benson Margulies <bi...@gmail.com>.
There isn't one. In fact, the current plan is to make the next release
be called '3.0' and release it quite soon.

You could build and run a snapshot from source.


On Fri, Jul 22, 2011 at 10:15 AM, Maven User <ma...@gmail.com> wrote:
> Where can I get 3.0-beta-4?
>
> Looks like you can't adjust the timeout using the <configuration> option
> with 3.0-beta-3 (see:  http://jira.codehaus.org/browse/MSITE-581).
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Deploy large files

Posted by Maven User <ma...@gmail.com>.
Where can I get 3.0-beta-4?

Looks like you can't adjust the timeout using the <configuration> option
with 3.0-beta-3 (see:  http://jira.codehaus.org/browse/MSITE-581).

Re: Deploy large files

Posted by Maven User <ma...@gmail.com>.
Sorry should be clearer - we're using maven 3.0.3 and the wagon dav for site
3.0-beta-3

On Thu, Jul 21, 2011 at 3:09 PM, Maven User <ma...@gmail.com> wrote:

> We are also seeing this but with the webdav portion of wagon -
>
> We don't have any special configuration at all - any suggestions?  This is
> crippling us at the moment :-/
>
> cause : Error uploading site
> Stack trace :
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:deploy (default-deploy) on project common: Error uploading site
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> 	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> 	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> 	at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> 	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.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> 	at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> 	at hudson.maven.Maven3Builder.call(Maven3Builder.java:126)
> 	at hudson.maven.Maven3Builder.call(Maven3Builder.java:73)
> 	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> 	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> 	at hudson.remoting.Request$2.run(Request.java:283)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site
> 	at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:271)
> 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> 	... 27 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Read timed out
> 	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.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:188)
> 	at org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:182)
> 	at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:257)
> 	... 29 more
> Caused by: java.net.SocketTimeoutException: Read timed out
> 	at java.net.SocketInputStream.socketRead0(Native Method)
> 	at java.net.SocketInputStream.read(SocketInputStream.java:129)
> 	at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> 	at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
> 	at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
> 	at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
> 	at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
> 	at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
> 	at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
> 	at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
> 	at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
> 	at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
> 	at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> 	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> 	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> 	at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:446)
> 	at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:330)
> 	... 33 more
>
>
>