Bug 1428338

Summary: [GSS](6.4.z) HornetQ Invalid Type exception handling improvements
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Shaun Appleton <sappleto>
Component: HornetQAssignee: Yong Hao Gao <hgao>
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.4.11CC: bmaxwell, csuconic, hrydmark, msvehla, pmackay, rnetuka, tom.ross, tywickra
Target Milestone: CR1   
Target Release: EAP 6.4.15   
Hardware: Unspecified   
OS: Unspecified   
URL: https://github.com/hornetq/hornetq/commit/7bde08c2d5b4c18c0fb61807b01f1ab078772502
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1435595 (view as bug list) Environment:
Last Closed: 2017-05-19 08:04:11 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1435595, 1419353, 1435783    

Description Shaun Appleton 2017-03-02 10:58:47 UTC 
Description of problem:
When a customer sees invalid Type -84 they sometimes get an OOME


Version-Release number of selected component (if applicable):
hornetq-core-client-2.3.25.SP14-redhat-1

How reproducible:
rarely

Steps to Reproduce:
none 

Actual results:
OOME occurs

Expected results:
no OOME, possibly close the connection straight away or set a limit so that if a message greater than a certain size is seen and an invalid type exception occurs the connection is closed

Additional info:
See support case 01648485
Comment 18 Yong Hao Gao 2017-03-21 09:38:33 UTC 
Hi Tyronne,

Yes we should handle "poisoned" messages. Right now what I'm not sure about is how the poisoned messages are look like in the customer's application. Once we know the details we can figure out a way to handle it. The best way is to have a reproducer.

Howard
Comment 21 Peter Mackay 2017-05-04 11:40:50 UTC 
Verified with EAP 6.4.15.CP.CR3
Comment 22 Petr Penicka 2017-05-19 08:04:11 UTC 
Released on May 18 as part of EAP 6.4.15.