...

• Starting from Release 2.0.0 the PLSQLJob
  • is implemented on top of the JDBC Interface of the Oracle® JDBC Driver, 
  • with a commit operation being performed by the Oracle® JDBC Driver when a connection is closed without an explicit commit or rollback.
• Starting from Release 2.7.1 the PLSQLJob
  • is implemented using Hibernate,
  • with no commit or rollback operation being performed when the connection is closed.
• Starting from Release 2.7.2 the PLSQLJob
  • makes use of the Hikari connection pool that ships with Hibernate,
  • performs a rollback operation when a connection is closed,
  • closes the connection in the event that a cancel/kill force or suspend/kill force operation is performed on the order.

  • Jira
    server SOS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JITL-743

...

• The cancel operation is applied to the order, not to the PLSQLJob. In case of cancellation the job will continue until completion and the order will be put in set to the failed state.
• The cancel/killforce operation is applied to the order and to the job. The PLSQLJob will be killed will be forcibly terminated, transactions are rolled back, the database connection will be closed and the DBMS session will be terminated. The order will be put in set to the failed state.The DBMS decides about rolling back transactions when closing the client session.

Further Resources

• JS7 - JITL SQLPLUSJob
• JS7 - JITL SQLExecutorJob
• JS7 - JITL Common Variables
• JS7 - Job Resources
• JS7 - Use of Credential Store with JITL Jobs

...