1 Reply Latest reply on Jan 8, 2009 9:02 AM by Carlo de Wolf

    Message delivered to wrong endpoint

    Carlo de Wolf Master

      Given the following scenario:
      1. An EJB3 Consumer Bean is tied to queue/mdbtest
      2. It fails to deactivate the endpoint (unrelated problem)
      3. queue/mdbtest is undeployed
      4. A MDB Bean comes up which wants to attach to queue/inflowmdbtest, but that one isn't there (yet) so it goes down again
      5. queue/inflowmdbtest comes up
      6. Client connects to queue/inflowmdbtest and starts sending messages
      7. The messages end up into the ConsumerContainer from step #1

      For the moment it can be reproduced by running EJB3s consumer and jca/inflowmdb tests in sequence.

        • 1. Re: Message delivered to wrong endpoint
          Carlo de Wolf Master

          Ah, the bean name is the same, while the JNDI name is not.

          <?xml version="1.0" encoding="UTF-8"?>
          <server>
           <mbean code="org.jboss.mq.server.jmx.Queue"
           name="jboss.mq.destination:service=Queue,name=queuetest">
           <attribute name="JNDIName">queue/inflowmdbtest</attribute>
           <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
           </mbean>
          </server>
          <?xml version="1.0" encoding="UTF-8"?>
          <server>
           <mbean code="org.jboss.mq.server.jmx.Queue"
           name="jboss.mq.destination:service=Queue,name=queuetest">
           <attribute name="JNDIName">queue/mdbtest</attribute>
           <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
           </mbean>
          </server>