The Runtime Service cannot communicate with the Access Service Portal

You must edit or replace this page before making it public.

The information below details some of the possible scenarios when this error occurs, and how to troubleshoot it.

For the exact reason why this communication failed, refer to the Local Log file of the Runtime Service in the <garoot>/log directory. The filename format is: LocalLog_RUNTIME_<instance><n>_<pid>.log.

For detailed descriptions of the causes and their solutions, refer to the Troubleshooting Guide.

Possible reasons for this error

All or some of the Access Services listed in the gaAccessServiceLocations setting are invalid, or inaccessible

Solution

Check:

• the setting validity. The setting is valid if the format is <cluster>:<node>:<port> . The node name is also used to connect to that machine, so make sure the node can be resolved into an IP address.
• if all the Access Service Portals are running
• if the connectivity between the Access Service Portal and Runtime Service is good by pinging the Access Service Portal machines from the machine hosting Runtime Service.

You are using the RuntimeSSL setting, but the SSL flags are not enabled in both the Runtime Service and server machines

Solution

Check:

• if the SSL flags are correctly enabled in both Runtime and server machines using the gaRuntimeSSL flag
• if the KeyStore is transferred properly. Check the gaKeyStore setting in both the server and Runtime Service machines, and ensure the gaCA entry is the same in both the machines. (This means that both machines are trusting the same Certification Authority (CA).

You are using either PAT or NAT, but the proxy information is not properly configured

Solution

Check:

• if the Access Service locations listed in the configuration file contain the proxy (translated) IP addresses and proxy ports, not the real IP addresses and port numbers.

The AJP Listener in the Infrastructure Service cannot accept the amount of connections required by all the Runtime Services

Solution

Check the maxProcessors attribute in the AJP Listener, using the server.xml file located in the <garoot>/infrastructure/<instanceName>/conf directory.

None of the above scenarios are applicable

Solution

Refer to the Troubleshooting Guide.

Customizing this error message

To customize this message, edit the <garoot>/templates/Runtime/InfrastructureError.html file.

Alternatively, define the <gaInfrastructureErrorTemplate> setting in the Runtime main instance, and specify the filename that contains the error template.