BPEL Console URL Hangs on One Server when Using Active Passive Cluster with Error "java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: Not a multicast address "
(Doc ID 462992.1)
Last updated on DECEMBER 04, 2013
Applies to:Oracle(R) BPEL Process Manager - Version 10.1.3.1 and later
Information in this document applies to any platform.
In a multiple node environment, after installing BPEL on HOST-A and HOST-B, logged into the HOST-A BPEL Console with no problem. Then stopped BPEL on HOST-A and started BPEL on HOST-B. Tried to log into the HOST-B BPEL Console and after supplying the userid and password access fails.
The BPEL $ORACLE_HOME/bpel/domains/<domain name>/logs/domain.log shows the following exception:
java.lang.Exception: exception caused by UDP.start(): java.net.SocketException:
Not a multicast address
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document