HDR: ITI-41 Doesn't Respect JTA Transaction Timeouts
Last updated on SEPTEMBER 12, 2017
Applies to:Oracle Healthcare Data Repository - Version 7.0.1 and later
Information in this document applies to any platform.
On : 7.0.1 version, RIM Query
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.
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");
long elapsedTime = (System.currentTimeMillis() - mPersistStartTime);
LOG.debug("Elapsed time so far: " + elapsedTime + " ms");
LOG.info("Persist time: " + (System.currentTimeMillis() - startTime) + "ms");
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