Pausing sending messages

To pause sending messages to ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for sending messages.
  3. In the Sending Paused column, click Pause. The page is automatically refreshed and the Sending Paused check box is selected.
    A Resume button becomes available.
Sending of messages by this connection point is paused. It is relevant for scenarios which are creating documents in ION. Application - Send from application, File - Read, API - Get from API, Database - Read and so on. No new messages are picked up or received from the source. The connection point still processes messages that were already picked up or received. This action can take some time in the background even though the sending status of the connection point is already changed to Paused.

Any new message, that was published after its connection point is paused, has not yet entered ION and is not yet available in ION OneView.

When the connection point is paused, no new schedules are added to the queue. If there was a job in the queue before the connection point was paused, then the job is executed when the connection point is resumed. It is not replaced, not even when there are newer scheduled jobs.

Connection point specific considerations:

  • IMS - When Sending is paused, IMS rejects incoming messages with an http status code 503 (Service unavailable) which triggers the application to retry sending messages. In the body of the response a new error code 490 is included to indicate the service is unavailable because its paused.

  • AnySQL - The behavior is consistent with other connection points. If the connection point is paused, and AnySQL extraction is in progress, then the extraction is not interrupted. It means that the AnySQL can still continue producing new documents. But no new extractions are started.

  • Network - When Sending is paused on the target side, the network connection point goes into error state on the source side. The retry mechanism is started. When the target network connection point is resumed, the message automatically continues to be sent again.