WmPublic. Retrieves the retry count and the maximum retry count for a service.

The retry count indicates the number of times the Integration Server has re-executed a service. For example, a retry count of 1 indicates that the Integration Server tried to execute the service twice (the initial attempt and then one retry). The maximum retry count indicates the maximum number of times theIntegration Server can re-execute the service if it continues to fail because of an ISRuntimeException.

None.

Although the pub.flow:getRetryCount service can be invoked at any point in a flow service, the pub.flow:getRetryCount service retrieves retry information for the service within which it is invoked. That is, you can use the pub.flow:getRetryCount service to retrieve retry information for top-level services or services invoked by a trigger only. The pub.flow:getRetryCount service does not retrieve retry information for a nested service (a service that is invoked by another service).

The Integration Server retries a service that is configured to retry if the service uses the pub.flow:throwISRuntimeException service to catch a transient error and re-throw it as an ISRuntimeException. The Integration Server will also retry a service written in Java if the service throws an exception using com.wm.app.b2b.server.ISRuntimeException(). For more information about constructing com.wm.app.b2b.server.ISRuntimeExceptions in Java services, see the webMethods Integration Server Java API Referencefor the com.wm.app.b2b.server.ISRuntimeException class.

The maximum number of times the Integration Server retries a service depends on the value of the Max attempts property for the service. If the service is invoked by a trigger, the retry behavior is determined by the trigger retry properties.