Bug 1014095 - Do sanity checks for dead letter and expiry address settings during server startup
Summary: Do sanity checks for dead letter and expiry address settings during server st...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
URL:
Whiteboard:
Depends On:
Blocks: 1014103
TreeView+ depends on / blocked
 
Reported: 2013-10-01 12:12 UTC by Martin Svehla
Modified: 2019-08-19 12:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:45:09 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)

Description Martin Svehla 2013-10-01 12:12:52 UTC 
HornetQ 2.3.8.Final

Right now, when user defines dead letter and/or expiry address in address-settings, HornetQ doesn't do any check whether these queues exist or not. User only gets WARN in log when some message hits max-delivery-attempts limit and HornetQ drops it because of non-existent dead letter/expiry destination.

While user can deploy dead letter/expiry queue later without server restart and HornetQ will start routing lost messages correctly, it would be nice to do a check during server start and log WARN message in case these addresses don't exist.
Note You need to log in before you can comment on or make changes to this bug.