You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2009/06/22 16:42:35 UTC
[jira] Created: (AMQCPP-250) Implement an Inactivity Monotir
Transport filter for use on Transport that are used by the Failover
Transport
Implement an Inactivity Monotir Transport filter for use on Transport that are used by the Failover Transport
-------------------------------------------------------------------------------------------------------------
Key: AMQCPP-250
URL: https://issues.apache.org/activemq/browse/AMQCPP-250
Project: ActiveMQ C++ Client
Issue Type: Improvement
Components: Decaf, Transports
Affects Versions: 3.0
Reporter: Timothy Bish
Assignee: Timothy Bish
Fix For: 3.1
Now that the Failover Transport is in place we need an Inactivity Monitor to wrap around transports such as TCP to detect long periods of inactivity and failures due to TCP connections that are otherwise not detected as broken such as a plug pull or switch failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-250) Implement an Inactivity Monotir
Transport filter for use on Transport that are used by the Failover
Transport
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55545#action_55545 ]
Timothy Bish commented on AMQCPP-250:
-------------------------------------
Added several fixes which have improved the inactivity monitoring code. Rev. 881778
> Implement an Inactivity Monotir Transport filter for use on Transport that are used by the Failover Transport
> -------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-250
> URL: https://issues.apache.org/activemq/browse/AMQCPP-250
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: Decaf, Transports
> Affects Versions: 3.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 3.1
>
> Original Estimate: 4 weeks
> Time Spent: 1 day
> Remaining Estimate: 3 weeks, 5 days
>
> Now that the Failover Transport is in place we need an Inactivity Monitor to wrap around transports such as TCP to detect long periods of inactivity and failures due to TCP connections that are otherwise not detected as broken such as a plug pull or switch failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-250) Implement an Inactivity Monotir
Transport filter for use on Transport that are used by the Failover
Transport
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55476#action_55476 ]
Timothy Bish commented on AMQCPP-250:
-------------------------------------
I've checked in the complete but not very well tested InactivityMonitor class along with changes to enable its usage. Unit testing looks good so far, however more tests need to be added and some real testing with cable pulls etc needs to be done.
Users are welcome to check out SVN rev. 881016 and give it a try. Test reports welcome.
> Implement an Inactivity Monotir Transport filter for use on Transport that are used by the Failover Transport
> -------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-250
> URL: https://issues.apache.org/activemq/browse/AMQCPP-250
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: Decaf, Transports
> Affects Versions: 3.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 3.1
>
> Original Estimate: 4 weeks
> Time Spent: 1 day
> Remaining Estimate: 3 weeks, 5 days
>
> Now that the Failover Transport is in place we need an Inactivity Monitor to wrap around transports such as TCP to detect long periods of inactivity and failures due to TCP connections that are otherwise not detected as broken such as a plug pull or switch failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work logged: (AMQCPP-250) Implement an Inactivity Monotir
Transport filter for use on Transport that are used by the Failover
Transport
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36841 ]
Timothy Bish logged work on AMQCPP-250:
---------------------------------------
Author: Timothy Bish
Created on: 09/Jul/09 06:38 AM
Start Date: 09/Jul/09 06:37 AM
Worklog Time Spent: 1 day
Work Description: Started work on additions to Decaf lib to support timers for use in the Inactivity Monitor class.
Issue Time Tracking
-------------------
Time Spent: 1 day
Remaining Estimate: 3 weeks, 5 days (was: 4 weeks)
> Implement an Inactivity Monotir Transport filter for use on Transport that are used by the Failover Transport
> -------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-250
> URL: https://issues.apache.org/activemq/browse/AMQCPP-250
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: Decaf, Transports
> Affects Versions: 3.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 3.1
>
> Original Estimate: 4 weeks
> Time Spent: 1 day
> Remaining Estimate: 3 weeks, 5 days
>
> Now that the Failover Transport is in place we need an Inactivity Monitor to wrap around transports such as TCP to detect long periods of inactivity and failures due to TCP connections that are otherwise not detected as broken such as a plug pull or switch failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQCPP-250) Implement an Inactivity Monotir
Transport filter for use on Transport that are used by the Failover
Transport
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQCPP-250.
---------------------------------
Resolution: Fixed
Resolved in SVN Rev. 883495
> Implement an Inactivity Monotir Transport filter for use on Transport that are used by the Failover Transport
> -------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-250
> URL: https://issues.apache.org/activemq/browse/AMQCPP-250
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: Decaf, Transports
> Affects Versions: 3.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 3.1
>
> Original Estimate: 4 weeks
> Time Spent: 1 day
> Remaining Estimate: 3 weeks, 5 days
>
> Now that the Failover Transport is in place we need an Inactivity Monitor to wrap around transports such as TCP to detect long periods of inactivity and failures due to TCP connections that are otherwise not detected as broken such as a plug pull or switch failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.