RE: Error reading large message from topic, have workaround

2025-01-15 Thread John Lilley
Sadly the error exists in 2.39 as well. I'll get a reproduction sample together. -Original Message- From: Justin Bertram Sent: Tuesday, January 14, 2025 8:08 AM To: users@activemq.apache.org Subject: Re: Error reading large message from topic, have workaround *** [Caution] This

Re: Error reading large message from topic, have workaround

2025-01-14 Thread Justin Bertram
ustin Bertram > 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 embe

RE: Error reading large message from topic, have workaround

2025-01-14 Thread John Lilley
Justin, When reproducing, are you after version 2.39 of the client, broker, or both? john -Original Message- From: Justin Bertram Sent: Monday, January 13, 2025 10:20 AM To: users@activemq.apache.org Subject: Re: Error reading large message from topic, have workaround *** [Caution

Re: Error reading large message from topic, have workaround

2025-01-13 Thread Justin Bertram
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 wrote: > I'm getting this error reading (presumably) a large topic mess

RE: Error reading large message from topic, have workaround

2025-01-13 Thread John Lilley
users@activemq.apache.org' Subject: RE: Error reading large message from topic, have workaround Regarding my previous email and large topic packets, I was mistaken, the streaming interface does not actually solve the issue, instead I get different errors when I compare the packet length r

RE: Error reading large message from topic, have workaround

2025-01-13 Thread John Lilley
Regarding my previous email and large topic packets, I was mistaken, the streaming interface does not actually solve the issue, instead I get different errors when I compare the packet length received to what the BytesMessage reports, for example 2025-01-13T07:46:14.090 [Thread-1] .JmsTopicServ