Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-13581

The multicast queue stats are not correct

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 21.0.0.Beta1, 21.0.0.Final
    • None
    • None
    • None
    • Hide

      1. Start a AMQ 7.6 instance.
      2. Use the standalone.xml I attached, to start the EAP 7.3

      and use the sample code 

      https://github.com/jboss-developer/jboss-eap-quickstarts/blob/7.3.x/helloworld-mdb/README.adoc

      to deploy the app :

      mvn clean install wildfly:deploy

      then visit the url

      http://localhost:8080/helloworld-mdb/HelloWorldMDBServletClient?topic

      3. in the AMQ 7.6 , run command 

      ./artemis queue stat

      will find out an additional multicast queue was created.

      Show
      1. Start a AMQ 7.6 instance. 2. Use the standalone.xml I attached, to start the EAP 7.3 and use the sample code https: //github.com/jboss-developer/jboss-eap-quickstarts/blob/7.3.x/helloworld-mdb/README.adoc to deploy the app : mvn clean install wildfly:deploy then visit the url http: //localhost:8080/helloworld-mdb/HelloWorldMDBServletClient?topic 3. in the AMQ 7.6 , run command ./artemis queue stat will find out an additional multicast queue was created.

    Description

      I am using EAP 7.3 to connect to the external AMQ 7.6, I am using MDB to consume messages from a topic: jms.topic.HelloWorldMDBTopic, I found there is an additional multicast queue was created.
      eg:
      The topic which works should be this one. 

      |d9684721-79ff-48d1-949f-310253f26dcc|jms.topic.HelloWorldMDBTopic|15             |0             |10             |0                |10             |0               |MULTICAST    |

      but I found another multicast queue was created too and there are messages there, not being consumed by the MDB. This will leave the AMQ in a danger state.

      |jms.topic.HelloWorldMDBTopic|jms.topic.HelloWorldMDBTopic|0              |10            |10             |0                |0              |0               |MULTICAST    |

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19653 The multicast queue stats are not correct

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-13882 StartException with "AMQ229204: Address already exists" on existing multicast queue creation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              ehugonne1@redhat.com Emmanuel Hugonnet
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: