Bug report

Should a timeout occur when trying to retrieve journal entries the connector closes the connection but the job may leave a job running.

Should this be a repeatable issue then more jobs will be created each time the timeout occurs.

What Debezium connector do you use and what version?

debezium-connector-ibmi - 3.1.0-SNAPSHOT

What is the connector configuration?

NA

What is the captured database version and mode of deployment?

DB2 on prem

What behavior do you expect?

Jobs to be terminated when the connector is interrupted

What behavior do you see?

jobs mounting up and running for long periods

Do you see the same behaviour using the latest released Debezium version?

Yes

Do you have the connector logs, ideally from start till finish?

can be provided

How to reproduce the issue using our tutorial deployment?

When the debezium is down for a period of time and the receiver it was on is deleted, it tries to restart from the first receiver that exists, if there are no journal entries for the tables of interest and there are sufficient entries to parse this will always timeout

Feature request or enhancement

Need to also fix the restart from beginning so it doesn't request from the entire range

Which use case/requirement will be addressed by the proposed feature?

denial of service on the iseries from number of jobs started

Implementation ideas (optional)

kill the job in the interrupt sequence