Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355338 - M2e does not respect settings.xml timeout specification for HTTP/HTTPS connections
Summary: M2e does not respect settings.xml timeout specification for HTTP/HTTPS connec...
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-22 02:33 EDT by Frederick Staats CLA
Modified: 2021-04-19 13:23 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederick Staats CLA 2011-08-22 02:33:40 EDT
Build Identifier: 1.0.0.20110607-2117

In AsyncFetecher.java http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/index/AsyncFetcher.java?id=3f2dd8a600d058419b42ff25d7afbe09854f7efd

In m2e 1.0.0 HTTP connection timeouts are hardwired to 15 seconds (Line 118) and request timeouts are hardwired to 60 seconds (Line 119).  In the Advanced Configuration of the HttpClient HTTP Wagon for Apache Maven (http://maven.apache.org/guides/mini/guide-http-settings.html) it specifies that the default timeouts should be configurable in the Server section of the settings.xml file.  The lack of the configuration option for the embedded Maven (3.0.3) in m2e (1.0.0) makes it m2e fail to upload/download large artifacts with maven-deploy-plugin in the same manner as the command line version of Maven (mvn).

Example m2e Debug output when the error occurs (Note in this case the upload takes ~130 seconds and works with the command line mvn tool), the server being deployed to has the following configuration):

    <server>
      <username>username</username>
      <password>***</password>
      <configuration>
        <httpConfiguration>
          <all>
            <connectionTimeout>300000</connectionTimeout>
          </all>
        </httpConfiguration>
      </configuration>
      <id>Snapshots</id>
    </server>

This configuration was also tried:

    <server>
      <username>username</username>
      <password>***</password>
      <configuration>
        <timeout>300000</timeout>
      </configuration>
      <id>Snapshots</id>
    </server>


[INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ ui ---
[DEBUG] org.apache.maven.plugins:maven-deploy-plugin:jar:2.6:
[DEBUG]    org.apache.maven:maven-plugin-api:jar:2.0.6:compile
[DEBUG]    org.apache.maven:maven-project:jar:2.0.6:compile
[DEBUG]       org.apache.maven:maven-settings:jar:2.0.6:compile
[DEBUG]       org.apache.maven:maven-profile:jar:2.0.6:compile
[DEBUG]       org.apache.maven:maven-artifact-manager:jar:2.0.6:compile
[DEBUG]          org.apache.maven:maven-repository-metadata:jar:2.0.6:compile
[DEBUG]       org.apache.maven:maven-plugin-registry:jar:2.0.6:compile
[DEBUG]       org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG]          junit:junit:jar:3.8.1:compile
[DEBUG]          classworlds:classworlds:jar:1.1-alpha-2:compile
[DEBUG]    org.apache.maven:maven-model:jar:2.0.6:compile
[DEBUG]    org.apache.maven:maven-artifact:jar:2.0.6:compile
[DEBUG]    org.codehaus.plexus:plexus-utils:jar:1.5.6:compile
[DEBUG] Created new class realm plugin>org.apache.maven.plugins:maven-deploy-plugin:2.6
[DEBUG] Importing foreign packages into class realm plugin>org.apache.maven.plugins:maven-deploy-plugin:2.6
[DEBUG]   Imported:  < project>com.intel.wcm:ui:1.0-SNAPSHOT
[DEBUG] Populating class realm plugin>org.apache.maven.plugins:maven-deploy-plugin:2.6
[DEBUG]   Included: org.apache.maven.plugins:maven-deploy-plugin:jar:2.6
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG]   Excluded: org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG] Configuring mojo org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-deploy-plugin:2.6, parent: sun.misc.Launcher$AppClassLoader@77cde100]
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy' with basic configurator -->
[DEBUG]   (f) artifact = com.intel.wcm:ui:content-package:1.0-SNAPSHOT
[DEBUG]   (f) attachedArtifacts = []
[DEBUG]   (s) localRepository =        id: local
      url: file:///C:/Users/fstaats/.m2/repository/
   layout: none

[DEBUG]   (f) offline = false
[DEBUG]   (f) packaging = content-package
[DEBUG]   (f) pomFile = C:\Users\fstaats\Desktop\workspaces\feature-build-automation\maven.1313694228331\wcm\ui\pom.xml
[DEBUG]   (f) project = MavenProject: com.intel.wcm:ui:1.0-SNAPSHOT @ C:\Users\fstaats\Desktop\workspaces\feature-build-automation\maven.1313694228331\wcm\ui\pom.xml
[DEBUG]   (f) skip = false
[DEBUG]   (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[DEBUG] Using connector AsyncRepositoryConnector with priority 100 for https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/ as fstaats
Downloading: https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/com/intel/wcm/ui/1.0-SNAPSHOT/maven-metadata.xml
Downloaded: https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/com/intel/wcm/ui/1.0-SNAPSHOT/maven-metadata.xml (759 B at 0.6 KB/sec)
[DEBUG] Reading resolution tracking file C:\Users\fstaats\.m2\repository\com\intel\wcm\ui\1.0-SNAPSHOT\resolver-status.properties
[DEBUG] Writing resolution tracking file C:\Users\fstaats\.m2\repository\com\intel\wcm\ui\1.0-SNAPSHOT\resolver-status.properties
Uploading: https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/com/intel/wcm/ui/1.0-SNAPSHOT/ui-1.0-20110822.062456-9.zip
Uploading: https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/com/intel/wcm/ui/1.0-SNAPSHOT/ui-1.0-20110822.062456-9.pom
Uploaded: https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/com/intel/wcm/ui/1.0-SNAPSHOT/ui-1.0-20110822.062456-9.pom (5 KB at 2.4 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:35.498s
[INFO] Finished at: Sun Aug 21 23:25:57 PDT 2011
[INFO] Final Memory: 9M/87M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project ui: Failed to deploy artifacts: Could not transfer artifact com.intel.wcm:ui:zip:1.0-20110822.062456-9 from/to Snapshots (https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/): No response received after 60000 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project ui: Failed to deploy artifacts: Could not transfer artifact com.intel.wcm:ui:zip:1.0-20110822.062456-9 from/to Snapshots (https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/): No response received after 60000
	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.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	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.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to deploy artifacts: Could not transfer artifact com.intel.wcm:ui:zip:1.0-20110822.062456-9 from/to Snapshots (https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/): No response received after 60000
	at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:192)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
	... 19 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact com.intel.wcm:ui:zip:1.0-20110822.062456-9 from/to Snapshots (https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/): No response received after 60000
	at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:141)
	at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:156)
	... 21 more
Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to deploy artifacts: Could not transfer artifact com.intel.wcm:ui:zip:1.0-20110822.062456-9 from/to Snapshots (https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/): No response received after 60000
	at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:284)
	at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:215)
	at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:480)
	at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137)
	... 22 more
Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact com.intel.wcm:ui:zip:1.0-20110822.062456-9 from/to Snapshots (https://ccapnexus.intel.com:8443/nexus/content/repositories/snapshots/): No response received after 60000
	at org.sonatype.aether.connector.async.AsyncRepositoryConnector$3.wrap(AsyncRepositoryConnector.java:1426)
	at org.sonatype.aether.connector.async.AsyncRepositoryConnector$3.wrap(AsyncRepositoryConnector.java:1417)
	at org.sonatype.aether.connector.async.AsyncRepositoryConnector$PutTask.flush(AsyncRepositoryConnector.java:1065)
	at org.sonatype.aether.connector.async.AsyncRepositoryConnector.put(AsyncRepositoryConnector.java:337)
	at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:278)
	... 25 more
Caused by: java.util.concurrent.TimeoutException: No response received after 60000
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture.run(NettyAsyncHttpProvider.java:1773)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	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)
[ERROR] 
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


Reproducible: Always

Steps to Reproduce:
1. Configure settings.xml for servers for extended timeout as specified in http://maven.apache.org/guides/mini/guide-http-settings.html see example in description.
2. Run a pom.xml with a deploy goal using the maven-deploy-plugin in m2e where the connection is slow and the artifact is large so the artifact transfer time exceeds 60 seconds.
3. Observe a stack trace similar to the one in the description.
Comment 1 Igor Fedorenko CLA 2011-08-22 10:53:02 EDT
This is limitation/incompatibility between Maven core and Aether used by m2e. Has to be fixed in maven and/or aether before we can address this in m2e.
Comment 2 Mario Jauvin CLA 2012-03-30 14:02:21 EDT
What is the status of this problem?
Comment 3 Igor Fedorenko CLA 2012-03-30 14:33:36 EDT
This is a limitation of aether, so you need to ask aether developers when/if this will happen or if there are alternative ways to achieve what you need. 

I am willing to consider using newer version of aether in m2e, if this is necessary to solve this problem, but somebody will need to tell me what version of aether that is and provide quality patches.
Comment 4 Igor Fedorenko CLA 2013-09-28 23:58:23 EDT
closing old/stale bugreports
Comment 5 Denis Roy CLA 2021-04-19 13:23:44 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/