Friday, 24 March 2017

Solving coherence error in Jdeveloper application runtime

ERROR :
 We are getting this error while trying to run an adf application in Jdeveloper 12c -

<Mar 23, 2017 2:49:16 AM EDT> <Error> <com.oracle.coherence> <BEA-000000> <2017-03-23 02:49:16.210/99.494 Oracle Coherence GE 12.2.1.0.0 <Error> (thread=Cluster, member=n/a): This member could not join the cluster because of a mismatch between Coherence license types. This member was attempting to run in dev mode. Rejected by Member(Id=1, Timestamp=2017-03-21 11:54:35.609, Address=10.45.232.75:62988, MachineId=18209, Location=site:dev.prod.wudip.com,machine:WUWVC0WSAPS03,process:5468,member:IBR_server1, Role=WeblogicServer).> 

<Mar 23, 2017 2:49:16 AM EDT> <Error> <CoherenceIntegration> <BEA-2194507> <The Coherence cluster service failed to start or failed to join cluster due to java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING) using <cluster-config>

SOLUTION :


This error is due to coherence and is resolved by verifying the coherence related configuration in config.xml file of the particular user .
E:\Users\3******9\AppData\Roaming\JDeveloper\system12.2.1.0.42.151011.0031\DefaultDomain\config\config.xml

This is the content of config.xml file : 

<listen-address></listen-address>
    <tunneling-enabled>true</tunneling-enabled>
    <server-diagnostic-config>
      <name>DefaultServer</name>
    </server-diagnostic-config>
    <coherence-cluster-system-resource>defaultCoherenceCluster</coherence-cluster-system-resource>

Make the changes in the 2 fields shown below :

<listen-address>localhost</listen-address>
    <tunneling-enabled>true</tunneling-enabled>
    <server-diagnostic-config>
      <name>DefaultServer</name>
    </server-diagnostic-config>
    <coherence-cluster-system-resource xsi:nil="true"></coherence-cluster-system-resource>
  </server>

6 comments:

  1. Thanks a ton!!!
    After using this solution finally I was able to get the weblogic up

    ReplyDelete
  2. This solved my problem. Appreciate this.

    ReplyDelete
  3. It's 2020 and this still worked! Thank you thank you!

    ReplyDelete
  4. This comment has been removed by the author.

    ReplyDelete
  5. This comment has been removed by the author.

    ReplyDelete
  6. I am facing similar issue when I try to start veridata Server in DEV mode.
    You Solution is working for Veridata configuration. Thank you

    ReplyDelete