You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Demis Bellot (JIRA)" <ji...@apache.org> on 2008/02/07 16:03:40 UTC
[jira] Created: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
does not throw an exception
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: James Strachan
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.
[jira] Commented: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
does not throw an exception
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42141#action_42141 ]
Jim Gomes commented on AMQNET-78:
---------------------------------
It may be possible to receive notification of connection timeout via the notification topics. However, this raises the question of what happens if the consumer waiting on the notification topic gets kicked off? "Who watches the watchers?"
> 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: James Strachan
> 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.
[jira] Commented: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
does not throw an exception
Posted by "Demis Bellot (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
does not throw an exception
Posted by "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.
[jira] Updated: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
does not throw an exception
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
does not throw an exception
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
does not throw an exception
Posted by "Chris Wiegand (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43305#action_43305 ]
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: 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.
[jira] Issue Comment Edited: (AMQNET-78) ActiveMQ v5 Idle
Connection Timeout does not throw an exception
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45358#action_45358 ]
semog edited comment on AMQNET-78 at 9/3/08 11:15 AM:
----------------------------------------------------------
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.2 SNAPSHOT on Windows.
was (Author: semog):
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.
[jira] Assigned: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout
does not throw an exception
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes reassigned AMQNET-78:
-------------------------------
Assignee: Jim Gomes (was: James Strachan)
> 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.