[jira] Commented: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout does not throw an exception

["Jim Gomes (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/AMQNET-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45338#action_45338 ] 

Jim Gomes commented on AMQNET-78:
---------------------------------

Chris, in your comment on 6 June 2008, you mention that you are binding to listenerContainer.SharedConnection.ExceptionListener.  This is not part of NMS, but rather sounds like Spring.NET.  If you are using Spring.NET, you should post your issue in their database so they can help you resolve the issue.  As for Apache NMS, I have not seen this reported issue.  There may be some kind of timeouts occurring within the Spring.NET connection pooling.

For now, I am going to mark this issue as won't fix, since it seems like the problem resides in a different software product.  Feel free to re-open it if I am mistaken.

> ActiveMQ v5 Idle Connection Timeout does not throw an exception
> ---------------------------------------------------------------
>
>                 Key: AMQNET-78
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-78
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>         Environment: Windows, JDK 1.6, ActiveMq version 5 (Stable), ActiveMQ.NET openwire client
>            Reporter: Demis Bellot
>            Assignee: Jim Gomes
>             Fix For: 1.1
>
>
> We are experiencing an issue when we have upgraded the ActiveMQ broker to the latest production version 5 where it appears that the broker is automatically disposing of a connection once it has been idle for long tim.
> We have a consumer that is listening on a topic, if the topic has not received a message for a long period of time (roughly 30mins) it appears that the connection is disposed of on the server (as seen in the JMX console) and the consumer will fail to receive any other messages sent to the topic after this time. This does not happen to consumers that are listening on more active topics (i.e. ones that receive messages every 5 minutes, etc).
> Unfortunately this idle connection timeout does not raise an exception when it is disposed of, so we have no way to know if the connection is dead so we can reconnect back to the broker.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.