[
https://issues.apache.org/jira/browse/ARTEMIS-4309?focusedWorklogId=865201&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-865201
]
ASF GitHub Bot logged work on ARTEMIS-4309:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Jun/23 12:17
Start Date: 13/Jun/23 12:17
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4489:
URL:
https://github.com/apache/activemq-artemis/pull/4489#issuecomment-1589189166
@prb17 I'm just confused.. I'm not discussing your changes here.. just
trying to understand when the large message was kicked in.. what's setting it
on.
you added a text files which is about TEXT * 5 times. I can't find the
minLargeMessageSize set anywhere in that test.
I will merge this fix BTW. I'm just trying to understand what set this off
on that test. Because I thought it was not supposed to use a large message with
the little text is using.
Issue Time Tracking
-------------------
Worklog Id: (was: 865201)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
