Bamboo REST error and info messages filling up JIRA log

[Anthony Pomtree]

Looking at the main log (atlassian.log), it is filled with the following log entries:

2014-02-11 10:43:48,617 http-bio-8080-exec-14 ERROR user 643x188734x3 ty0tpe X.X.X.X /rest/bamboo/latest/deploy/PROJ/PROJ-XXXX [ext.bamboo.service.BambooRestServiceImpl] Invalid return code received from rCMS Bamboo. 404:Not Found

2014-02-11 10:43:48,695 http-bio-8080-exec-14 INFO user 643x188734x3 ty0tpe X.X.X.X /rest/bamboo/latest/deploy/PROJ/PROJ-XXX [ext.bamboo.rest.BambooDeploymentProjectResource] Bamboo server version 4.4.5 does not support Deployments REST endpoint. Suppressing error 404

Our application versions are as follows:

JIRA - v6.0.1#6096
Bamboo - v4.4.5#3507

I know we have plans to upgrade both products at some point, but is there something that we can look at in the meantime? These log entries make up approximately 40-50% of the log. Thanks.

[DIGIT CITnet]

Same problem with

- JIRA 6.2.7

- Bamboo 4.4.8

@Guy, we don't have access to your support issue, what is the status?

[Guy Anela]

They basically told me we need to upgrade our Bamboo instance to 5.1 and/or adjust our log levels to prevent the entries from populating the log (See last post below regarding the log level adjustments).

Guy,

Since you are not able to upgrade now, you may want to try adjusting the log levels so that these events are not captured.

Logging is described on our Logging and Profiling page.

You can change the logging level of the packages that are filling up the logs. Keep in mind that this does not just filter out the 404s but all errors for that package.

To filter out the message, add the following lines to the end of your log4j.properties file, which is located in your JIRA Installation Directory (atlassian-jira/bin/WEB-INF/classes).

404 Errors

log4j.logger.com.atlassian.jira.plugin.ext.bamboo.rest.BambooDeploymentProjectResource = ERROR
log4j.logger.com.atlassian.jira.plugin.ext.bamboo.service.BambooRestServiceImpl = FATAL

"...Using getResponseBodyAsStream..."

log4j.logger.org.apache.commons.httpclient = ERROR, console, filelog
log4j.additivity.org.apache.commons.httpclient = false

You will need to restart JIRA after making this change. By editing the log4j file, the changes will persist across JIRA reboots.

You have the option of turning off the 404 errors without rebooting. To do this you just need to add the two Bamboo packages to list of Default Loggers that appears in the JIRA administration section Logging & Profiling (<JIRA>/secure/admin/ViewLogging.jspa).

• If you add the Bamboo packages through the UI, remove "log4j.logger." from the beginning of the packages so that the package begins with "com"
• Note that this will not persist after a reboot, only changes to the log4j file persist.

I hope that helps you knock out some of the messages that are filling up your log files. If you have any questions please be sure to let me know.

Thanks!!
Tim | Atlassian

[Guy Anela]

We're seeing this as well. I added JSP-194143.

JIRA - v6.0.8

Bamboo - v5.0

[David Sutton]

We are seeing the same problem.

JIRA - v6.1.5#6160
Bamboo - v4.4.5#3507