[
https://issues.apache.org/jira/browse/AMQ-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004413#comment-13004413
]
Gil Guo commented on AMQ-3171:
------------------------------
I met the same issue. Please see below for the error message:
SEVERE: Channel was inactive for too long: localhost/127.0.0.1:61616
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)
org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1216)
org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1208)
org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1643)
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:227)
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:269)
> Channel was inactive for too long
> ---------------------------------
>
> Key: AMQ-3171
> URL: https://issues.apache.org/jira/browse/AMQ-3171
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Environment: Centos 5.3
> Reporter: Kaminiecki
> Attachments: activemq.log, wrapper.log
>
>
> I have a problem with connection when client works without failover and work
> longer than 1day after that error occur Channel was inactive for to long. Any
> close and dispose inside application and start connection doesnt give
> anything only one solution is restart all applications.
> I attach logs from server. It standalone maschine, single instance, default
> configuration.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
