[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failover analysis

[clebert.suconic@jboss.com]

My comments regarding the WIKI page:

>>2. Failure detected when sending a new invocation into the server

For new connections, Remoting will mask any IOException as org.jboss.remoting.somewhere.CannotConnectException.

>>3. Failure detected during an in-flight invocation

On this case you get an IOException indeed.


>> Failure Handling

"Ovidiu on Wiki Page" wrote : If there are active threads traversing the valve at the moment when "close" command arrives, those threads must be interrupted and put to wait until the valve opens again

There is no way to interrupt those threads, but on the event of a failure, all of the inflight invocations are going to fail at the same time, and all of them will capture the failure trying to close the valve at the same time.


This scenario is already implemented on Clebert_Third_Failover Branch.

The is a slightly differences on the way implemented:

- I only have one valve, so there is no recursivety on closing the valve.
- There is no need for the "command center" I guess, since a call on performFailover on ConnectionDelegate is already equivalent to "a failure has happened".



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999058#3999058

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999058