activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-212) Add an Inactivity Monitor to the Transports layer to timeout broken connections
Date Wed, 23 Dec 2009 20:55:41 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56643#action_56643
] 

Timothy Bish commented on AMQNET-212:
-------------------------------------

Committed several fixes to the InactivityMonitor code and it seems to work pretty well now.
 The monitor is disabled by default for now, to enable add option transport.UseInactivityMonitor=true
to your connection URI.


> Add an Inactivity Monitor to the Transports layer to timeout broken connections
> -------------------------------------------------------------------------------
>
>                 Key: AMQNET-212
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-212
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ
>    Affects Versions: 1.2.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 1.2.0
>
>         Attachments: InactivityMonitor.diff
>
>
> In order to more quickly detect broken connections between client and broker the NMS.AcitveMQ
client needs to add an InactivityMonitor transport filter that deals with the keep alive messages
that allow for detection of broken sockets.  Right now a broken connection such as one that
occurs when a cable is pulled isn't detected and the client can sit idle instead of failing
over if there's no outbound messages to trigger a failed write.

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