Details
-
Bug
-
Resolution: Done
-
Low
-
5.14.0.2
-
None
-
JIRA 7.2.4
-
Severity 3 - Minor
-
Description
Summary
When triggering Bamboo build through JIRA Version Release function, Bamboo return 500 exception if max concurrent builds reached
Steps to Reproduce
- Create Application Link between JIRA and Bamboo
- Create a JIRA Software Development Project
- Create a JIRA Project version
- Set Concurrent Build in Bamboo to be 2
- Run the same Bamboo Build Plan twice
- Make sure that it is still running from Bamboo Build Activity
- Release the JIRA version in Step 3 and trigger the a new build for the same Bamboo Build Plan in Step 5, eg http://localhost:8724/projects/ASDF/versions/10001
Expected Results
It will have an error message that maximum concurrent build have reached
Actual Results
The below exception is thrown in the atlassian-jira.log file:
2016-11-03 17:25:22,967 http-nio-8724-exec-22 ERROR kahloun.foong 1045x1317x1 erd83b 0:0:0:0:0:0:0:1 /secure/SubmitBambooRelease.jspa [c.a.j.p.e.bamboo.service.BambooRestServiceImpl] Invalid return code received from Atlassian Bamboo. Response.statusCode: 500, statusMessage: Internal Server Error, responseBody: <html>
<head>
<title>Internal server error</title>
<meta name="decorator" content="install" />
</head>
<body>
<h1>Internal server error</h1>
<h4>Go to...</h4>
<ul>
<li><a href="/">Site homepage</a></li>
</ul>
A system error has occurred - our apologies!
<p>
Please create a problem report on our <b>support system</b> at <a href="https://support.atlassian.com/secure/CreateIssue.jspa?pid=10060&issuetype=1">http://support.atlassian.com</a> with the following information:
<ol class="standard">
<li>a description of your problem and what you were doing at the time it occurred
<li>cut & paste the error and system information found below
<li>attach the <strong>atlassian-bamboo.log</strong> log file found in your application home.
</ol>
We will respond as promptly as possible.<br/>Thank you!
</p>
<p>
<b>Version:</b> 5.14.0.2<br>
<b>Build:</b> 51412<br>
<b>Build Date:</b> 31 Oct 2016
</p>
<h4>Request information:</h4>
<ul class="standard">
<li>Request URL: http://localhost:8085/500.action</li>
<li>Scheme: http</li>
<li>Server: localhost</li>
<li>Port: 8085</li>
<li>URI: /500.action</li>
<li>Context path: </li>
<li>Servlet path: /500.action</li>
<li>Path info: </li>
<li>Query string: </li>
</ul>
<p>
<b>Stack Trace:</b>
</p>
</body>
</html>
The below exception is thrown in the atlassian-bamboo.log file:
2016-11-03 17:25:22,957 WARN [http-nio-8085-exec-23] [QueueResource] Build requested but not started, you have reached the maximum number of concurrent builds allowed 2. 2016-11-03 17:25:22,958 ERROR [http-nio-8085-exec-23] [ContainerResponse] A message body writer for Java class com.atlassian.plugins.rest.common.Status, and Java type class com.atlassian.plugins.rest.common.Status, and MIME media type application/x-www-form-urlencoded was not found 2016-11-03 17:25:22,959 ERROR [http-nio-8085-exec-23] [ContainerResponse] The registered message body writers compatible with the MIME media type are: application/x-www-form-urlencoded -> com.sun.jersey.core.impl.provider.entity.FormProvider com.sun.jersey.core.impl.provider.entity.FormMultivaluedMapProvider */* -> com.sun.jersey.core.impl.provider.entity.FormProvider com.sun.jersey.core.impl.provider.entity.StringProvider com.sun.jersey.core.impl.provider.entity.ByteArrayProvider com.sun.jersey.core.impl.provider.entity.FileProvider com.sun.jersey.core.impl.provider.entity.InputStreamProvider com.sun.jersey.core.impl.provider.entity.DataSourceProvider com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General com.sun.jersey.core.impl.provider.entity.ReaderProvider com.sun.jersey.core.impl.provider.entity.DocumentProvider com.sun.jersey.core.impl.provider.entity.StreamingOutputProvider com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter com.sun.jersey.server.impl.template.ViewableMessageBodyWriter com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General com.sun.jersey.json.impl.provider.entity.JSONWithPaddingProvider com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy 2016-11-03 17:25:22,962 ERROR [http-nio-8085-exec-23] [FiveOhOh] 500 Exception was thrown.
Notes
The JIRA error might not appear in Atlassian JIRA Cloud instance. Will need to enable HTTP debug logging to check Bamboo reply
Workaround
Increase Bamboo Concurrent Builds at Bamboo Administration >> Plans >> Concurrent builds
