[
https://jira.jboss.org/jira/browse/JBMESSAGING-999?page=com.atlassian.jir...
]
Tim Fox commented on JBMESSAGING-999:
-------------------------------------
Markus. the only differences I can see in BridgeService between 1.4.0.SP3_CP03 and
1.4.0.SP3_CP04 is:
---
BridgeService.java (.../JBossMessaging_1_4_0_SP3_CP03/src/main/org/jboss/jms/server/bridge/BridgeService.java) (revision
5536)
+++
BridgeService.java (.../JBossMessaging_1_4_0_SP3_CP04/src/main/org/jboss/jms/server/bridge/BridgeService.java) (revision
5536)
@@ -351,6 +351,8 @@
destCff= new JNDIConnectionFactoryFactory(targetProps, targetCFRef);
}
+ bridge.setName(serviceName.getCanonicalName());
+
bridge.setSourceConnectionFactoryFactory(sourceCff);
bridge.setDestConnectionFactoryFactory(destCff);
The svn command I used is:
svn diff
https://svn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_0_SP3_CP03/...
https://svn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_0_SP3_CP04/...
That change is accounted for by this JIRA:
https://jira.jboss.org/jira/browse/JBMESSAGING-1407
I don't see any other changes.
I guess you are looking in a different place. Can you be more specific as to where.
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