Am Freitag, dem 14.10.2022 um 09:22 +0100 schrieb Robbie Gemmell:
> A very similar report came in a couple months ago, and the reason was
> that the session (/children) was incorrectly being used from multiple
> threads, causing responses operations to 'overlap' and leading to a
> ClassCastExceptio
A very similar report came in a couple months ago, and the reason was
that the session (/children) was incorrectly being used from multiple
threads, causing responses operations to 'overlap' and leading to a
ClassCastException when the mismatching responses for a different
operation arrived.
On Th
If you are able to reproduce with 2.26.0 please follow up with a Jira [1],
and attach the test you're using to reproduce it (or some other equivalent
way to reproduce the CCE). Thanks!
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS
On Thu, Oct 13, 2022 at 2:31 PM Thorsten Meinl
wrote
Am Donnerstag, dem 13.10.2022 um 11:38 -0500 schrieb Justin Bertram:
> It looks like perhaps the responses are being read by the client out
> of order or something like that. Are you using both the core JMS
> client and broker from 2.24.0?
Yes, both client and broker are 2.24.0.
> How often do you
It looks like perhaps the responses are being read by the client out of
order or something like that. Are you using both the core JMS client and
broker from 2.24.0? How often do you see this? Have you tried reproducing
with the latest release (i.e. 2.26.0)?
Justin
On Thu, Oct 13, 2022 at 9:51 AM
Hi all,
Very occasionally we get the following exception when creating a new
topic in Artemis (2.24.0):
Caused by: java.lang.ClassCastException: class
org.apache.activemq.artemis.core.protocol.core.impl.wireformat.NullResp
onseMessage_V2 cannot be cast to class
org.apache.activemq.artemis.core.pr
