RS03579: DECISION RUNNER MAY FAIL TO RUN TEST SUITE IN A SPECIFIC ENVIRONMENT

IBM Operational Decision Manager V8.10.4 Download Document
IBM Operational Decision Manager for z/OS 8.10.4 Mod Pack
Operational Decision Manager V8.10.2.2: Interim Fix 3
Operational Decision Manager V8.10.2.2: Interim Fix 4
Operational Decision Manager V8.10.2.2: Interim Fix 7 for Decision Server
IBM Operational Decision Manager V8.10.5 Download Document
IBM Operational Decision Manager V8.10.5 Refresh Pack

APAR status

• Closed as program error.

Error description

• In one specific customer environment with ODM 8.10.2, Oracle DB
  (OCI driver 18.3) and tomcat 8.5, all test suites launched from
  the Business Console fail with the exception below in the
  log.
  After investigation, it turns out that the DB transactions
  are not automatically committed as expected, for some reasons
  that have not been
  identified.
  
  com.ibm.rules.res.logging.internal.RESLogger.log
  An internal error occurred in Decision Batch Runner: Error
  occurred while getting the status for the job with execution
  identifier 123
  
  
  com.ibm.rules.cdi.core.service.output.ScenarioSuiteException:
  Error occurred while getting the status for the job with
  execution identifier 123
  
   at com.ibm.rules.cdi.runtime.Decision
  RunnerController.getStatus(DecisionRunnerController.java:888)
  
  
  at com.ibm.rules.cdi.server.rest.api.DecisionRunnerAPIImplV1.pro
  cessGetRequest(DecisionRunnerAPIImplV1.java:91)
  
   at com.ibm.rul
  es.cdi.server.servlet.DecisionRunnerRestServlet.handleRequest(De
  cisionRunnerRestServlet.java:291)
  
   at com.ibm.rules.cdi.server.
  servlet.DecisionRunnerRestServlet.doGet(DecisionRunnerRestServle
  t.java:249)
  
   at javax.servlet.http.HttpServlet.service(HttpServ
  let.java:635)
  
  ...
  
  Caused by:
  com.ibm.rules.cdi.persistence.NoSuchJobExecutionIdException:
  Cannot retrieve in database the job execution ID: 123.
  
   at com.
  ibm.rules.cdi.persistence.internal.service.PersistenceServiceImp
  
  l.checkIfJobExecutionIdExists(PersistenceServiceImpl.java:738)
  
  
  at com.ibm.rules.cdi.runtime.DecisionRunnerController.getStatus(
  DecisionRunnerController.java:786)
  
   ... 27 more
  
  Caused by:
  javax.batch.operations.NoSuchJobExecutionException: Cannot find
  the job instance that is associated with the job execution ID:
  123.
  
   at com.ibm.rules.cdi.persistence.internal.service.Persist
  enceServiceImpl.getJobInstanceIdByExecutionId(PersistenceService
  Impl.java:679)
  
   at com.ibm.rules.cdi.persistence.internal.servi
  ce.PersistenceServiceImpl.checkIfJobExecutionIdExists(Persistenc
  eServiceImpl.java:735)
  
   ... 28 more
  
  10-Oct-2019 10:58:29.874
  SEVERE [http-apr-172.23.242.181-32401-exec-10]
  com.ibm.rules.res.logging.internal.RESLogger.log An internal
  error occurred in Decision Batch Runner: Error occurred while
  deleting data for the job with execution identifier 123
  
  
  com.ibm.rules.cdi.core.service.output.ScenarioSuiteException:
  Error occurred while deleting data for the job with execution
  identifier 123
  
   at com.ibm.rules.cdi.runtime.DecisionRunnerCont
  roller.deleteJobData(DecisionRunnerController.java:715)
  
   at com
  .ibm.rules.cdi.server.rest.api.DecisionRunnerAPIImplV1.processPo
  stRequest(DecisionRunnerAPIImplV1.java:229)
  
   at com.ibm.rules.c
  di.server.servlet.DecisionRunnerRestServlet.handleRequest(Decisi
  onRunnerRestServlet.java:293)
  
   at com.ibm.rules.cdi.server.serv
  let.DecisionRunnerRestServlet.doPost(DecisionRunnerRestServlet.j
  ava:256)
  
   at
  javax.servlet.http.HttpServlet.service(HttpServlet.java:661)
  
  
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
  

Local fix

• Add the lines below in the WEB-INF\web.xml file in
  decisionrunner.war :
  
   <context-param>
  <description>transaction support</description>
  <param-name>datasourcePersistenceTransactional</param-name>
  <param-value>true</param-value>
   </context-param>
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users running a test suite in a specific environment.        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In one specific environment with ODM 8.10.2, Oracle DB (OCI  *
  * driver 18.3) and tomcat 8.5, all test suites launched from   *
  * the Business Console fail.                                   *
  * After investigation, it turns out that the DB transactions   *
  * are not automatically committed as expected.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Decision Runner now double-checks that the driver is set in
  'autocommit' mode.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WDS FOR RULES

• Fixed component ID

  5725B6903

Applicable component levels

• R8A0 PSY

     UP