Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-5471

[LTS] Broker does not auto create a queue when deploying a MDB

    XMLWordPrintable

Details

    • Enhancement
    • Status: Closed
    • Major
    • Resolution: Done
    • AMQ 7.8.2.GA
    • AMQ 7.8.3.CR1
    • broker-core
    • None

    Description

      A broker with following address settings

      <address-setting match="#">
      				<dead-letter-address>DLQ</dead-letter-address>
      				<expiry-address>ExpiryQueue</expiry-address>
      				<redelivery-delay>0</redelivery-delay>
      				<!-- with -1 only the global-max-size is in use for limiting -->
      				<max-size-bytes>-1</max-size-bytes>
      				<message-counter-history-day-limit>10</message-counter-history-day-limit>
      				<address-full-policy>PAGE</address-full-policy>
      				<auto-create-queues>true</auto-create-queues>
      				<auto-create-addresses>true</auto-create-addresses>
      				<auto-create-jms-queues>true</auto-create-jms-queues>
      				<auto-create-jms-topics>true</auto-create-jms-topics>
      				<auto-delete-queues>false</auto-delete-queues>
      				<auto-delete-addresses>false</auto-delete-addresses>
      			</address-setting>
      

      does not auto create JMS queue when deploying a MDB to EAP server.
      I can see an exception

      ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ229017: Queue inQueue does not exist]
      

      when stepping through RA code in the debugger when deploying MDB.
      The broker auto creates JMS TOPIC when a MDB is deployed that listens on JMS topic.

      Attachments

        Issue Links

          Activity

            People

              rhn-support-jbertram Justin Bertram
              dbruscin Domenico Francesco Bruscino
              Roman Vais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: