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 Thorsten Meinl <thorsten.me...@knime.com> wrote: > 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.protocol.core.impl.wireformat.SessionB > indingQueryResponseMessage_V4 > (org.apache.activemq.artemis.core.protocol.core.impl.wireformat.NullRes > ponseMessage_V2 and > org.apache.activemq.artemis.core.protocol.core.impl.wireformat.SessionB > indingQueryResponseMessage_V4 are in unnamed module of loader > io.quarkus.bootstrap.classloading.QuarkusClassLoader @3bf0cb2d) > at > org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionCont > ext.addressQuery(ActiveMQSessionContext.java:413) > at > org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.addressQ > uery(ClientSessionImpl.java:794) > at > org.apache.activemq.artemis.jms.client.ActiveMQSession.lookupTopic(Acti > veMQSession.java:1325) > at > org.apache.activemq.artemis.jms.client.ActiveMQSession.internalCreateTo > pic(ActiveMQSession.java:554) > at > org.apache.activemq.artemis.jms.client.ActiveMQSession.createTopic(Acti > veMQSession.java:542) > at > org.apache.activemq.artemis.jms.client.ActiveMQJMSContext.createTopic(A > ctiveMQJMSContext.java:418) > > Any hints what could be the problem? > > Thanks, > > Thorsten > > -- > Dr.-Ing. Thorsten Meinl > KNIME AG > Talacker 50 > 8001 Zurich, Switzerland > > >
