activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Demis Bellot (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout does not throw an exception
Date Wed, 03 Sep 2008 18:05:52 GMT

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

Demis Bellot commented on AMQNET-78:
------------------------------------

Jim,

Do you mind sending me a link to the integration test you ran so I can let you know if its
a valid test that would've caught the problem. We have deployed a work around solution for
every listener to ping a status update every 5 mins, which has an added benefit of notifying
the status of the listener as well as keeping the connection open.

Also we are also very short of tests on the c#/.NET libraries so the more we have the better.
You would obviously want to keep Integration tests like this separate from other slow running
tests, however it would be still nice to have in the source tree.

> 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.


Mime
View raw message