[ARTEMIS-4309] Large JMS ObjectMessage types result in UTFDataFormatException when deserialized on client side

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.29.0
• Assignee: Unassigned
• Reporter: peter brady
• Created: 10/Jun/23 17:03
• Updated: 21/Jun/23 13:58
• Resolved: 21/Jun/23 13:58

Description

When an activemq classic client uses the compression option to create a connection with the Artemis broker, ObjectMessage types greater than 1024 bytes have a problem being deserialized on the consumer side. The process consuming the message attempts to reconstruct the Java object from the data contained in the received ObjectMessage, but then throws a UTFDataFormatException.

Issue Links

• links to: GitHub Pull Request #4489