asap$ENV_ID.ear File is Showing Prepared State in Weblogic Console (Summary of Deployments) And Unable to Redeploy Due to Missing Users / Groups (Doc ID 1933303.1)

Last updated on MARCH 24, 2016

Applies to:

Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.

Symptoms

Because of abnormal shutdown due to the result of a disk issue,  the asap$ENV_ID.ear file showing in 'Prepared' state in the Weblogic console (Under Summary of Deployments)  after restarting weblogic. We tried to redeploy the asap$ENV_ID.ear file but it failed and the following error messages appeared in the weblogic admin server log file:


AdminServer.log:
<Sep 23, 2014 2:24:07 PM MMT> <Warning> <EJB> <BEA-010212> <The EJB 'AsapUtilRng(Application: asapAUC0, EJBComponent: cdws-adapter-rng-ejb.jar)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: local[recycleSecureID(java.lang.String), generateSecureID()]  >
<Sep 23, 2014 2:24:07 PM MMT> <Warning> <EJB> <BEA-010212> <The EJB 'CartridgeManagementCache(Application: asapAUC0, EJBComponent: cdws-adapter-cache-ejb.jar)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: local[updateUnit(java.lang.String,com.oracle.cgbu.asap.cm.common.CartridgeManagementCacheUnit), removeUnit(java.lang.String), addUnit(java.lang.String,com.oracle.cgbu.asap.cm.common.CartridgeManagementCacheUnit), getUnit(java.lang.String), findUnitByTemplate(com.oracle.cgbu.asap.cm.common.CartridgeManagementCacheUnit)]  >
<Sep 23, 2014 2:24:07 PM MMT> <Warning> <EJB> <BEA-010199> <EJB AdapterMDB with run as role CARTRIDGE_MANAGEMENT_WEBSERVICE has no run-as-principal-name specified in its deployment descriptor or annotation. The EJB container has chosen principal-name cmws_studio from the security-role-assignment list for role CARTRIDGE_MANAGEMENT_WEBSERVICE to be the run as principal name.>
<Sep 23, 2014 2:24:07 PM MMT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "AUC0.RPCDataSource": JZ006: Caught IOException: java.net.ConnectException: Connection refused.>
<Sep 23, 2014 2:24:07 PM MMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1411458845044' for task '2'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(cdws-adapter-cache-mdb.jar)
Unable to deploy EJB: AdapterMDB from cdws-adapter-cache-mdb.jar:
The run-as security principal, 'cmws_studio', chosen for the EJB 'AdapterMDB(Application: asapAUC0, EJBComponent: cdws-adapter-cache-mdb.jar)' is not a valid user principal in the current security realm. Please specify a valid user principal for the EJB to use.
weblogic.application.ModuleException: Exception preparing module: EJBModule(cdws-adapter-cache-mdb.jar)
Unable to deploy EJB: AdapterMDB from cdws-adapter-cache-mdb.jar:
The run-as security principal, 'cmws_studio', chosen for the EJB 'AdapterMDB(Application: asapAUC0, EJBComponent: cdws-adapter-cache-mdb.jar)' is not a valid user principal in the current security realm. Please specify a valid user principal for the EJB to use.
       at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
       at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
       at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
       at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
       at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
       Truncated. see log file for complete stacktrace
Caused By: The run-as security principal, 'cmws_studio', chosen for the EJB 'AdapterMDB(Application: asapAUC0, EJBComponent: cdws-adapter-cache-mdb.jar)' is not a valid user principal in the current security realm. Please specify a valid user principal for the EJB to use.
       at weblogic.ejb.container.deployer.BeanInfoImpl.calculateRunAsPrincipal(BeanInfoImpl.java:1025)
       at weblogic.ejb.container.deployer.BeanInfoImpl.prepare(BeanInfoImpl.java:971)
       at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1281)
       at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:1031)
       at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1288)
       Truncated. see log file for complete stacktrace
>
<Sep 23, 2014 2:24:07 PM MMT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'asapAUC0'.>
<Sep 23, 2014 2:24:07 PM MMT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(cdws-adapter-cache-mdb.jar)
Unable to deploy EJB: AdapterMDB from cdws-adapter-cache-mdb.jar:
The run-as security principal, 'cmws_studio', chosen for the EJB 'AdapterMDB(Application: asapAUC0, EJBComponent: cdws-adapter-cache-mdb.jar)' is not a valid user principal in the current security realm. Please specify a valid user principal for the EJB to use.
       at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
       at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
       at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
       at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
       at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
       Truncated. see log file for complete stacktrace
Caused By: The run-as security principal, 'cmws_studio', chosen for the EJB 'AdapterMDB(Application: asapAUC0, EJBComponent: cdws-adapter-cache-mdb.jar)' is not a valid user principal in the current security realm. Please specify a valid user principal for the EJB to use.
-------------------------------------

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