(Atlassian SDK) Sometime Occur java.net.SocketException: Software caused connection abort: recv failed

JongBum Lee July 30, 2015

Dear All.

 

sometime, my atlassian sdk execute with atlas-run then, follow error occurs

(using proxy (set settings.xml))

 

[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:5.0.13:run (default-cli) on project helloworld: Unable to execute mojo: Execution null of goal com.atlassian.mav
en.plugins:maven-jira-plugin:5.0.13:run failed: java.net.SocketException: Software caused connection abort: recv failed -> [Help 1]

 

[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:5.0.13:run (default-cli) on project adminUI: Unable to execute mojo: Execution null of goal com.atlassian.maven.
plugins:maven-refapp-plugin:5.0.13:run failed: java.net.SocketException: Software caused connection abort: recv failed -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:5.0.13:run (default-cli) on project adminUI: Unable to execute m
ojo
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
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:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:174)
at org.twdata.maven.mojoexecutor.MojoExecutor$ExecutionEnvironmentM3.executeMojo(MojoExecutor.java:476)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo(MojoExecutor.java:75)
at com.atlassian.maven.plugins.ampsdispatcher.AbstractAmpsDispatcherMojo.execute(AbstractAmpsDispatcherMojo.java:60)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution null of goal com.atlassian.maven.plugins:maven-refapp-plugin:5.0.13:run failed: java.net.SocketException: Software caused connect
ion abort: recv failed
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:144)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:172)
... 24 more
Caused by: java.lang.RuntimeException: java.net.SocketException: Software caused connection abort: recv failed
at com.atlassian.maven.plugins.updater.MarketplaceSdkResource.getPluginJsonAsMap(MarketplaceSdkResource.java:136)
at com.atlassian.maven.plugins.updater.MarketplaceSdkResource.getLatestSdkVersion(MarketplaceSdkResource.java:98)
at com.atlassian.maven.plugins.amps.util.UpdateCheckerImpl.check(UpdateCheckerImpl.java:57)
at com.atlassian.maven.plugins.amps.RunMojo.doExecute(RunMojo.java:103)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.execute(AbstractProductHandlerMojo.java:750)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
... 25 more
Caused by: java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:188)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
at sun.security.ssl.InputRecord.read(InputRecord.java:503)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
at com.atlassian.maven.plugins.updater.MarketplaceSdkResource.getPluginJsonAsMap(MarketplaceSdkResource.java:133)
... 30 more
[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

 

 

Ask me for help.
Thank you

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted
Volodymyr Krupach
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 30, 2015

I guess that link that you have at the end of the stack trace answers your question: http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Logan G Hawkes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 31, 2015

One would think, but the linked page is less than helpful: "Unlike many other errors, this exception is not generated by the Maven core itself but by a plugin. As a rule of thumb, plugins use this error to signal a problem in their configuration or the information they retrieved from the POM. The concrete meaning of the exception depends on the plugin so please have a look at its documentation. The documentation for many common Maven plugins can be reached via our plugin index." It would seem that the problem is related to the maven-amps-dispatcher-plugin version 5.0.13, specifically the "run" command, but that's all we know. Moreover, the plugins index page (http://maven.apache.org/plugins/) doesn't list the maven-amps-dispatcher-plugin.

3 votes
Logan G Hawkes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 31, 2015

I'm in the same boat. I've found some things to try that help sometimes.

  1. Check your proxy settings. They may be defined in several places. Which one is "right" is a mystery to me.
    1. Your ~/.m2/settings.xml file.
    2. C:\atlassian-plugin-sdk\apache-maven-3.2.1\conf\settings.xml
    3. Other places TBD. 
  2. I've never been able to get atlas-run to contact marketplace.atlassian.com. The first time I try each day it will fail. Atlas-run is set to try to contact the marketplace once a day, so once that failure has happened atlas-run won't try again until the next day. There's an open bug on this: AMPS-1239. The workaround is to use 'atlas-run -Doffline=true'.
  3. Run 'atlas-clean' and then try 'atlas-run' again. Sometimes it just works.
  4. Make sure there isn't an errant unkilled java process lurking on your machine.
  5. Try running the actual maven command listed in the 'atlas-run' output to see what you get. It will look something like this: 
C:\atlastutorial\my_plugin_project>atlas-run
Executing: "C:\atlassian-plugin-sdk\apache-maven-3.2.1\bin\mvn.bat" com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:5.0.13:run -gs C:\atlassian-plugin-sdk\apache-maven-3.2.1/conf/settings.xml
TAGS
AUG Leaders

Atlassian Community Events