activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (Updated) (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Updated] (AMQNET-370) Channel was inactive for too long does not recover
Date Wed, 29 Feb 2012 17:51:58 GMT

     [ https://issues.apache.org/jira/browse/AMQNET-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jim Gomes updated AMQNET-370:
-----------------------------

    Attachment: nms-inactivityexception.log

I have attached a log snippet of an Inactivity exception that I had from my client last night.
 This is using the latest NMS.ActiveMQ 1.5.x branch build.  After recovery, I am able to send/receive
messages without any problems.  Here is my connection string:

activemq:failover:(tcp://activemqhost:61616)?transport.StartupMaxReconnectAttempts=3&nms.PrefetchPolicy.All=50

Can you compare this log output with what your client logs?  Maybe we can find out where the
difference is.
                
> 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
>         Attachments: nms-inactivityexception.log
>
>
> 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

        

Mime
View raw message