This content has been marked as final. Show 2 replies
We are seeing same stack trace, did you resolve this?
we had the same problem. Root cause was another WebLogic cluster on other servers within the same subnet using the same cluster multicast IP and port.
After changing port number to an unique and unused value the error was gone.