[
https://issues.apache.org/jira/browse/AMQ-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-3257.
-----------------------------
Resolution: Incomplete
Need to supply some additional information like broker logs and configuration.
Not enough here to determine why the inactivity monitor is kicking in.
> Channel was inactive for too long exception occurs with service mix clustering
> ------------------------------------------------------------------------------
>
> Key: AMQ-3257
> URL: https://issues.apache.org/jira/browse/AMQ-3257
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Environment: Solaris
> Reporter: GowthamB
>
> We are getting the following JMS exceptions in our production environment.
> While processing transactions suddenly one of the servers goes down after the
> occurrence of following exceptions. Also, Currently we are restarting the
> servers to bring up the application. This exception is occurring at least
> once in a day. It will be great if you can advise on how to suppress these
> exceptions.
>
> javax.jbi.messaging.MessagingException:
> org.apache.activemq.ConnectionFailedException: The JMS connection has failed:
> Channel was inactive for too long
> org.apache.activemq.transport.InactivityIOException: Channel was inactive for
> too long
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
