Bug 1320753

Summary:	Destination blocked warning although PAGE address full policy being used
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Tyronne Wickramarathne <tywickra>
Component:	HornetQ	Assignee:	Yong Hao Gao <hgao>
Status:	CLOSED WONTFIX	QA Contact:	Miroslav Novak <mnovak>
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.4.6	CC:	csuconic, msvehla
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-24 02:47:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Tyronne Wickramarathne 2016-03-23 23:40:30 UTC

Description of problem:

HornetQ throws the following address blocked warning message despite PAGE address full policy being used. 

<snip>
HQ214024: Destination address=jms.topic.MyTopic is blocked. If the system is configured to block make sure you consume messages on this configuration.
</snip>

This has occurred under heavy load, due to long GC pauses. This warning message is confusing and misleading, specially when one has already configured PAGE address full policy. 

Could it be possible to change this WARN message to say that it could also occur under heavy load due to long GC pauses please?


Version-Release number of selected component (if applicable):
JBoss-EAP-6.4.6 
HornetQ-2.3.25.SP8

Comment 2 Yong Hao Gao 2016-03-24 02:34:18 UTC

Hey,

GC is a common issue and affects the whole application, not just the specific sending in this case. So I don't think it's proper to add this warning to this log.
Users who are getting frequent long time GC have options to deal with it:

1) enlarge callTimeout to a suitable value so it won't get timed out in case GC happens.

2) using non-blocking send.

I'll reject this based on above reason.

Thanks
Howard