Troubleshoot connection timeouts when running a wsadmin script

Running a wsadmin administrative script that calls an MBean in a network deployment environment results in several connections between server processes using JMX connectors for...

• deployment manager
• node agent
• cluster member

Some IBM Connections administrative scripts can run for longer than the default connection timeout specified for the connector used, resulting in messages like...

WASX7017E: Exception received while running file "/install_root/ProcessChoreographer/admin/script_name"; exception information: javax.management.JMRuntimeException: ADMN0034E: The service is unable to obtain a valid administrative client to connect process "nodeagent" from process "dmgr", because of exception: com.ibm.websphere.management.exception.ConnectorException:
ADMC0009E: The system failed to make the SOAP RPC call: invoke.

Reasoning

Some IBM Connections administrative scripts can perform database operations on large numbers of database objects. This means they can run for longer than the default connection timeout. When a wsadmin script is run with a connection to the server, the following connection timeouts can happen:

• For connection from wsadmin to the deployment manager, default is 180 seconds.
• For connection from dmgr to the nodeagent, default is 600 seconds.
• For connection from nodeagent to the runtime deployment target, default is 600 seconds.

Resolution

You have the following options:

• Modify the invocation parameters so that less work is performed, so the operation completes before the timeout. For example, many scripts have parameters that can be used to select fewer objects.

• Modify the properties for the connector used.

  Remote JMX connector	Used between server processes residing on different physical machines, for example, between the deployment manager and the node agent. The default is the SOAP connector.
  Local JMX connector	Used between server processes residing on the same physical machine, for example, between the node agent and its application servers. The default is the IPC connector.

  Edit...

  • soap.client.props file
  • ipc.client.props
  • sas.client.prop files

  ...and set the properties for the deployment manager and the node agents where members of the runtime deployment target are running. For example, to change the SOAP connector properties.

  1. Modify the property...
     com.ibm.SOAP.requestTimeout

     ...in...

     profile_root/properties/soap.client.props file

  2. Change the requestTimeout custom property using the administrative console:

     1. For servers or cluster members, click...
        Servers | Application servers | server_name | Server Infrastructure | Administration | Administration Services | Additional properties | JMX Connectors | SOAPConnector | Additional Properties | Custom properties

        ...then locate the requestTimeout custom property, and modify its value.

     2. For the deployment manager, click...
        System administration | dmgr | Additional Properties | Administration Services | Additional properties | JMX Connectors | SOAPConnector | Additional Properties | Custom properties

        ...then locate the requestTimeout custom property, and modify its value.

     3. For the node agents, click...
        System administration | Node agents | node_agent_name | Additional Properties | Administration Services | Additional properties | JMX Connectors | SOAPConnector | Additional Properties | Custom properties

        Then locate the requestTimeout custom property, and modify its value.

Parent topic:
Troubleshooting tips