Re: Wildfly 32.0.1 issues with ActiveMQ Messaging

34 views
Skip to first unread message

Emmanuel Hugonnet

unread,
Jul 1, 2024, 7:17:43 AM (6 days ago) Jul 1
to wil...@googlegroups.com
I think it is due to https://issues.apache.org/jira/browse/ARTEMIS-4652 which is fixed in Apache Artemis 2.34.0 which will be (2.35.0 in
fact) in WildFly 33.

Emmanuel

Le 27/06/2024 à 07:14, Goren Zicwar a écrit :
> Hi,
> We are upgrading to Wildfly 32 from an older version. After successful deployment of our webapp ear when we try to fetch some data from h2
> db we are getting following errors:
>
> WARN  [org.apache.activemq.artemis.core.client] (default task-1) AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]
>
> ERROR [stderr] (default task-1) org.hibernate.exception.SQLGrammarException: could not prepare statement [Syntax error in SQL statement
> "select pr1_0.jobId,pr1_0.transactionId,pr1_0.[*]user from H2DB pr1_0 where pr1_0.started between ? and ? order by pr1_0.jobId desc";
> expected "identifier"; SQL statement:
>
>
> We enabled activemq artemis logger in standalone.xml to get more info:
> <logger category="org.apache.activemq.artemis">
> <level name="DEBUG"/>
> </logger>
>
> And received following logs:
>
> DEBUG [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] (Thread-21
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@6391dc0)) PostOffice::simpleRoute null as bindings
>
> DEBUG [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] (Thread-21
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@6391dc0)) Couldn't find any bindings for
> address=activemq.notifications on message=CoreMessage[messageID=311385129571, durable=true, userID=null, priority=0, timestamp=Wed Jun 26
> 07:42:24 CEST 2024, expiration=0, durable=true, address=activemq.notifications, size=735,
> properties=TypedProperties[_AMQ_User=8593081b-ddcf-49c4-9f88-825dd3b6ffed, _AMQ_Distance=0,
> _AMQ_SessionName=dd21f242-337e-11ef-a266-005056822590, _AMQ_Protocol_Name=CORE, _AMQ_Address=activemq.notifications,
> _AMQ_NotifType=SESSION_CLOSED, _AMQ_Client_ID=NULL-value, _AMQ_NotifTimestamp=1719380544094,
> _AMQ_ConnectionName=dd20b9bf-337e-11ef-a266-005056822590]]@437383639
>
> [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] (Thread-21
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@6391dc0)) Message CoreMessage[messageID=311385129571,
> durable=true, userID=null, priority=0, timestamp=Wed Jun 26 07:42:24 CEST 2024, expiration=0, durable=true,
> address=activemq.notifications, size=735, properties=TypedProperties[_AMQ_User=8593081b-ddcf-49c4-9f88-825dd3b6ffed, _AMQ_Distance=0,
> _AMQ_SessionName=dd21f242-337e-11ef-a266-005056822590, _AMQ_Protocol_Name=CORE, _AMQ_Address=activemq.notifications,
> _AMQ_NotifType=SESSION_CLOSED, _AMQ_Client_ID=NULL-value, _AMQ_NotifTimestamp=1719380544094,
> _AMQ_ConnectionName=dd20b9bf-337e-11ef-a266-005056822590]]@437383639 is not going anywhere as it didn't have a binding on
> address:activemq.notifications
>
> DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionImpl] (default task-1) calling cleanup on ClientSessionImpl
> [name=dd21f242-337e-11ef-a266-005056822590, username=null, closed=false, factory =
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl@5caaeaf7, metaData=(jms-session=,)]@59cc2d71
>
> DEBUG [org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl] (default task-1) RemotingServiceImpl::removing succeeded
> connection ID dd20b9bf-337e-11ef-a266-005056822590, we now have 32 connections
>
> WARN  [org.apache.activemq.artemis.core.client] (default task-1) AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]
>
> DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionImpl] (default task-1) Session was already closed, giving up now,
> this=ClientSessionImpl [name=dd21f242-337e-11ef-a266-005056822590, username=null, closed=true, factory =
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl@5caaeaf7, metaData=(jms-session=,)]@59cc2d71
>
> DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl] (Thread-2 (ActiveMQ-client-global-threads)) Failure captured
> on connectionID=dd20b9bf-337e-11ef-a266-005056822590, performing failover or reconnection now:
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219006: Channel disconnected]
> at
> org.apache.active...@2.32.0//org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:418)
> at
> org.apache.ac...@2.32.0//org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:280)
> at org.apache.active...@2.32.0//org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:57)
> at org.apache.active...@2.32.0//org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:32)
> at
> org.apache.active...@2.32.0//org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:68)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at org.apache.active...@2.32.0//org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
>
>
> The functionality was working correctly in previous Wildfly version 18.0.1. Any idea what could be the cause? Thanks in advance.
> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/ca843b3a-417d-4cf1-82a6-56bbb3bfc905n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/ca843b3a-417d-4cf1-82a6-56bbb3bfc905n%40googlegroups.com?utm_medium=email&utm_source=footer>.

Reply all
Reply to author
Forward
0 new messages