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

ASF GitHub Bot logged work on ARTEMIS-4309:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Jun/23 20:49
            Start Date: 10/Jun/23 20:49
    Worklog Time Spent: 10m 
      Work Description: prb17 commented on PR #4489:
URL: 
https://github.com/apache/activemq-artemis/pull/4489#issuecomment-1585813365

   @jbertram I believe I satisfied the requirements for having an associated 
Jira, squashed the commits, and followed the Artemis commit message style.
   
   I recognized by pushing first and having to squash later I got myself into a 
weird state. Just let me know if something else needs to be addressed.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 864831)
    Time Spent: 20m  (was: 10m)

> 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: 20m
>  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)

Reply via email to