Troubleshooting issues when adapters are enabled on a remote peer

When any adapter is enabled on a remote peer such as the Activity Peer or the Lightweight Activity Peer, and a job is executed on the CDP, the CDP only waits for one hour before assuming that something has happened to the request or to the LAP and terminates the connection. To prevent the process from expiring, one must create the $BAO_HOME/config/tuning-config.xml file. 

 Open the file and add the following XML:

<config>
   <adapter-manager>
      <adapter-call-timeout>3600000</adapter-call-timeout>
   </adapter-manager>
</config>

The default value is in milliseconds, so 3600000 is one hour.

Change this value to a setting that works for you and restart the peer. You must add this setting to the tuning-config.xml file on every peer, including LAPs. Also, if you provide invalid XML in the file, you may see unexpected behavior in your grid.

For more information, see BMC Knowledge Base article, KA400574

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments