Deployment Failure Due To New Addition Of Data Element And Data Change Notification (Doc ID 1678432.1)

Last updated on NOVEMBER 17, 2015

Applies to:

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

Symptoms

We have come across the use case which is failing for Order notification change in consecutive deployment.

Use case: Modifying a data change notification node from attribute “A” to a newly added attribute “B”.

Use case steps:
1. Add a new element “B” in data dictionary
2. Add the newly added element in order template
3. Add the newly added element in required views and tasks
4. Modify the data change notification to use the newly added attribute.
5. The cartridge was deployed before the change
6. We have a deployment error in the next deployment. Below is the error:

<03-May-2014 10:31:48,834 KST AM> <INFO> <model.MetaDataManager> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <Refreshing MetaData - Completed>
<03-May-2014 10:31:48,835 KST AM> <ERROR> <cartridgemgmt.DeployCartridgeMDB> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <Cartridge deployment failed:>
com.mslv.oms.metadatahandler.handler.HandlerException: Transformation of cartridge entity [notification:SampleProjectOrder_Test2] to ObjectModel failed.
      at com.mslv.oms.metadatahandler.transformer.CartridgeEntityTransformer.toObjectModel(Unknown Source)
      at com.mslv.oms.metadatahandler.operation.ImportOperation.processEntity(Unknown Source)
      at com.mslv.oms.metadatahandler.operation.ImportOperation.doProcess(Unknown Source)
      at com.mslv.oms.metadatahandler.operation.ImportOperation.deploy(Unknown Source)
      at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.a(Unknown Source)
      at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.a(Unknown Source)
      at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.onMessage(Unknown Source)
      at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:583)
      at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:486)
      at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:388)
      at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
      at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
      at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
      at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
      at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.NullPointerException: The validated object is null
      at org.apache.commons.lang3.Validate.notNull(Validate.java:222)
      at org.apache.commons.lang3.Validate.notNull(Validate.java:203)
      at oracle.communications.ordermanagement.metadatahandler.model.notification.DataChangeNotification.addDataNode(Unknown Source)
      at com.mslv.oms.metadatahandler.transformer.NotificationTransformer.getDataChangeNotification(Unknown Source)
      at com.mslv.oms.metadatahandler.transformer.NotificationTransformer.convertToObjectModel(Unknown Source)
      ... 18 more


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms