Sunday, October 13, 2013

SOA Cluster Coherence Error: Detected another cluster senior, running on an incompatible protocol

Issue:

Platform: OEL 5
SOA Version: 11.1.1.5.0 for AIA

Had set up SOA cluster with two managed servers running on same server and managed as part of a cluster.

On starting up the second managed server, it always fail throwing following error stack.


<Oct 10, 2013 7:54:48 PM GMT> <Error> <Coherence> <BEA-000000> <2013-10-10 19:54:48.830/1032.427 Oracle Coherence GE 3.7.1.1 <Error> (thread=Cluster, member=2): Detected another cluster senior, running on an incompatible protocol at null manual intervention may be required>

Reason:

By default the coherence.clusterport is set to 9778 and it seems to have an issue with this version. Change it to any other valid/available port number and restart the service.

Solution:

Move to $DOMAIN_HOME/bin directory

Take a backup of setDomainEnv.sh file.

Open setDomainEnv.sh and search for clusterport and come to the following line

EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Dsoa.archives.dir=${SOA_ORACLE_HOME}/soa -Dsoa.oracle.home=${SOA_ORACLE_HOME} -Dsoa.instance.home=${DOMAIN_HOME} -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9777 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=${WL_HOME}/server/lib/DemoTrust.jks"

Change the port number as shown above. By default it would be 9778. Change it to any other valid port number. In above example I changed it to 9777.

Restart the SOA services.

No comments:

Post a Comment