Deployment Fails in Design Studio After Adding Second Automation To an Order Event
(Doc ID 1333737.1)
Last updated on MARCH 28, 2019
Applies to:Oracle Communications Order and Service Management - Version 7.0.1 and later
Information in this document applies to any platform.
OSM cartridge cannot be deployed, after adding a second automation to the same Order Event.
Deployment fails with:
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'>
com.mslv.oms.deploytool.api.DeployException: Activation of deployment object failed with this message: weblogic.application.ModuleException: Exception activating module: EJBModule(osm_CentralOrderManagement_1_2_0.jar)
Unable to deploy EJB: CentralOrderManagementOrder.order.centralordermanagement.submitOrderCompletionNotification from osm_CentralOrderManagement_1_2_0.jar:
[EJB:011008]Unable to bind EJB Home Interface to the JNDI name: /automation/plugin/internal/orderNotification/CentralOrderManagement/1.2.0/om:on-CentralOrderManagementOrder-CentralOrderManagementOrder-completion.
javax.naming.NameAlreadyBoundException: om:on-CentralOrderManagementOrder-CentralOrderManagementOrder-completion is already bound; remaining name 'automation/plugin/internal/orderNotification/CentralOrderManagement/1/2/0'
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