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
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
Verified with EAP 6.4.15.CP.CR3
Released on May 18 as part of EAP 6.4.15.