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

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732068#comment-17732068 ] 

ASF subversion and git services commented on ARTEMIS-4309:
----------------------------------------------------------

Commit 2f5463c960f5498bb407d38b2a771a7ffdae2504 in activemq-artemis's branch refs/heads/main from Peter Brady
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=2f5463c960 ]

ARTEMIS-4309 Read all bytes of compressed objmsg

Continually read from the compressed byte[] into
the decompressed object

Add test to validate large (>1024 bytes) compressed data can be
deserialized properly


> Large JMS ObjectMessage types result in UTFDataFormatException when deserialized on client side
> -----------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4309
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4309
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: peter brady
>            Priority: Minor
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)