My Oracle Support Banner

OSM Deployment Failed While Deploying Cartridge With Orchestration Condition In OrderItemSpec (Doc ID 2007165.1)

Last updated on JANUARY 27, 2021

Applies to:

Oracle Communications Order and Service Management - Version 7.2.4 to 7.2.4 [Release 7.2]
Information in this document applies to any platform.


When a condition is used in Orchestration conditions tab of Order Item Specification, the cartridge is getting built properly, but the deployment of cartridge is failing.
Error logs:

org.xml.sax.SAXParseException; lineNumber: 9; columnNumber: 59; Error attempting to parse XML file (href='model/OSM_SOM_Orchestration.xml').
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(
at com.mslv.oms.cartridgemgmt.PAR.PARFile.parseDocument(
at com.mslv.oms.cartridgemgmt.PAR.PARFile.getModelAsDocument(
at com.mslv.oms.cartridgemgmt.PAR.PARFile.getCartridgeManifest(
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.deployModel(
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.processMessage(
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.onMessage(
at weblogic.ejb.container.internal.MDListener.execute(
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(
at weblogic.ejb.container.internal.MDListener.onMessage(
at weblogic.jms.client.JMSSession.onMessage(
at weblogic.jms.client.JMSSession.execute(
at weblogic.jms.client.JMSSession.executeMessage(
at weblogic.jms.client.JMSSession.access$000(
at weblogic.jms.client.JMSSession$




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

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