Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Apache's JIRA Issue Tracker by Kevin W Edwards, 1 year ago
Channel was inactive for too long.
via Apache's JIRA Issue Tracker by Kevin W Edwards, 2 years ago
Channel was inactive for too long.
via activemq-dev by bill richard, 2 years ago
Channel was inactive for too long: /10.61.0.212:61616
via activemq-dev by bill richard, 2 years ago
Channel was inactive for too long: /10.61.0.212:61616
via Stack Overflow by Sam
, 2 years ago
Channel was inactive for too long: localhost/127.0.0.1:61616
via Stack Overflow by shuttsy
, 2 years ago
Channel was inactive for too (>30000) long: jmsserver/xxx.xx.xx.xxx:61616
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long.	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)