Bug 1428338 - [GSS](6.4.z) HornetQ Invalid Type exception handling improvements
Summary: [GSS](6.4.z) HornetQ Invalid Type exception handling improvements
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.11
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: CR1
: EAP 6.4.15
Assignee: Yong Hao Gao
QA Contact: Peter Mackay
URL: https://github.com/hornetq/hornetq/co...
Whiteboard:
Depends On:
Blocks: 1435595 eap6415-payload 1435783
TreeView+ depends on / blocked
 
Reported: 2017-03-02 10:58 UTC by Shaun Appleton
Modified: 2020-06-11 13:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1435595 (view as bug list)
Environment:
Last Closed: 2017-05-19 08:04:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2371801 0 None None None 2017-03-24 18:13:11 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.