HornetQ Exception, HQ119032: Invalid type: -84. What does it mean ?

Solution Unverified - Updated

Environment

Red Hat JBoss Enterprise Application Platform 6.4.6

Issue

What problem/issue/behavior are you having trouble with? What do you expect to see?

We have a HorentQ client running in an EAP instance. Sometimes it throws OOM exception when hornetq sever restarts.

The logs show

2016-06-02 16:20:10,304 ERROR [org.hornetq.core.client] (Old I/O client worker ([id: 0x24ff517f, /11.22.33.44:42153 => /55.66.77.88:5445]), runningThread=Thread-35
(HornetQ-client-global-threads-1955853658)) HQ214013: Failed to decode packet: java.lang.IllegalArgumentException: HQ119032: Invalid type: -84

Can you explain the cause of Invalid type: -84 ?

Resolution

Identify the cause of the corruption.

Root Cause

You get HQ214013: Failed to decode packet: java.lang.IllegalArgumentException: HQ119032: Invalid type:

When using the HornetQ protocol and the packet cannot be deciphered. For some reason it appears PacketDecoder is receiving -84 and that is not defined within the HornetQ protocol so is reported as invalid. Some corruption has taken place.

If this occurs in JBoss EAP 6.4.0_CP17 and above the connection will be closed.

Diagnostic Steps

If this is a repeatable scenario then you may be able to trace by getting a tcpdump but that may only show the packet of type -84 being received.
With the aim of finding where the corruption is taking place.

SBR
Product(s)
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.