Topic
  • 3 replies
  • Latest Post - ‏2014-07-30T13:30:56Z by jtonline
Barnali9985
Barnali9985
17 Posts

Pinned topic MDM11 Business Level application deplyment

‏2014-05-18T16:24:49Z |
In WAS console i could see that MDM-operational-server-EBA-E001 is partially started. I tried to stop start the application and have got the following message:

"ErrorMDM-operational-server-EBA-E001 failed to start."

The ffdc log is as follows:

[5/18/14 11:23:46:648 EDT]     FFDC Exception:com.ibm.ws.exception.RedundantStateChangeException SourceId:com.ibm.ws.runtime.component.CompositionUnitMgrImpl ProbeId:842 Reporter:com.ibm.ws.runtime.component.CompositionUnitMgrImpl@55b0c1e4

com.ibm.ws.exception.RedundantStateChangeException: Composition Unit WebSphere:cuname=com.ibm.mdm.hub.server.app-E001_0001.eba,cuedition=BASE not started
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$2.run(CompositionUnitMgrImpl.java:794)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5459)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5585)
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.stopCompositionUnit(CompositionUnitMgrImpl.java:840)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.stopCompositionUnit(CompositionUnitMgrImpl.java:746)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:272)
at javax.management.modelmbean.RequiredModelMBean$4.run(RequiredModelMBean.java:1152)
at java.security.AccessController.doPrivileged(AccessController.java:298)
at com.ibm.oti.security.CheckedAccessControlContext.securityCheck(CheckedAccessControlContext.java:30)
at sun.misc.JavaSecurityAccessWrapper.doIntersectionPrivilege(JavaSecurityAccessWrapper.java:41)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1146)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:999)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:847)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:783)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1335)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1228)
at com.ibm.ws.management.bla.runtime.ControlOperationHelper.execControlOpViaRuntimeMBean(ControlOperationHelper.java:1084)
at com.ibm.ws.management.bla.runtime.ControlOperationHelper.execControlOpOnLocalServer(ControlOperationHelper.java:538)
at com.ibm.wsspi.management.bla.runtime.CompUnitControlOpDispatcher.dispatchCompUnitControlOpToTarget(CompUnitControlOpDispatcher.java:285)
at com.ibm.wsspi.management.bla.runtime.CompUnitControlOpDispatcher.dispatch(CompUnitControlOpDispatcher.java:210)
at com.ibm.ws.management.bla.steps.StepStopBLA.execute(StepStopBLA.java:156)
at com.ibm.wsspi.management.bla.op.compound.Phase.execute(Phase.java:166)
at com.ibm.wsspi.management.bla.op.compound.CompoundOperation._doPhaseExecute(CompoundOperation.java:123)
at com.ibm.wsspi.management.bla.op.compound.CompoundOperation.doExecute(CompoundOperation.java:103)
at com.ibm.wsspi.management.bla.op.Operation.execute(Operation.java:235)
at com.ibm.wsspi.management.bla.op.compound.CompoundOperation.execute(CompoundOperation.java:83)
at com.ibm.ws.management.bla.commands.ADTCommand$OperationScheduler.run(ADTCommand.java:672)
at java.lang.Thread.run(Thread.java:796)
 

 

I am trying to deploy a .cba for one custom project but I could see the asset is stopped:

com.ibm.mdm.hub.server.app-E001_0001.eba

 

and there is no option to start the asset in the following page:

Business-level applications > MDM-operational-server-EBA-E001

Please help. 

 

Updated on 2014-05-18T16:25:36Z at 2014-05-18T16:25:36Z by Barnali9985
  • kumarchandan
    kumarchandan
    2 Posts

    Re: MDM11 Business Level application deplyment

    ‏2014-06-23T06:43:33Z  

    Hi,

    I am also getting the same error.Please let me know if you have any fix/suggestion for this.

  • joechen@us.ibm.com
    6 Posts

    Re: MDM11 Business Level application deplyment

    ‏2014-07-28T22:11:37Z  

    Hi,

    I am also getting the same error.Please let me know if you have any fix/suggestion for this.

    One likely cause is that your MDM-operational-server-EBA-E001 extends from an external cba deployed from an MDM v11 workspace which that has renamed or deleted.  One way to confrim if that is the case is to check if a status is in red in WAS admin console Applications/Business-level applications/MDM-operational-server-EBA-E001.

    To resolve this issue:

    1) If you just renamed the workspace, you may restore the workspace, bounce MDM, then retest

    2) If the workspace is gone, then you can at least get your OOTB MDM to work by removing the cba extention in WAS admin console, Applications/Business-level applications/MDM-operational-server-EBA-E001. Note, you may need to rollback your MDM DB if necessary.

    Regards,

    JC

     

  • jtonline
    jtonline
    24 Posts

    Re: MDM11 Business Level application deplyment

    ‏2014-07-30T13:30:56Z  

    One likely cause is that your MDM-operational-server-EBA-E001 extends from an external cba deployed from an MDM v11 workspace which that has renamed or deleted.  One way to confrim if that is the case is to check if a status is in red in WAS admin console Applications/Business-level applications/MDM-operational-server-EBA-E001.

    To resolve this issue:

    1) If you just renamed the workspace, you may restore the workspace, bounce MDM, then retest

    2) If the workspace is gone, then you can at least get your OOTB MDM to work by removing the cba extention in WAS admin console, Applications/Business-level applications/MDM-operational-server-EBA-E001. Note, you may need to rollback your MDM DB if necessary.

    Regards,

    JC

     

    It's best to avoid deploying with resources in the workspace. To configure your workspace to deploy resources to the server, and other essential tips for working with OSGi, have a look at the OSGi best practices and troubleshooting guide.

    Regards, James