Publishing specs fails with java.net.SocketException: Connection reset

SimonM
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 19, 2019

Hi,

I have a large Bamboo plan containing 100 jobs. Frequently when publishing the specs for this plan I get the exception below. Often it fails with this exception but on some occasions it will work.

Running Bamboo 6.7.1 and specs are published with the command mvn -Ppublish-specs

End snippet of stacktrace:

Caused by: com.atlassian.bamboo.specs.api.exceptions.BambooSpecsPublishingException: An error occurred while publishing plan TPROJ-G4ST
at com.atlassian.bamboo.specs.util.BambooServer.translateException (BambooServer.java:143)
at com.atlassian.bamboo.specs.util.BambooServer.publish (BambooServer.java:97)
at G4FDT.main (G4FDT.java:1203)
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:498)
at com.atlassian.bamboo.specs.maven.sandbox.SpecsRunner.callMainMethod (SpecsRunner.java:95)
at com.atlassian.bamboo.specs.maven.sandbox.SpecsRunner.runSpecsInternal (SpecsRunner.java:76)
at com.atlassian.bamboo.specs.maven.sandbox.SpecsRunner.runSpecs (SpecsRunner.java:48)
at com.atlassian.bamboo.specs.maven.RunBambooSpecsMojo.execute (RunBambooSpecsMojo.java:88)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
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:498)
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: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read (SocketInputStream.java:210)
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:983)
at sun.security.ssl.SSLSocketImpl.readDataRecord (SSLSocketImpl.java:940)
at sun.security.ssl.AppInputStream.read (AppInputStream.java:105)
at org.apache.http.impl.io.SessionInputBufferImpl.streamRead (SessionInputBufferImpl.java:139)
at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer (SessionInputBufferImpl.java:155)
at org.apache.http.impl.io.SessionInputBufferImpl.readLine (SessionInputBufferImpl.java:284)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead (DefaultHttpResponseParser.java:140)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead (DefaultHttpResponseParser.java:57)
at org.apache.http.impl.io.AbstractMessageParser.parse (AbstractMessageParser.java:261)
at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader (DefaultBHttpClientConnection.java:165)
at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader (CPoolProxy.java:167)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse (HttpRequestExecutor.java:272)
at org.apache.http.protocol.HttpRequestExecutor.execute (HttpRequestExecutor.java:124)
at org.apache.http.impl.execchain.MainClientExec.execute (MainClientExec.java:271)
at org.apache.http.impl.execchain.ProtocolExec.execute (ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute (RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute (RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute (InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute (CloseableHttpClient.java:71)
at org.apache.http.impl.client.CloseableHttpClient.execute (CloseableHttpClient.java:220)
at org.apache.http.impl.client.CloseableHttpClient.execute (CloseableHttpClient.java:164)
at org.apache.http.impl.client.CloseableHttpClient.execute (CloseableHttpClient.java:139)
at com.atlassian.bamboo.specs.util.RestHelper.sendRequest (RestHelper.java:92)
at com.atlassian.bamboo.specs.util.RestHelper.post (RestHelper.java:201)
at com.atlassian.bamboo.specs.util.SendQueue$1.run (SendQueue.java:23)

 

2 answers

0 votes
Grzegorz Słaby
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 4, 2019

Please move this ticket to Premier Support

0 votes
Grzegorz Słaby
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 2, 2019

Please move this ticket to Premier Support

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events