nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bamboo Maven builds for a 3rd party product are failing with the following connection reset errors.

GSHerber

Bamboo Log errors: build 24-Jul-2023 16:28:53 Caused by: javax.net.ssl.SSLException: Connection reset
GET request of: org/apache/cxf/cxf-core/3.5.5/cxf-core-3.5.5.jar from nexus.mirror failed

The Nexus proxy shows a similar error at the same time: Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host.

We have the idle timeouts to 5 minutes for Maven and Nexus but the build still fails. Any one have some insight?

Accepted answers

Eduardo Alvarenga

Hello @GSHerber

Bamboo will launch the build task as configured but will have no control over the transmission between Maven and your Nexus server. You will have to investigate the process externally.

Ideally, try to run the same subset of commands manually while being outside of the Bamboo Agent interface looking to reproduce the issue.

You can cwd to the <bamboo-agent-home>/xml-data/build-dir/PLAN-KEY-JOB> folder on your Agent and run the tasks from that Job manually looking to reproduce it.

Kind regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

All comments

Eduardo Alvarenga

Hello @GSHerber

Bamboo will launch the build task as configured but will have no control over the transmission between Maven and your Nexus server. You will have to investigate the process externally.

Ideally, try to run the same subset of commands manually while being outside of the Bamboo Agent interface looking to reproduce the issue.

You can cwd to the <bamboo-agent-home>/xml-data/build-dir/PLAN-KEY-JOB> folder on your Agent and run the tasks from that Job manually looking to reproduce it.

Kind regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

GSHerber

Not sure this is progress but this is what we have so far: The Maven build task in Bamboo was set with the -U -X parameters, both of which created a lot of network overhead. We replaced them with -e parameter and the network resets/disconnects are gone. We still have the ' Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-process-classes of goal org.mule.tools.maven:mule-maven-plugin:3.8.5:process-classes failed: org.mule.tooling.api.ToolingException: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy' error.

Any insight?

GSHerber

I was able to run the Maven build outside of Bamboo from command line. I first had the -X debug off and just ran a 'mvn -e clean verify'. This ran with with out the network disconnects but still failed with an error 'org.mule.tooling.api.ToolingException: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy'. I then added the '-U -X' back to the build along with '-Dmaven.wagon.http.pool=false' like so 'mvn -s "D:\Atlassian\bamboo-install\Bamboo\tools\apache-maven-3.8.1\conf\settings.xml" -U -X clean verify -Dmaven.wagon.http.pool=false' this produced the huge debug logs without the network disconnects. The build still failed with the error 'org.mule.tooling.api.ToolingException: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy'.

At this point I'm certain that Bamboo is not the cause as the build failure is the same whether Bamboo or Maven command line runs the build. The build log revealed that there were no failures getting artifacts from Nexus for the build but the build still failed.

At this point the reporting developer was informed of the results and responded with the classic 'It builds in the development environment.' He was informed that since there were no get failures from Nexus and the build fails in the CI\CD process that there must be a dependency resource available in the development environment not defined in the the project poms. The problem was put back in the development teams hands to determine why this project builds in Dev but not in Bamboo in the CI\CD process.

So this is not a Bamboo or Maven problem at all.

Thanks to Eduardo for the guidance on running the build outside of Bamboo.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo