Warn if there is no resource bound for address-settings expiry and dead-letter a

Solution Unverified - Updated -

Issue

  • We saw the following in our logs, but apparently was fixed in WindFly 8.1.0.Final. Has this issue been fixed in JBoss-EAP-6 ?
JBAS011618: There is no resource matching the expiry-address jms.queue.ExpiryQueue for the address-settings #, 
expired messages from destinations matching this address-setting will be lost!
JBAS011619: There is no resource matching the dead-letter-address jms.queue.DLQ for the address-settings #, 
undelivered messages from destinations matching this address-setting will be lost!

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.3.0
    • 6.3.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.