[
https://jira.jboss.org/jira/browse/JBMESSAGING-1543?page=com.atlassian.ji...
]
Alexei Sadovnikov commented on JBMESSAGING-1543:
------------------------------------------------
What I see is: when the Bridge#start() fails to open JMS connections then the
BatchTimeChecker is not created, later when StartupFailureHandler succeeds it only starts
the JMS connections but not the BatchTimeChecker. If the value maxbatchsize is set to 1
then BatchTimeChecker is not needed - all messages are bridged immediately.
This happens on JBM 1.4.2.GA-SP1.
Message Bridge does not start if the first attempt failed
---------------------------------------------------------
Key: JBMESSAGING-1543
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1543
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3, 1.4.2.GA.SP1
Environment: Windows XP, Java 1.5.0_17, JBoss AS 4.2.3.GA, JBossRemoting
2.5.0.SP2
Reporter: Alexei Sadovnikov
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
The server A sends messages to the queue QA. A message bridge is deployed on the server
B, it reads messages from QA and sends them to the queue QB on the server B. If we start
the server A first and then the server B then the bridge works properly. If we start the
server B first, the bridge fails to start (as expected), then we start the server A. The
bridge detects that A is running and the source connection (the message "Succeeded in
connecting to servers" is printed), but it does not deliver any messages.
The same happens if messages are sent to a queue on the server B and should be bridged to
a queue on the server A.
--
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