Previous Topic Next topic Print topic


Handling XA Connection Errors

The way a server instance handles XA resource connection errors is controlled by the following environment variables:

ES_XA_RECONNECT
If this environment variable is set to True, when an error occurs on a call to XA, the server attempts to reconnect to the Resource Manager.

If it cannot reconnect, the server monitors the number of attempts made.

ES_XA_????_NB_RETRIES
The format for setting this is:
ES_XA_????_NB_RETRIES=nnnn

where ???? defines the XA ID, and nnnn is the number of subsequent XA call failures allowed before the SEP is recycled and the switch disabled. The default is 5 and its maximum value is 254. If you set nnnn to -1 or a number greater than 254, your switch module will never be disabled and reconnection attempts will continue indefinitely.

If the maximum number of call failures is reached, disabling your switch module, and ES_XA_RECONNECT is set to True, you can reenable the switch by starting Enterprise Server Monitoring and Control (ESMAC) and performing the following steps:

To start ESMAC:

  1. Access the Enterprise Server Administration screen for your installation.
  2. In the table of Enterprise Server instances, check that the server you want has started, and if not, start it.
  3. In the Status column of the Enterprise Server instance to monitor, click Details.

    The Details screen for the server is displayed.

  4. On the Details screen, select the Server > Control tab, then click ES Monitor & Control.

    The Enterprise Server Monitoring and Control (ESMAC) screen is displayed.

To reenable the switch module:

  1. In the Resources options, select Active.
  2. Select XAT.
  3. Click on the relevant disabled resource from the list of active ones to open the details for that XAT.
  4. Check the Enable box.
Previous Topic Next topic Print topic