Error:
====
<Sep 24, 2014 10:48:26 PM CDT> <Error> <Cluster> <BEA-000109> <An error occurred while sending multicast message: java.io.IOException: Invalid argument
java.io.IOException: Invalid argument
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:676)
at weblogic.cluster.MulticastFragmentSocket.sendThrottled(MulticastFragmentSocket.java:206)
at weblogic.cluster.MulticastFragmentSocket.send(MulticastFragmentSocket.java:158)
at weblogic.cluster.FragmentSocketWrapper.send(FragmentSocketWrapper.java:91)
Truncated. see log file for complete stacktrace
We faced this issue on a customer with a cluster and using multicast for some reason.When we tried starting managed server we got this error.
Fix:
Refer:Doc ID 1360498.1
====
<Sep 24, 2014 10:48:26 PM CDT> <Error> <Cluster> <BEA-000109> <An error occurred while sending multicast message: java.io.IOException: Invalid argument
java.io.IOException: Invalid argument
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:676)
at weblogic.cluster.MulticastFragmentSocket.sendThrottled(MulticastFragmentSocket.java:206)
at weblogic.cluster.MulticastFragmentSocket.send(MulticastFragmentSocket.java:158)
at weblogic.cluster.FragmentSocketWrapper.send(FragmentSocketWrapper.java:91)
Truncated. see log file for complete stacktrace
We faced this issue on a customer with a cluster and using multicast for some reason.When we tried starting managed server we got this error.
Fix:
Refer:Doc ID 1360498.1
Even if both protocols are enabled, it is possible to force a specific protocol for multicast using the property java.net.preferIPv4Stack. Adding this property to JAVA_OPTIONS in the startup script, like setDominEnv.sh, resolves the issue:
export JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.net.preferIPv4Stack=true"
This fixed the issue.
|
No comments:
Post a Comment