[
https://jira.jboss.org/jira/browse/JBMESSAGING-999?page=com.atlassian.jir...
]
Markus Lutum commented on JBMESSAGING-999:
------------------------------------------
Hi Tim!
Of course I can!
I reported this issue and so it was fixed in SP1. Currently we are using SP3 where this
startup retry is still working.
As I upgraded to CP04 this was not included!!
Then I also checked the sources at the branch 1_4 and there this issue also exist.
It all has to do with the direct lookup at the BridgeService class.
As I know in SP1 it was fixed by doing the lookup inside the Bridge itself so the retry
mechanism can take over this error.
In case of the Service fails to start there is no retry of course.
So simple merge the changes of 1.4.0GA to 1.4.0.SP1 to the branch and thats it :-)
I just looked at the revisions.
Compare 3163 to 3272 of the BridgeService and you will see....
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