Channel was inactive for too long does not recover
--------------------------------------------------
Key: AMQNET-370
URL: https://issues.apache.org/jira/browse/AMQNET-370
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.5.1
Environment: Windows .NET
Server is 5.4.2 on Windows server 2008.
Reporter: Matthew Good
Assignee: Jim Gomes
I see many of these bugs about "Channel was inactive for too long" and they all
get closed as incomplete because no one can determine the cause. So I won't
ask for that.
The biggest problem here isn't that this one call fails, it's that the client
does not recover or failover after this occurs so once this happens once, it
continues for every request until the client application is restarted. In a
production environment, we can't be restarting services all the time.
For services that are just listening, they stop receiving messages, no error is
raised so we don't even know that it is in a bad state.
So please fix the failover to re-establish the connection(s) or whatever it
must do so that the next call works since that is the intention of the failover
protocol.
Apache.NMS.ActiveMQ.IOException: Channel was inactive for too long:
tcp://ipc-393-pstg-05.ipcommerce.com:61616/
at Apache.NMS.ActiveMQ.Connection.Oneway(Command command)
at Apache.NMS.ActiveMQ.Session..ctor(Connection connection, SessionId
sessionId, AcknowledgementMode acknowledgementMode)
at Apache.NMS.ActiveMQ.Connection.CreateAtiveMQSession(AcknowledgementMode
ackMode)
at Apache.NMS.ActiveMQ.Connection.CreateSession(AcknowledgementMode
sessionAcknowledgementMode)
--
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
