Bug 1014095

Summary:	Do sanity checks for dead letter and expiry address settings during server startup
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Martin Svehla <msvehla>
Component:	HornetQ	Assignee:	Clebert Suconic <csuconic>
Status:	CLOSED EOL	QA Contact:	Miroslav Novak <mnovak>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	mnovak, msvehla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:45:09 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1014103

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.