ITI-41 Doesn't Respect JTA Transaction Timeouts (Doc ID 2266292.1)

Last updated on MAY 15, 2017

Applies to:

Oracle Healthcare Data Repository - Version 7.0.1 and later
Information in this document applies to any platform.

Symptoms

On : 7.0.1 version, RIM Query

ACTUAL BEHAVIOR
---------------
Customer noticed that the ITI-41 service doesn't respect the JTA timeout setting (in WLS Console - Services > JTA > Timeout Seconds).
What they are seeing is even though their request long times out, the ITI-41 transaction keeps running and completes successfully.


EXPECTED BEHAVIOR
--------------
They would like the ITI-41 service implement something like the following (as they did in the custom persist service at MHR)...

ctx = new InitialContext();
utx = (UserTransaction) ctx.lookup("java:comp/UserTransaction");
utx.begin();

...
rimService.submit(controlAct);

long elapsedTime = (System.currentTimeMillis() - mPersistStartTime);
LOG.debug("Elapsed time so far: " + elapsedTime + " ms");



utx.commit();
LOG.info("Persist time: " + (System.currentTimeMillis() - startTime) + "ms");

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms