Starting and stopping all callout threads

You can start and stop the callout threads by using the SOAP Gateway management utility.

The worker thread pool must be started before you can start callout threads.

The callout threads poll defined tpipes for new callout request messages and then add the messages to the work queue. If the callout threads are stopped, SOAP Gateway does not poll tpipes for new callout request messages.

The worker thread pool pulls messages from the work queue and open connections to external web services. If the worker thread pool is stopped, the work queue fills up with unprocessed messages and SOAP Gateway halts callout processing.

The server must have an active HTTP listening port before you can issue callout thread management commands.

  1. Ensure that the worker thread pool is started with the iogmgmt -view -workerthreads command.
  2. Start all callout threads with the iogmgmt -callout -startall command.
  3. Optional: Verify that the callout threads are started with the iogmgmt -view -calloutthreads command.
The callout threads begin processing callout request messages.
Before you stop the worker thread pool, stop all callout threads with the iogmgmt -callout -stopall command. Stopping callout threads before you stop the worker thread pool ensures that no callout request messages are left unprocessed in the work queue.