My Oracle Support Banner

Unable To Start Up The OMS Application After Adding Coherence Configuration (Doc ID 2038761.1)

Last updated on JULY 21, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.

Symptoms

Unable to start up the OMS application after adding coherence configuration. Customer started the managed servers and the "oms" application is not coming up now. The error is as below.


ERROR
-----------------------

com.tangosol.dev.compiler.CompilerException
  at com.tangosol.run.xml.XmlTokenizer.eatName(XmlTokenizer.java:785)
  at com.tangosol.run.xml.XmlTokenizer.eatElement(XmlTokenizer.java:742)
  at com.tangosol.run.xml.XmlTokenizer.eatToken(XmlTokenizer.java:280)
  at com.tangosol.run.xml.XmlTokenizer.nextToken(XmlTokenizer.java:136)
  at com.tangosol.run.xml.SimpleParser.next(SimpleParser.java:796)
  at com.tangosol.run.xml.SimpleParser.current(SimpleParser.java:769)
  at com.tangosol.run.xml.SimpleParser.match(SimpleParser.java:826)
  at com.tangosol.run.xml.SimpleParser.parseElement(SimpleParser.java:510)
  at com.tangosol.run.xml.SimpleParser.parseDocument(SimpleParser.java:337)
  at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:188)
  at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:93)
  at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:162)
  at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:115)
  at com.tangosol.run.xml.XmlHelper.loadXml(XmlHelper.java:118)
-----
-----
Caused By: com.tangosol.dev.compiler.CompilerException
  at com.tangosol.run.xml.XmlTokenizer.eatName(XmlTokenizer.java:785)
  at com.tangosol.run.xml.XmlTokenizer.eatElement(XmlTokenizer.java:742)
  at com.tangosol.run.xml.XmlTokenizer.eatToken(XmlTokenizer.java:280)
  at com.tangosol



osm-coherence-cluster-config.xml configured as below

<cluster-config xml-override=”override”>
<member-identity>
<cluster-name system-property="tangosol.coherence.cluster">osm_cluster</cluster-name>
</member-identity>
<unicast-listener>
<well-known-addresses>
<socket-address id="1">
<address>x.x.x.x</address>
<port>8011</port>
</socket-address>
<socket-address id="2">
<address>x.x.x.x</address>
<port>8012</port>
</socket-address>
</well-known-addresses>
<authorized-hosts>
<host-address id="1">x.x.x.x</host-address>
<host-address id="2">x.x.x.x</host-address>
</authorized-hosts>
</unicast-listener>
</cluster-config>

 

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.