I have a clustered OIM environment and an AdminServer. Each WebLogic Server instance is on its own machine.
I am seeing the following error messages in the Admin and OIM logs:
####<Mar 19, 2014 4:48:57 PM EDT> <Error> <org.jgroups.protocols.UDP> <*********> <oim_server2> <Timer-1,OSCacheBus,********> <<anonymous>> <> <0000KJRZgkRFo285rjs1yY1JATpB000003> <1395262137119> <BEA-000000> <failed sending message to null (109 bytes)
java.lang.Exception: dest=/********** (112 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.Discovery.down(Discovery.java:363)
at org.jgroups.protocols.MERGE2.down(MERGE2.java:169)
at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:333)
at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:72)
at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:771)
at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:572)
at org.jgroups.protocols.UNICAST.down(UNICAST.java:468)
at org.jgroups.protocols.pbcast.STABLE$1.run(STABLE.java:649)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
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:744)
Caused By: java.io.IOException: Invalid argument
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:676)
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.Discovery.down(Discovery.java:363)
at org.jgroups.protocols.MERGE2.down(MERGE2.java:169)
at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:333)
at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:72)
at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:771)
at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:572)
at org.jgroups.protocols.UNICAST.down(UNICAST.java:468)
at org.jgroups.protocols.pbcast.STABLE$1.run(STABLE.java:649)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
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:744)
Any insights on what is causing this issue and possible fixes?