Monday 19 February 2018

java.lang.Exception:at org.jgroups.protocols.UDP._send(UDP.java:212) Error in OIM and SOA server logs

java.lang.Exception:at org.jgroups.protocols.UDP._send(UDP.java:212)
Error in OIM and SOA server logs

OIM Version:-11.1.2.3.0

Error:-

<Feb 19, 2018 3:04:10 PM IST> <Error> <org.jgroups.protocols.UDP> <BEA-000000> <failed sending message to null (58 bytes)
java.lang.Exception: dest=/224.255.1.75:45566 (61 bytes)
        at org.jgroups.protocols.UDP._send(UDP.java:212)
        at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:167)
        at org.jgroups.protocols.TP.doSend(TP.java:1102)
        at org.jgroups.protocols.TP.send(TP.java:1088)
        at org.jgroups.protocols.TP.down(TP.java:907)
        at org.jgroups.protocols.PING.sendMcastDiscoveryRequest(PING.java:276)
        at org.jgroups.protocols.PING.sendGetMembersRequest(PING.java:256)
        at org.jgroups.protocols.Discovery$PingSenderTask$1.run(Discovery.java:396)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused By: java.io.IOException: Invalid argument
        at java.net.PlainDatagramSocketImpl.send(Native Method)
        at java.net.DatagramSocket.send(DatagramSocket.java:698)
        at org.jgroups.protocols.UDP._send(UDP.java:204)
        at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:167)
        at org.jgroups.protocols.TP.doSend(TP.java:1102)
        at org.jgroups.protocols.TP.send(TP.java:1088)
        at org.jgroups.protocols.TP.down(TP.java:907)
        at org.jgroups.protocols.PING.sendMcastDiscoveryRequest(PING.java:276)
        at org.jgroups.protocols.PING.sendGetMembersRequest(PING.java:256)
        at org.jgroups.protocols.Discovery$PingSenderTask$1.run(Discovery.java:396)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

>

To Resolve above Error:-


Add this property to the startup tab of the server in weblogic console if you have setup the oim server and soa server to start using the weblogic console:

1. Log in to the WebLogic Console.
2. Navigate to Environment -> Servers.
3. Click Lock and Edit.
4. Click on the OIM or SOA Managed server.
5. Click on the Server Start subtab
6. Add the following to the Arguments field:
  -Djava.net.preferIPv4Stack=true
  Note:-Add following argument field in all managed servers if it is cluster
7. Click Save.
8. Click Activate Changes.
9. Restart the managed WebLogic server

or

If you trying to start Managed servers using script or from back-end location
add following argument :-Djava.net.preferIPv4Stack=true in setDomainEnv.sh file

Note: Take backup of tmp, cache and data folders present 
           servers location of all managed  servers and restart servers.

If you’re having Managed servers in cluster nodes add following
 Argument: - -Djava.net.preferIPv4Stack=true in setDomainEnv.sh file
Present in all cluster nodes.

Take backup of tmp, cache and data folders present servers’ location of
Managed server and restart servers

No comments:

Post a Comment