Hi,
I had started to use a Bamboo cloud a couple of days ago, and i set up the process in the first day and it works great.
Agent is installed on my Mac laptop. For starting it, i'm running a sh script with the
java -jar atlassian-bamboo-agent-installer address and stuff
However, now i'd switched to another Bamboo server (moved from test server to the real one), so i updated sh with new address and keys, and i had started to get these issues in console:
INFO | jvm 1 | 2016/04/26 11:36:38 | org.apache.activemq.transport.InactivityIOException: Channel was inactive (no connection attempt made) for too (>30000) long: ***:443/builds/jmsServlet
INFO | jvm 1 | 2016/04/26 11:36:38 | at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)
INFO | jvm 1 | 2016/04/26 11:36:38 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
INFO | jvm 1 | 2016/04/26 11:36:38 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
INFO | jvm 1 | 2016/04/26 11:36:38 | at java.lang.Thread.run(Thread.java:745)
INFO | jvm 1 | 2016/04/26 11:36:55 | 2016-04-26 11:36:55,038 INFO [ActiveMQ Task-24] [HttpClientTransport] Broker Servlet supports GZip compression.
INFO | jvm 1 | 2016/04/26 11:37:23 | 2016-04-26 11:37:23,387 WARN [ActiveMQ InactivityMonitor Worker] [FailoverTransport] Transport (***:443/builds/jmsServlet) failed, attempting to automatically reconnect
Sometimes it works fine, but from time to time, Agent is not able to start its job after commit was pushed, and Bamboo reports:
Build JOB-31 had to be cancelled: it was marked as queued but was not present in the queue for (at least) the past 720 seconds.
Google said nothing about this error.
