Long queue time with Bamboo Remote Agent

[Caleb Duckwall]

I just recently started seeing issues with our Bamboo Remote Agent and plans being queued for a few minutes before running, even though no other plans are running and the agent is clear to build the queued plan. In the log for the remote agent, the following is printed almost every minute until eventually the agent picks up the plan and runs it like normal.

2016-04-25 09:14:10,987 WARN [ActiveMQ InactivityMonitor Worker] [FailoverTransport] Transport (https://xxx.atlassian.net:443/builds/jmsServlet) failed, attempting to automatically reconnect
org.apache.activemq.transport.InactivityIOException: Channel was inactive (no connection attempt made) for too (>30000) long: https://xxx.atlassian.net:443/builds/jmsServlet
at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source
2016-04-25 09:14:26,624 INFO [ActiveMQ Task-48] [HttpClientTransport] Broker Servlet supports GZip compression.

I have tried to completely uninstall/re-install the remote agent, Java, etc. All plans seem to get run from the queue eventually, but they are not instantaneous like they used to be, and all of the plans being queued creates a backlog. Any suggestions are welcome.

Thanks. 

[Przemek Bruski · Accepted solution]

It's a known issue, we are working on fixing it.

[Bhagwan Basnet (Aakash)]

Did you check the remote agent status, I mean they are offline or online? also sometimes dedicating the agent to specific plan may help to build the plan in timely fashion.

[Caleb Duckwall]

Thanks for your response, Bhagwan. The agent is online and will eventually run the build after the plan has sat in the queue for 1-5 minutes. There are no other builds being run and the agent should be completely clear and capable to run the queued build, so not sure why the plan is being queued in the first place. At this point, since our Bamboo set up only has one available remote agent, dedicating the agent to a specific plan is not possible.

[vitalii]

Have the same problem here.

[Caleb Duckwall]

Hey vitalii,

Check out the JIRA created to handle this issue here: BAM-17479 - Bamboo Not Executing Queued Builds OPEN  

I followed the directions supplied by Russ Gould and entered a support case for having a workaround applied to our environment which seems to have fixed the issue for us.

Hope that helps.

Caleb

[vitalii]

Hi, Caleb - thanks for the hint, opening a support ticket was a great idea: they had fixed the problem yesterday, so now everything works fine.