AnsweredAssumed Answered

CA API Gateway - Full logs - Error exceptions org.jgroups.protocols.UDP: failed sending message to null

Question asked by SBBenitezEveris on Jul 5, 2016
Latest reply on Jul 7, 2016 by Charles_Nack

Good Morning.

 

We have a problem in our CA API Gateway 9.0 production environment (Linux).

The log CA API Gateway is completely filled with the same error log from exceptions and appears every 5 seconds and within the same second, 60 times.

The log is as follows:

 

2016-07-05T11:44:08.852+0200 SEVERE  833 org.jgroups.protocols.UDP: failed sending message to null (280 bytes)

java.lang.Exception: dest=/224.0.34.104:8777 (283 bytes)

        at org.jgroups.protocols.UDP._send(UDP.java:361)

        at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:302)

        at org.jgroups.protocols.TP.doSend(TP.java:1478)

        at org.jgroups.protocols.TP.send(TP.java:1468)

        at org.jgroups.protocols.TP.down(TP.java:1186)

        at org.jgroups.protocols.Discovery.down(Discovery.java:374)

        at org.jgroups.protocols.MERGE2.down(MERGE2.java:175)

        at org.jgroups.protocols.FD.down(FD.java:315)

        at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:95)

        at org.jgroups.protocols.pbcast.NAKACK.sendXmitRsp(NAKACK.java:1051)

        at org.jgroups.protocols.pbcast.NAKACK.handleXmitReq(NAKACK.java:983)

        at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:718)

        at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)

        at org.jgroups.protocols.FD.up(FD.java:284)

        at org.jgroups.protocols.MERGE2.up(MERGE2.java:144)

        at org.jgroups.protocols.Discovery.up(Discovery.java:264)

        at org.jgroups.protocols.PING.up(PING.java:273)

        at org.jgroups.protocols.TP.passMessageUp(TP.java:1277)

        at org.jgroups.protocols.TP.access$100(TP.java:50)

        at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1830)

        at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1809)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at java.lang.Thread.run(Thread.java:745)

Caused by: java.io.IOException: No such device

        at java.net.PlainDatagramSocketImpl.send(Native Method)

        at java.net.DatagramSocket.send(DatagramSocket.java:693)

        at org.jgroups.protocols.UDP._send(UDP.java:352)

        ... 23 more

 

We did not get to see the source of the problem.

We searched the ip (unknown to us) indicating the log, and we have located in files sql scripts implying that it is a "multicast_address". But we do not know its purpose.

 

We need to solve the problem that prevents us from seeing the log.

 

A greeting.

 

PD: We have also located another exception occurs but less frequently. This is:

2016-07-05T11:29:28.315+0200 SEVERE  104 org.jgroups.protocols.UDP: failed sending message to null (83 bytes)

java.lang.Exception: dest=/224.0.34.104:8777 (86 bytes)

        at org.jgroups.protocols.UDP._send(UDP.java:361)

        at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:302)

        at org.jgroups.protocols.TP.doSend(TP.java:1478)

        at org.jgroups.protocols.TP.send(TP.java:1468)

        at org.jgroups.protocols.TP.down(TP.java:1186)

        at org.jgroups.protocols.PING.sendMcastDiscoveryRequest(PING.java:278)

        at org.jgroups.protocols.PING.sendGetMembersRequest(PING.java:259)

        at org.jgroups.protocols.Discovery$PingSenderTask$1.run(Discovery.java:407)

        at org.jgroups.util.TimeScheduler$RobustRunnable.run(TimeScheduler.java:196)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at java.lang.Thread.run(Thread.java:745)

Caused by: java.io.IOException: No such device

        at java.net.PlainDatagramSocketImpl.send(Native Method)

        at java.net.DatagramSocket.send(DatagramSocket.java:693)

        at org.jgroups.protocols.UDP._send(UDP.java:352)

        ... 15 more

Outcomes