activemq-dev mailing list archives

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

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

Jim Gomes resolved AMQNET-78.
-----------------------------

    Resolution: Cannot Reproduce

I ran a long-running test to try and reproduce the original problem.  I connected several
consumers to different topics.  Some topics were active, and one was less active.  I sent
one message to the less active topic, and it was received by the consumer.  I then left all
consumers over night for over 10 hours.  In the morning, I saw that all consumers appeared
to be active.  The active consumers were still receiving messages.  I then sent another message
to the less active consumer, and it received the message.  This shows that the consumer was
not disconnected by the broker.  I am using ActiveMQ 5.1.0 on Windows.

> 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