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] | 8 months ago
  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 | 8 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 | 8 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)
  3. 0

    Reloading with a lot of needs causes exception on owner

    GitHub | 5 months ago | m0ru
    javax.jms.JMSException: Channel was inactive for too (>30000) long: tcp://192.168.124.6:61617
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    ServiceMix - User - Exceptions in servicemix

    nabble.com | 12 months ago
    org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long.
  6. 0

    603422 [AcitveMQ Connection Worker: tcp://localhost/127.0.0.1:61616] ERROR JMS Connection Service - exception occurred in JMS connection; restarting javax.jms.JMSException: Channel was inactive for too long. at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49) at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1638) at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1655) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98) at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98) at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143) at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:155) at org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:100) at org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:50) at org.apache.activemq.thread.Scheduler$SchedulerTimerTask.run(Scheduler.java:36) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) Caused by: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long. ... 5 more

    Apache's JIRA Issue Tracker | 9 years ago | Kevin W Edwards
    javax.jms.JMSException: Channel was inactive for too long.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    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