org.apache.activemq.transport.InactivityIOException: Channel was inactive (no connection attempt made) for too (>30000) long: blockingQueue_3328772 2016-04-21 18:19:29.032365500 at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)

Atlassian JIRA | Russ Gould [Atlassian] | 10 months ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    h3. Summary Bamboo Cloud instances are not executing queued builds despite the availability of idle agents. Restarting the agents or canceling the build and re-executing occasionally clears this issue but it will eventually begin to reoccur. This has been noted impacting both elastic and remote agents. h3. Environment Bamboo Cloud h3. Steps to Reproduce Exact method for reproduction is unknown at this time. Bamboo Cloud instances with multiple agents and high levels of build activity are experiencing this issue with high frequency. The following error is occuring frequently in the Bamboo application logs when this behavior is present. {noformat} 2016-04-21 18:19:22.749954500 2016-04-21 18:19:22,749 INFO [scheduler_Worker-8] [ExpiryTickerImpl] Live expiry handlers: 17 2016-04-21 18:19:29.032352500 org.apache.activemq.transport.InactivityIOException: Channel was inactive (no connection attempt made) for too (>30000) long: blockingQueue_3328772 2016-04-21 18:19:29.032365500 at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91) 2016-04-21 18:19:29.032366500 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 2016-04-21 18:19:29.032366500 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 2016-04-21 18:19:29.032372500 at java.lang.Thread.run(Thread.java:745) {noformat} h3.Workaround (partial) Restarting the agents or canceling the build and re-executing occasionally clears this issue but it will eventually begin to reoccur.

    Atlassian JIRA | 10 months ago | Russ Gould [Atlassian]
    org.apache.activemq.transport.InactivityIOException: Channel was inactive (no connection attempt made) for too (>30000) long: blockingQueue_3328772 2016-04-21 18:19:29.032365500 at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)
  2. 0

    h3. Summary Bamboo Cloud instances are not executing queued builds despite the availability of idle agents. Restarting the agents or canceling the build and re-executing occasionally clears this issue but it will eventually begin to reoccur. This has been noted impacting both elastic and remote agents. h3. Environment Bamboo Cloud h3. Steps to Reproduce Exact method for reproduction is unknown at this time. Bamboo Cloud instances with multiple agents and high levels of build activity are experiencing this issue with high frequency. The following error is occuring frequently in the Bamboo application logs when this behavior is present. {noformat} 2016-04-21 18:19:22.749954500 2016-04-21 18:19:22,749 INFO [scheduler_Worker-8] [ExpiryTickerImpl] Live expiry handlers: 17 2016-04-21 18:19:29.032352500 org.apache.activemq.transport.InactivityIOException: Channel was inactive (no connection attempt made) for too (>30000) long: blockingQueue_3328772 2016-04-21 18:19:29.032365500 at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91) 2016-04-21 18:19:29.032366500 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 2016-04-21 18:19:29.032366500 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 2016-04-21 18:19:29.032372500 at java.lang.Thread.run(Thread.java:745) {noformat} h3.Workaround (partial) Restarting the agents or canceling the build and re-executing occasionally clears this issue but it will eventually begin to reoccur.

    Atlassian JIRA | 10 months ago | Russ Gould [Atlassian]
    org.apache.activemq.transport.InactivityIOException: Channel was inactive (no connection attempt made) for too (>30000) long: blockingQueue_3328772 2016-04-21 18:19:29.032365500 at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)

    Root Cause Analysis

    1. org.apache.activemq.transport.InactivityIOException

      Channel was inactive (no connection attempt made) for too (>30000) long: blockingQueue_3328772 2016-04-21 18:19:29.032365500 at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)

      at java.util.concurrent.ThreadPoolExecutor.runWorker()
    2. Java RT
      ThreadPoolExecutor$Worker.run
      1. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      2. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      2 frames