[
https://jira.jboss.org/jira/browse/JBMESSAGING-1661?page=com.atlassian.ji...
]
Art Plata commented on JBMESSAGING-1661:
----------------------------------------
I got this working by copying the source for Bridge.java in 1.4.4, to 1.4.3. The Remote
cluster receives messages fine, but now we're running into an issue with messages
getting stuck when we try to test fail-over on the remote cluster. This looks like a
separate issue. Should i open a new bug?
Messages in JBoss 5.1 that use bridging get stuck in a devlivering
mode and are not sent to the remote cluster
--------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1661
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1661
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.3.GA
Environment: Linux -- JBoss 5.1 GA / JBM 1.4.3GA / Remoting 2.5.1
Reporter: Peter Crossley
Assignee: Howard Gao
Fix For: 1.4.5.GA
A Message bridge between to clusters will get in to a state where the messages will not
be picked up by the bridge on the topic/queue and remain in the "delivering"
counter until the bridge is restarted via the JMX console or by restarting the Jboss
instance.
I attempted to use JBM 1.4.4 which has a fix (JBMESSAGING-1456) that seems to be the same
issue, though do to the difference in the remoting I cannot use the 1.4.4 GA release.
Can we get the fixes that were applied to the 1.4.4 release in a usable build for JBoss
AS 5.1
--
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