[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-999) Bridge startup should retry if remote destinations are not available
Howard Gao (JIRA)
jira-events at lists.jboss.org
Wed Dec 17 11:42:55 EST 2008
[ https://jira.jboss.org/jira/browse/JBMESSAGING-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12443172#action_12443172 ]
Howard Gao commented on JBMESSAGING-999:
----------------------------------------
Hi Tim and Markus,
I compared the Bridge.java of Branch_1_4 and tag SP1, the major difference is only in the method AddMessageIDInHeader(), where the JMSX header check is removed in Branch_1_4, other diffs include added a name attribute and log changes. (I use a tool called Kompare to compare the two versions).
So I believe if SP1 works, then it should work still now. If it doesn't work now, it should not work in SP1.
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.
I'll do a test before make any change to confirm the real state of the case.
> 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
More information about the jboss-jira
mailing list