Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.0.0
-
None
Description
Current Situation
- The Cancel/Kill operation is implemented for the Shell jobs and has no effect on the JITL(Java) jobs.
Test Instructions
- SSH Jobs
- com.sos.jitl.jobs.ssh.SSHJob
- Configure a workflow with the SSH job. Use a long running command.
- Cancel/Kill this workflow while the workflow (the SSH Job) is running.
- Check execution result: order state, order protocoll, SSH Server logs - make shure that the client was disconnected after the Cancel/Kill operation.
- com.sos.jitl.jobs.ssh.SSHJob
- Database Jobs
- com.sos.jitl.jobs.db.SQLExecutorJob
- Configure a workflow with this job. Use a long running query (e.g. MySQL: SELECT SLEEP(30)).
- Cancel/Kill this workflow while the workflow (the database Job) is running.
- Check execution result: order state, order protocoll, Database Server logs - make shure that the client/session was disconnected after the Cancel/Kill operation.
- Examples monitoring tools:
- MySQL: Client Connections view
- Oracle: SELECT * FROM V$SESSION WHERE USERNAME='<js7 database user>'
- Examples monitoring tools:
- Repeat the Test for the supported DBMSs (MySQL, MS SQL Server, Oracle, PgSQL)
- com.sos.jitl.jobs.db.oracle.PLSQLJob and com.sos.jitl.jobs.db.oracle.SQLPLUSJob
- See Test instructions above. Oracle only.
- com.sos.jitl.jobs.db.SQLExecutorJob