Why does HVR kill capture & integrate agents when suspending a job

This topic contains 1 reply, has 2 voices, and was last updated by  Frank Knot 1 month, 1 week ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #8871

    Frank Knot
    Participant

    When a running job with a capture / integrate agent (action agent / agentplugin) is suspended in the HVR scheduler, HVR seems to kill the agent. Is this correct behaviour and why is HVR doing this.

    #8873

    Frank Knot
    Participant

    The Capture / Integrate agent as defined with the agent / agentplugin action is running as an integral part of the replication stream. It is part of the replication job (hence the term plug in), HVR is capturing its output & status and acts upon it.

    When a running replication job is suspended, HVR will clean up all parts of this job including a running agent.

    This clean up is done gracefully, by sending a termination signal to the agent process . The agent can therefore be programmed to catch the termination signal and perform a proper rollback when needed.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

© 2017 HVR Software

Request Trial Contact Us