org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Channel was inactive for too (>30000) long: tcp://192.168.10.144:61617

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

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via uima-user by Satya Nand Kanodia, 1 year ago
Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Channel was inactive for too (>30000) long: tcp://192.168.10.144:61617
via incubator-uima-user by Satya Nand Kanodia, 1 year ago
Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Channel was inactive for too (>30000) long: tcp://192.168.10.144:61617
via uima-user by Satya Nand Kanodia, 1 year ago
Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Channel was inactive for too (>30000) long: tcp://192.168.10.144:61617
via cisco.com by Unknown author, 2 years ago
Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
via GitHub by tdiesler
, 1 year ago
Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: There is no queue with name OrdersQueue
via activemq-users by Michele, 1 year ago
Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Java heap space
org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Channel was inactive for too (>30000) long: tcp://192.168.10.144:61617
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.