[
http://jira.jboss.com/jira/browse/JBMESSAGING-898?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-898:
---------------------------------------------
Summary of changes:
Testsuite:
Added a testsuite on graveyard (a test that would kill server0... what would invalidate
the test run)
Added ClusteredConnectionFactoryTest, and also added poisoning support for
ConnectionFactory
(Adding poisoning required to expose serverPeer on ServerConnectionFactoryEndpoint)
Implementation:
Protected the connection creation in a loop, and doing retries until a max is reached.
Testing connection/IO failures on getClientAOPConfig, retrying on any delegates. (notice
that a failure on getClientAOPConfig is expected to be a rare event, as this is executed
only once)
Connection factory is not protected for failover
------------------------------------------------
Key: JBMESSAGING-898
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-898
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.CR1
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.2.0.GA
ConnectionFactory has 3 methods:
createConnectionDelegate
getIDBlock
getClientAOPConfig
if a failure occurs when one if this invoked, then the invocation fails. I.e. failover is
not transparent.
We need to catch and retry on the next cf in the list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira