javax.jms.JMSException: Channel was inactive for too long.

Apache's JIRA Issue Tracker | Kevin W Edwards | 9 years ago
  1. 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.
  2. 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.
  3. 0

    ServiceMix - User - Exceptions in servicemix

    nabble.com | 12 months ago
    org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [AMQ-1863] org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long - ASF JIRA

    apache.org | 11 months ago
    java.lang.Exception: org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is org.apache.activemq.ConnectionFailedException: The JMS connection has failed: Channel was inactive for too long.; nested exception is org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long.
  6. 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

    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 for too long.

      at org.apache.activemq.transport.InactivityMonitor.readCheck()
    2. AMQ HTTP
      InactivityMonitor$1.run
      1. org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:100)
      2. org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:50)
      2 frames
    3. ActiveMQ :: Core
      Scheduler$SchedulerTimerTask.run
      1. org.apache.activemq.thread.Scheduler$SchedulerTimerTask.run(Scheduler.java:36)
      1 frame
    4. Java RT
      TimerThread.run
      1. java.util.TimerThread.mainLoop(Unknown Source)
      2. java.util.TimerThread.run(Unknown Source)
      2 frames