Saturday, 20 May 2017

Hmmm - ADMA5107E and CWWBA0008E seen whilst uninstalling a SCA module from IBM BPM Advanced 8.5.7

Hmmm, I started seeing this whilst attempting to remove an existing SCA module ( EAR file ) from a BPM Advanced 8.5.7 environment: -

[5/20/17 6:10:25:473 UTC] 0000013b UninstallSche I   ADMA5017I: Uninstallation of MQ_Test started.
[5/20/17 6:10:25:535 UTC] 0000013b DMAdapter     I com.ibm.ws.ffdc.impl.DMAdapter getAnalysisEngine FFDC1009I: Analysis Engine using data base: /opt/ibm/WebSphere/AppServer/properties/logbr/ffdc/adv/ffdcdb.xml
[5/20/17 6:10:25:616 UTC] 0000013b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/ibm/WebSphereProfiles/Dmgr01/logs/ffdc/dmgr_78f7b3ac_17.05.20_06.10.25.5262387762556679923990.txt com.ibm.ws.management.AdminServiceImpl.invoke 679
[5/20/17 6:10:25:652 UTC] 0000013b BPCAppMgmt    I   CWWBF0021I: Uninstall of process application MQ_Test completed.
[5/20/17 6:10:25:671 UTC] 0000013b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/ibm/WebSphereProfiles/Dmgr01/logs/ffdc/dmgr_78f7b3ac_17.05.20_06.10.25.669165681660585464853.txt com.ibm.ws.management.application.AppUtils.getMessage 715
[5/20/17 6:10:25:673 UTC] 0000013b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/ibm/WebSphereProfiles/Dmgr01/logs/ffdc/dmgr_78f7b3ac_17.05.20_06.10.25.6728117628847154269247.txt com.ibm.ws.management.application.task.ConfigRepoHelper.getDesiredEarFileFromBinaries 804
[5/20/17 6:10:25:675 UTC] 0000013b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/ibm/WebSphereProfiles/Dmgr01/logs/ffdc/dmgr_78f7b3ac_17.05.20_06.10.25.6741709013655431538129.txt com.ibm.ws.management.application.task.ConfigRepoHelper.getDesiredEarFileFromBinaries 814
[5/20/17 6:10:25:678 UTC] 0000013b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/ibm/WebSphereProfiles/Dmgr01/logs/ffdc/dmgr_78f7b3ac_17.05.20_06.10.25.676378039060005473378.txt com.ibm.ws.sca.internal.deployment.SCAUninstallTask 001
[5/20/17 6:10:25:699 UTC] 0000013b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/ibm/WebSphereProfiles/Dmgr01/logs/ffdc/dmgr_78f7b3ac_17.05.20_06.10.25.6783939092327342589718.txt com.ibm.ws.management.application.SchedulerImpl.run 328
[5/20/17 6:10:25:703 UTC] 0000013b UninstallSche I   ADMA5107E: The application MQ_Test cannot be uninstalled.


 /opt/ibm/WebSphereProfiles/Dmgr01/logs/ffdc/dmgr_78f7b3ac_17.05.20_06.10.25.5262387762556679923990.txt

[5/20/17 6:10:25:529 UTC]     FFDC Exception:javax.management.MBeanException SourceId:com.ibm.ws.management.AdminServiceImpl.invoke ProbeId:679 Reporter:com.ibm.ws.management.AdminServiceImpl$1@7c861ea7
javax.management.MBeanException: Exception thrown in RequiredModelMBean while trying to invoke operation getProcessTemplateState
        at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1304)
        at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1093)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:832)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:814)
        at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1350)
        at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
        at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1243)
        at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:181)
        at com.ibm.ws.management.connector.ipc.CallRouter.route(CallRouter.java:247)
        at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink.doWork(IPCConnectorInboundLink.java:360)
        at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink$IPCConnectorReadCallback.complete(IPCConnectorInboundLink.java:602)
        at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1820)
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
Caused by: com.ibm.bpe.api.ProcessTemplateNotFoundException: CWWBA0008E: Process template 'processMessage. Tue 2017-05-16 18:11:58.000' is not found.


There wasn't a corresponding Process Template showing up in the BPC Explorer: -



even whilst logged in as the Deployment Environment super-user, deAdmin.

I'd tried the obvious - stopping the entire DE - Cluster Members, Node Agent, Deployment Manager etc. - but to no avail.

I even tried removing the wstemp directory from within the DM's profile, but again no dice.

Working on the assumption that the problem was in the WAS rather than BPM world ( because BPC Explorer showed no template ), I took the nuclear option of removing the JEE application from the DM configuration: -

cd /opt/ibm/WebSphereProfiles/Dmgr01/config/cells/PSCell1/applications
rm -Rf MQ_Test.ear/

restarted the Deployment Manager, and forcibly resynced the node: -

/opt/ibm/WebSphereProfiles/Dmgr01/bin/wsadmin.sh -lang jython -user wasadmin -password passw0rd

AdminControl.invoke('WebSphere:name=repository,process=nodeagent,platform=common,node=Node1,version=5.0,type=ConfigRepository,mbeanIdentifier=repository,cell=PSCell1,spec=1.0', 'refreshRepositoryEpoch')
AdminControl.invoke('WebSphere:name=cellSync,process=dmgr,platform=common,node=Dmgr,version=8.5.5.11,type=CellSync,mbeanIdentifier=cellSync,cell=PSCell1,spec=1.0', 'syncNode', '[Node1]')

Having done the latter, the app disappeared from the All Applications view: -


and, more importantly, I was then able to install a fresh copy of the SCA module: -

AdminApp.install('/tmp/'+AppName+'.ear', '[ -nopreCompileJSPs -distributeApp -nouseMetaDataFromBinary -nodeployejb -appname '+AppName+' -createMBeansForResources -noreloadEnabled -nodeployws -validateinstall warn -processEmbeddedConfig -filepermission .*\.dll=755#.*\.so=755#.*\.a=755#.*\.sl=755 -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -asyncRequestDispatchType DISABLED -nouseAutoLink -noenableClientModule -clientMode isolated -novalidateSchema -MapResRefToEJB [[ '+AppName+'Web "" '+AppName+'Web.war,WEB-INF/web.xml sca/resource/export/readTheMessage_MQEXPORT_CF javax.jms.ConnectionFactory jms/'+conFact+' "" "" "" ] -MapModulesToServers [[ MQ_TestWeb MQ_TestWeb.war,WEB-INF/web.xml WebSphere:cell='+cellID+',cluster='+clusterName+' ]]]')
AdminConfig.save()
AdminNodeManagement.syncActiveNodes()


and start the application: -

AdminControl.invoke('WebSphere:name=ApplicationManager,process=AppClusterMember1,platform=proxy,node=Node1,version=8.5.5.11,type=ApplicationManager,mbeanIdentifier=ApplicationManager,cell=PSCell1,spec=1.0', 'startApplication', '[MQ_Test]')

which is always nice :-)

No comments: