I'm getting AMQ212037 and AMQ119014 at cluster Wildfly 11

752 views
Skip to first unread message

Emerson Martinez Peppinelli

unread,
Aug 14, 2023, 5:14:21 PM8/14/23
to WildFly
Hi everybody!

I'm getting the warnings described above in server.log file. 

I'm using Wildfly 11, ActiveMQ and OpenJDK 8.

How can I stop this warnings? Any setup that I have to do? 

  
2023-08-14 18:11:09,794 WARN  [org.apache.activemq.artemis.core.client] (Thread-61 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@25a8bcf8)) AMQ212037: Connection failure has been detected: AMQ119014: Did not receive data from /192.168.56.104:35026 within the 600.000ms connection TTL. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

Emmanuel Hugonnet

unread,
Aug 16, 2023, 3:24:36 AM8/16/23
to Emerson Martinez Peppinelli, WildFly
Are your connection call timeout and ttl set to the same value (aka 600000) on your pool connection factory ?
Emmanuel
> --
> 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/15a037eb-9bcd-43bd-8bee-d99cb6f4ff2an%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/15a037eb-9bcd-43bd-8bee-d99cb6f4ff2an%40googlegroups.com?utm_medium=email&utm_source=footer>.

Emerson Martinez Peppinelli

unread,
Aug 21, 2023, 7:59:28 AM8/21/23
to WildFly

I have good news! I solved the trouble changing http undertow configuration. I had read-timeout and write-timeout with 30s configured. When I removed this parameters, the warnings disappear. Let me show how my configuration is:

Before:
<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" read-timeout="30000" write-time-out="30000" />

After:
<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" />

Reply all
Reply to author
Forward
0 new messages