[
https://jira.jboss.org/jira/browse/JBMESSAGING-999?page=com.atlassian.jir...
]
Tim Fox commented on JBMESSAGING-999:
-------------------------------------
> I didn't verify the 1.4 before starting the work, as I can
see the Bridge.java (and BridgeService) can not tolerate the case where the target or the
source is not available when the Bridge Service is deployed and started.
Hmm, I don't know where you got that idea from.
The code should already cope with the case where target or source is not available before
it is started. Like I said before, see StartupFailureHandler. If there is a bug in that
please be more specific. But it certainly should work and did work before.
Bridge startup should retry if remote destinations are not available
--------------------------------------------------------------------
Key: JBMESSAGING-999
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-999
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assignee: Howard Gao
Priority: Minor
Fix For: 1.4.0.SP3.CP05, 1.4.2.GA
Currently the bridge only retries connection creation after startup.
If remote provider is not available at startup it will fail to start.
We should change this by institutiing a retry at startup too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira