-
Enhancement
-
Resolution: Done
-
Major
-
None
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.
- clones
-
ENTMQBR-5471 [LTS] Broker does not auto create a queue when deploying a MDB
-
- Closed
-
- is incorporated by
-
JBEAP-21308 (7.4.z) Upgrade Artemis from 2.16.0.redhat-00022 to 2.16.0.redhat-00032
-
- Closed
-
