server.log shows warning about no Dead Letter Address for an MDB

Solution Unverified - Updated -

Issue

  • When a Save is made to the database from the application. The save process should try to add things to the common queue mentioned above but instead fails saying it was unable to find a queue specific to the MDB that does not exist. Here's my address configuration :
<address-setting match="java:/topic/myCustomTopic">
               <dead-letter-address>jms.queue.myCustomTopicDLQ</dead-letter-address>
               <expiry-address>jms.topic.myCustomTopicExpiryQueue</expiry-address>
               <redelivery-delay>0</redelivery-delay>
               <max-delivery-attempts>3</max-delivery-attempts>
               <max-size-bytes>10485760</max-size-bytes>
               <page-size-bytes>2097152</page-size-bytes>
               <address-full-policy>PAGE</address-full-policy>
               <message-counter-history-day-limit>10</message-counter-history-day-limit>
</address-setting>

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content