activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-250) Implement an Inactivity Monotir Transport filter for use on Transport that are used by the Failover Transport
Date Mon, 16 Nov 2009 22:33:52 GMT

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


Mime
View raw message