Hello All,
We’ve been encountering Ping Failed to server: Servername2: Port in server logs.
This only happens on our Servername2 server while our Servername1 is doing good.
The trend of this log is every hour.
May I ask for your expertise and experience on what triggered this failure?
Thanks,
Brian
Hi Brian,
please provide your wM version as well as the list of Fixes being applied.
Regards,
Holger
Hello Holger,
Thank You for your response.
IS version is 9.8.
This failure message happens before and our findings was for the Ping failed, there’s a longer time Pinging for JVM it took almost a minute.
But for it only took less than 25 seconds.
STATUS | wrapper | 2019/04/26 07:58:49 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 08:02:11 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 08:02:57 | Pinging the JVM took 4 seconds to respond.
STATUS | wrapper | 2019/04/26 08:16:33 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 08:17:55 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 08:21:02 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 08:23:23 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 08:27:23 | Pinging the JVM took 3 seconds to respond.
STATUS | wrapper | 2019/04/26 08:41:09 | Pinging the JVM took 24 seconds to respond.
STATUS | wrapper | 2019/04/26 08:41:09 | Pinging the JVM took 20 seconds to respond.
STATUS | wrapper | 2019/04/26 08:41:09 | Pinging the JVM took 16 seconds to respond.
STATUS | wrapper | 2019/04/26 08:41:09 | Pinging the JVM took 12 seconds to respond.
STATUS | wrapper | 2019/04/26 08:41:09 | Pinging the JVM took 8 seconds to respond.
STATUS | wrapper | 2019/04/26 08:41:09 | Pinging the JVM took 4 seconds to respond.
STATUS | wrapper | 2019/04/26 08:58:38 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 09:00:22 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 09:01:31 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 09:03:07 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 09:12:42 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 09:26:16 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 09:34:03 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 09:38:54 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2019/04/26 09:41:54 | Pinging the JVM took 23 seconds to respond.
STATUS | wrapper | 2019/04/26 09:41:54 | Pinging the JVM took 19 seconds to respond.
STATUS | wrapper | 2019/04/26 09:41:54 | Pinging the JVM took 14 seconds to respond.
STATUS | wrapper | 2019/04/26 09:41:54 | Pinging the JVM took 10 seconds to respond.
STATUS | wrapper | 2019/04/26 09:41:54 | Pinging the JVM took 6 seconds to respond.
STATUS | wrapper | 2019/04/26 09:41:54 | Pinging the JVM took 2 seconds to respond.
I’ve searched related topics in forum and found out that restarting will stop the pinging of the server.
Per checking on our services I cannot see any service that is tasked in to ping the server itself.
Hi Brian,
the ping is occuring between the Tanuki Wrapper and the JVM running the IS, which was spawned by the Tanuki Wrapper.
By doing so the Tanuki Wrapper checks if the IntegrationServer is still alive or not.
When the IS get under load, the response to the ping request might take longe than usual.
When the Tanuki Wrapper thinks, that IS (or its jvm) crashed by any reason, it will try to restart the IS by spawning a new JVM thread for this.
Regards,
Holger
Hello Holger,
That was very helpful thoughts from you.
For now, the auto restart don’t work for us so we need to wait for our next restart to get rid of this messages.