SA-13605

Summary

When starting the application in the Acceptance environment, there is an error message "Failed to initialize ADM Async response dispatcher" observed in the logs.

However, the same configuration exists in the DEV environment and works correctly. The only difference between the DEV and Acceptance environments is the production Level and that VBD and ADM are deployed to different websphere clusters in Acceptance (and the same Websphere cluster in DEV).

When viewing the Decisioning:Services screen, the Embedded Process option is not available on the Acceptance environment but is available on DEV. Also, the versions of the admin service are a little different (although this may be because one env is using the embedded process and the other is not - because it can not).

The websphere JMS configuration does not follow the instructions in the installation guide for DSM literally as an ESB is used, not a SIB. Both environments use this configuration.

Error Messages

[8/18/15 12:25:17:406 CEST] 000001db XmlBeanDefini I org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions Loading XML bean definitions from class path resource [com/pega/decision/adm/webapp/adm-client-config.xml]
[8/18/15 12:25:20:167 CEST] 000001c3 P2PGroup I ODCF8040I: Detected process was85\was85node02\cluster-nodename-appsrv02 started.
[8/18/15 12:25:25:037 CEST] 0000009e SystemOut O 2015-08-18 12:25:25,016 [.PegaWorkManager : 7] [ STANDARD] [ ] [ PegaDM:07.10] ( adm.client.ClientFactory) ERROR - Failed to initializeRemoteServer asynchronous response dispatcher
com.pega.decision.adm.client.ADMException: Failed to initialize ADM Async response dispatcher. Exception details: com.pega.decision.adm.client.ADMException: javax.naming.NameNotFoundException: Context: was85/clusters/cluster-nodename, name: jms/admRequestDestination: First component in name jms/admRequestDestination not found.
at com.pega.decision.adm.client.ADMException.raise(ADMException.java:39)
at com.pega.decision.adm.client.jms.ADMAsyncResponseDispatcher.getInstance(ADMAsyncResponseDispatcher.java:37)
at com.pega.decision.adm.client.ClientFactory.initialize(ClientFactory.java:168)
at com.pega.decision.adm.client.ClientFactory.initializeRemoteServer(ClientFactory.java:156)
at com.pega.decision.adm.client.ClientFactory.initializeClient(ClientFactory.java:85)
at com.pegarules.generated.pzGetADMClient_071017_5Mv359_fpWjNHJtzx0feQQ.pzGetADMClient07_10_17(pzGetADMClient_071017_5Mv359_fpWjNHJtzx0feQQ.java:103)
at com.pegarules.generated.pzGetADMClient_071017_5Mv359_fpWjNHJtzx0feQQ.invoke(pzGetADMClient_071017_5Mv359_fpWjNHJtzx0feQQ.java:78)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:133)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:110)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:8954)
at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflection(LibrarySupport.java:181)
.
.
.
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:796)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)

Steps to Reproduce

Setup ADM and PRPC in a seperate clusters. Start the servers.

Root Cause

A defect or configuration issue in the operating environment. Requirement was to setup separate Websphere clusters for PRPC and ADM, because ADM cannot be clustered, only one server will be running at ADM Cluster. ADM JMS resources need to be visible to both PRPC and ADM Cluster.

Resolution

The local-change is to add both PRPC and ADM clusters to a Websphere Cell and create the ADM JMS resources at Cell level.