Justin,
When reproducing, are you after version 2.39 of the client, broker, or both?
john

-----Original Message-----
From: Justin Bertram <jbert...@apache.org> 
Sent: Monday, January 13, 2025 10:20 AM
To: users@activemq.apache.org
Subject: Re: Error reading large message from topic, have workaround

*** [Caution] This email is from an external source. Please use caution 
responding, opening attachments or clicking embedded links. ***


Do you have a way to reproduce this? If so, are you able to reproduce it on the 
latest release (i.e. 2.39.0)? If so, could you open a Jira and attach the 
reproducer to it?


Justin

On Sun, Jan 12, 2025 at 7:14 PM John Lilley 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__john.lilley-40redpointglobal.com&d=DwIFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=VpU5fPwEQ8wKbKY5SBkV1DYypS_WKWolD9Eue6u6sYo&m=mOhvtpj1bPmQq3FvZwt3JbkJC5HsYlYZ1co5eU_FKkmh3Lh3XCJJ-PqwCpFZxjGB&s=u36WldRAfPHsavyk1-v5qPpvrzqDmaoQ-MRkB4PMN7k&e=>
wrote:

> I'm getting this error reading (presumably) a large topic message.
> Running on Windows 11.
> Broker version Artemis 2.30.
> JMS client dependency:
> <dependency>
>     <groupId>org.apache.activemq</groupId>
>     <artifactId>artemis-jakarta-client</artifactId>
>     <version>2.32.0</version>
> </dependency>
>
> This seems to happen only for "large" packets, observed with packets 
> around 100KB and larger.  I read that the default threshold for large 
> messages is 100KB, so this kind of makes sense.
>
> I have a workaround, which is using streams for large messages as 
> described here:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__activemq.apache.o
> rg_components_artemis_documentation_2.5.0_large-2Dmessages.html&d=DwIF
> aQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=VpU5fPwEQ8wKbKY5SBk
> V1DYypS_WKWolD9Eue6u6sYo&m=mOhvtpj1bPmQq3FvZwt3JbkJC5HsYlYZ1co5eU_FKkm
> h3Lh3XCJJ-PqwCpFZxjGB&s=fAVOJMbPdD5rKTiLoVacSeUdnEocUwJcPyXgYMEdF7M&e=
>
> Back on 27 July 2023, I posted a similar issue to the group but it was 
> for large messages posted to queues, and it had just been fixed in a 
> recent update, so that's working fine now.  This is perhaps a similar 
> issue with topic publication?
>
> Let me know if I should post a bug report for this.
>
> Thanks
> john
>
>
> 2025-01-12T17:05:18.439 [Thread-1] .JmsTopicServer.run:126 [] ERROR -
> Subscriber: Error processing message java.lang.RuntimeException: AMQ219028:
> Timeout waiting for LargeMessage Body
>                 at
> org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:91)
>                 at
> org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.readBytes(ActiveMQBytesMessage.java:217)
>                 at
> net.redpoint.rpdm.ipc.jms.JmsTopicServer$TopicReceiver.run(JmsTopicServer.java:111)
>                 at java.base/java.lang.Thread.run(Thread.java:840)
> Caused by:
> ActiveMQLargeMessageException[errorType=LARGE_MESSAGE_ERROR_BODY
> message=AMQ219028: Timeout waiting for LargeMessage Body]
>                 at
> org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.waitCompletion(LargeMessageControllerImpl.java:303)
>                 at
> org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.saveBuffer(LargeMessageControllerImpl.java:268)
>                 at
> org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.checkBuffer(ClientLargeMessageImpl.java:157)
>                 at
> org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:89)
>                 ... 3 more
> PLEASE NOTE: This e-mail from Redpoint Global Inc. ("Redpoint") is 
> confidential and is intended solely for the use of the individual(s) 
> to whom it is addressed. If you believe you received this e-mail in 
> error, please notify the sender immediately, delete the e-mail from 
> your computer and do not copy, print or disclose it to anyone else. If 
> you properly received this e-mail as a customer, partner or vendor of 
> Redpoint, you should maintain its contents in confidence subject to 
> the terms and conditions of your agreement(s) with Redpoint.
>

Reply via email to