[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1128) Message not routed from one node to node with only consumer.

[Mike Clark (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1128?page=all ]

Mike Clark closed JBMESSAGING-1128.
-----------------------------------

    Resolution: Done

No bug here:  jgroups configuration was the root cause of the behavior I was seeing.

> Message not routed from one node to node with only consumer.
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-1128
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1128
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>         Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database.
>            Reporter: Mike Clark
>         Assigned To: Tim Fox
>             Fix For: EAP 4.3 Integration
>
>
> In trying to reproduce behavior described in case 18885, I can reproduce the following:
> Start two instances of JBoss (ports-01 and ports-02 using the usual binding manager approach).  Deployed a simple MDB to ports-02; simply logs messages with INFO priority.  Deployed a simple MBean to both ports-01 and ports-02 that allows me to send TextMessage messages to the respective boxes from the JMX console.
> Messages sent to ports-02 are consumed by the MDB as expected.  Messages sent to ports-01 are not consumed unless ports-02 is shutdown (normal shutdown) and restarted.  The MDB on ports-02 will consume the messages queued to ports-01 regardless of whether ports-01 is up or not (ports-01 shutdown cleanly).  Messages sent to ports-01 are, of course, seen in the database as soon as they are submitted (I'm using PERSISTENT delivery mode.)
> Both instances were created from a clean "all" instance.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira