You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/05/14 10:43:27 UTC
[jira] Resolved: (AMQ-2511) Regression: Inactivity monitor does not
time out stale connections.
[ https://issues.apache.org/activemq/browse/AMQ-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-2511.
-----------------------------
Fix Version/s: 5.3.2
Resolution: Fixed
fix is also on 5.3 branch
> Regression: Inactivity monitor does not time out stale connections.
> -------------------------------------------------------------------
>
> Key: AMQ-2511
> URL: https://issues.apache.org/activemq/browse/AMQ-2511
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 5.4.0, 5.3.2
>
>
> The fix @ AMQ-2088 cause a the Inactivity Monitor to regress.
> Now when a socket is waiting to read the next message, or is in the middle of receiving the next message it sets a flag that disable the inactivity monitor from timing out the connection. The problem is that if the connection gets hung, then it won't time out since the flag is set.
> I think a better approach would be for the wireformat to expose a counter which is incremented as data is read.
> That way between inactivity check intervals the inactivity monitor can check to see if that value has changed since it's last check.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.