Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Failed to initialize asynchronous Adaptive Model response



Error shows up in the Decisioning ->Infrastructure-> Services - Failed to initialize asynchronous Adaptive Model response dispatcher.
User has two data centers - ADM services run in one data center.
Use Store and Forward remote messaging in clustered environment.

Error Messages

Failed to initialize asynchronous Adaptive Model response dispatcher.

Steps to Reproduce

Go to Decisioning >Infrastructure> Services and click save and ping.

Root Cause

Weblogic configuration issue on the ADM server.


Perform the following local-change: 

Setup JMS on the ADM server as described in the PRPC documentation, and then ensure that each cluster of PRPC servers has a Foreign (JMS) Server declared which points to the ADM server.
Step by step:
  1. Setup JMS on the ADM Server
    1. Via the Admin console of the WebLogic installation that contains the ADM Server, create a new JMS server named ADM JMS Server
    2. Add the server running the ADM service as the target for this JMS server
    3. Create a new JMS system module named ADM JMS Module
    4. Select the server running the ADM service as the target for this module
    5. Once created, select this module from the JMS Modules section. On the default Configuration tab, click New and add a Queue resource using the following information:

      Name: ADM Queue
      JNDI Name: jms/admRequestDestination

      During this process, create a new subdeployment for the queue, and target the ADM JMS Server you created previously.
    6. Once back on the Configuration tab of the ADM JMS Module, create another new resource: a connection factory. Use the following information:

      Name: ADM Request Connection Factory
      JNDI Name: jms/admRequestConnectionFactory

JMS is now configured on the ADM Server.
  1. Setup a JMS Foreign Server on each WebLogic installation containing PRPC servers
    1. Using the Domain Structure tree on the Admin console, navigate to Services – Messaging – JMS Modules
    2. As PRPC JMS should already be configured, you should see the following (or a similarly named) module:

      Click into this module, and then click add a new resource.
    3. This resource should be a Foreign Server. Call it ADM Server, and add all the PRPC servers in this installation as targets
    4. When returned to the PRJMS_Module screen, click into the new resource you’ve created. Under the Configuration - General tab, add the JNDI Connection URL using the information relevant for your ADM Server installation.

      For example, if your ADM Server is deployed on a WebLogic system on address, port 7676, your URL should be

      T3 is WebLogic’s proprietary RMI protocol, and should be used here.
    5. After saving this, navigate to the Configuration – Destinations tab of the ADM Server Foreign Server resource
    6. Create a new Foreign JMS Destination using the following information:

      Name: ADM Queue
      Local JNDI Name: jms/admRequestDestination
      Remote JNDI Name: jms/admRequestDestination

    7. Now navigate to the Configuration – Connection Factories tab of the ADM Server Foreign Server resource
    8. Create a new  Foreign Connection Factory using the following information:

      Name: ADM Connection Factory
      Local JNDI Name: jms/admRequestConnectionFactory
      Remote JNDI Name: jms/admRequestConnectionFactory

    9. The entire WebLogic installation will now need to be restarted before these changes take effect (regardless of what the Admin console says when changes are activated).
This WebLogic installation is now configured; we’ve defined our ADM Server as a JMS Foreign Server, hooked it up to our PRPC servers via its targets, and mapped both the ADM queue and connection factory from local JNDI (on PRPC servers) to remote (on ADM server).

Step 2 above should now be repeated on all WebLogic installations that contain PRPC servers we wish to connect to ADM – even if one of those installations actually contains the ADM Server itself.

Published March 2, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us