javax.jms.JMSException

Channel was inactive for too long.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web325

  • via Apache's JIRA Issue Tracker by Kevin W Edwards, 1 year ago
    Channel was inactive for too long.
  • Channel was inactive for too long.
  • via Apache's JIRA Issue Tracker by Kevin W Edwards, 11 months ago
    Channel was inactive for too long.
  • Stack trace

    • 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

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.