Bug 1320753 - Destination blocked warning although PAGE address full policy being used
Summary: Destination blocked warning although PAGE address full policy being used
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.6
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: Yong Hao Gao
QA Contact: Miroslav Novak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-23 23:40 UTC by Tyronne Wickramarathne
Modified: 2019-10-10 11:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-24 02:47:09 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.