activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Wiegand (JIRA)" <>
Subject [jira] Commented: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout does not throw an exception
Date Fri, 06 Jun 2008 17:04:00 GMT


Chris Wiegand commented on AMQNET-78:

To workaround this problem we use a timer that disconnects and reconnects every 10 minutes,
which also has the convenient benefit of redelivering any messages that we were unable to
process earlier (we use ClientAcknowledge mode in case our system's unable to process a message
at that time). Also, we find that if we bind to listenerContainer.SharedConnection.ExceptionListener
we do get an exception when the connection goes dead, although the server doesn't seem to
notice that it's gone on the queues page.

> ActiveMQ v5 Idle Connection Timeout does not throw an exception
> ---------------------------------------------------------------
>                 Key: AMQNET-78
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>         Environment: Windows, JDK 1.6, ActiveMq version 5 (Stable), ActiveMQ.NET openwire
>            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.

View raw message