Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1364000911.1220397233158.JavaMail.jira@brutus>
Date: Tue, 2 Sep 2008 16:13:53 -0700 (PDT)
From: "Jim Gomes (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
 does not throw an exception
In-Reply-To: <12990870.1202396620988.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Jim Gomes updated AMQNET-78:
----------------------------

    Comment: was deleted

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