[BAM-15520] 5.7.2 REST regression: /queue at plan concurrency limit

Type: Bug
Resolution: Done
Priority: Medium
Fix Version/s: 5.15.0.1
Affects Version/s: 5.7.2
Component/s: None
Labels:
None

Symptom Severity:
Severity 2 - Major
Bug Fix Policy:
View Atlassian Server bug fix policy

We just upgraded to 5.7.2. Didn't want to since we were stable, but were forced by your Security Advisory about Struts breakage. Now we're unstable

In particular, the /queue REST call no longer handles concurrency limits gracefully. Formerly it returned a 3xx code and a nice message, now it throws a stack trace in the logs with status=500. Excerpt from atlassian-bamboo.log:

2015-02-04 12:24:35,777 INFO [http-bio-8085-exec-37] [AccessLogFilter] 10.140.142.252 GET http://re-bamboo.sv.splunk.com/rest/api/latest/plan/MISC-TST?expand=stages.stage.plans 30969kb
2015-02-04 12:24:35,868 INFO [http-bio-8085-exec-45] [AccessLogFilter] bamboo POST http://re-bamboo.sv.splunk.com/rest/api/latest/queue/MISC-TST 27375kb
Feb 04, 2015 12:24:35 PM com.sun.jersey.spi.container.ContainerResponse write
SEVERE: 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
2015-02-04 12:24:35,871 ERROR [http-bio-8085-exec-45] [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
Feb 04, 2015 12:24:35 PM com.sun.jersey.spi.container.ContainerResponse write
SEVERE: 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

2015-02-04 12:24:35,871 ERROR [http-bio-8085-exec-45] [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

2015-02-04 12:24:35,873 ERROR [http-bio-8085-exec-45] [FiveOhOh] 500 Exception was thrown.

Please provide a fix ETA ASAP. This whole Struts issue is a mess for us: first we're made vulnerable, then we have to upgrade, now the upgrade introduces more bugs ... aaagh! This new bug is delaying an internal product release and is hard to code around since little is returned to the caller to distinguish this from another 5xx return.

duplicates

BAM-17995 Bamboo should return a valid error message when JIRA fail to trigger build due to max concurrent build reached

Closed

Monique Khairuliana (Inactive) made changes - 19/Aug/2019 2:05 AM

Workflow	Original: Bamboo Workflow 2016 v1 - Restricted [ 1436753 ]	New: JAC Bug Workflow v3 [ 3385757 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Owen made changes - 24/Oct/2018 5:06 AM

Symptom Severity

Original: Major [ 14431 ]

New: Severity 2 - Major [ 15831 ]

Marcin Oles made changes - 15/Nov/2016 1:05 PM

Fix Version/s		New: 5.15.0 [ 64338 ]
Resolution	Original: Fixed [ 1 ]	New: Done [ 17 ]
Status	Original: In Progress [ 3 ]	New: Resolved [ 5 ]

Marcin Oles made changes - 04/Nov/2016 9:13 AM

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Marcin Oles made changes - 04/Nov/2016 9:13 AM

Assignee

New: Marcin Oles [ moles ]

Marcin Oles made changes - 04/Nov/2016 9:05 AM

Link

New: This issue duplicates ~~BAM-17995~~ [ ~~BAM-17995~~ ]

jonah (Inactive) made changes - 26/Aug/2016 1:34 AM

Symptom Severity

New: Major [ 14431 ]

Owen made changes - 07/Jul/2016 3:48 AM

Workflow

Original: Bamboo Workflow 2016 v1 [ 1418622 ]

New: Bamboo Workflow 2016 v1 - Restricted [ 1436753 ]

Marek Went (Inactive) made changes - 16/Jun/2016 10:21 AM

Workflow

Original: Bamboo Workflow 2014 v2 [ 797541 ]

New: Bamboo Workflow 2016 v1 [ 1418622 ]

Sten Pittet (Inactive) added a comment - 08/Feb/2015 10:27 PM

Hi eng-release,

I'm sorry to see you running into this issue. Could you please let me know which version of Bamboo you were using before? That will help to identify when the regression was introduced.

Thanks,

Sten Pittet
Bamboo Product Manager

Sten Pittet (Inactive) added a comment - 08/Feb/2015 10:27 PM Hi eng-release , I'm sorry to see you running into this issue. Could you please let me know which version of Bamboo you were using before? That will help to identify when the regression was introduced. Thanks, Sten Pittet Bamboo Product Manager

Assignee:: Marcin Oles

Reporter:: Splunk Release Engineering

Affected customers:: 1 This affects my team

Watchers:: 10 Start watching this issue

Created:: 04/Feb/2015 8:50 PM

Updated:: 19/Aug/2019 2:05 AM

Resolved:: 15/Nov/2016 1:05 PM

Details

Description

Attachments

Issue Links

Forms

Activity

Collapse comment: Sten Pittet (Inactive) added a comment - 08/Feb/2015 10:27 PM

Expand comment: Sten Pittet (Inactive) added a comment - 08/Feb/2015 10:27 PM

People

Dates