You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2008/03/06 21:44:35 UTC
[jira] Created: (AMQ-1613) Inactivity monitor blocks trying to
close out a Failover transport that is in the middle of send.
Inactivity monitor blocks trying to close out a Failover transport that is in the middle of send.
-------------------------------------------------------------------------------------------------
Key: AMQ-1613
URL: https://issues.apache.org/activemq/browse/AMQ-1613
Project: ActiveMQ
Issue Type: Bug
Reporter: Hiram Chirino
The net affect of this is that clients don't get reconnected within the inactivity monitor configured time. They have to wait for the OS socket to notice the connection failure to reconnect. This in effect is making the inactivity monitor in-effective for heavily used connections.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1613) Inactivity monitor blocks trying to
close out a Failover transport that is in the middle of send.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved AMQ-1613.
--------------------------------
Fix Version/s: 5.1.0
Resolution: Fixed
Fixed.
> Inactivity monitor blocks trying to close out a Failover transport that is in the middle of send.
> -------------------------------------------------------------------------------------------------
>
> Key: AMQ-1613
> URL: https://issues.apache.org/activemq/browse/AMQ-1613
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Hiram Chirino
> Fix For: 5.1.0
>
>
> The net affect of this is that clients don't get reconnected within the inactivity monitor configured time. They have to wait for the OS socket to notice the connection failure to reconnect. This in effect is making the inactivity monitor in-effective for heavily used connections.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.