-
Bug
-
Resolution: Done
-
Minor
-
32.0.0.Final, 32.0.1.Final
-
None
-
---
-
---
After upgrading to Wildfly 32 (from 31) we are seeing the following repeating error in the server log
0:41:18,391 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
10:42:07,657 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
10:43:07,655 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
10:44:07,661 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
10:45:07,662 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
10:46:07,661 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
10:47:07,664 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
10:48:07,660 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
10:49:07,655 WARN [org.apache.activemq.artemis.core.client] (EJB default - 2) AMQ212037: Connection failure to invm:0 has been detected: null [code=GENERIC_EXCEPTION]
This looks to be caused by [ARTEMIS-4691] AMQ212037 warning when closing any in-vm connection - ASF JIRA (apache.org)
So I guess a component upgrade to 2.33.0 would probably resolve it.
- is duplicated by
-
WFLY-19394 ActiveMQ Artemis 2.32 to 2.33
-
- Resolved
-
- relates to
-
WFLY-19166 Upgrade Apache Artemis to 2.34.0
-
- Closed
-