My Oracle Support Banner

PRIMARY_JTS Not Updated When Timeout Value Is Set In Connection Pool (Doc ID 1327965.1)

Last updated on NOVEMBER 01, 2018

Applies to:

Oracle Transportation Management - Version 6.2.1 and later
Information in this document applies to any platform.
***Checked for relevance on 02-Jan-2013***

Symptoms

The issue occurs after moving a DB and trying to point OTM to the new DB.

The new database - of course - has a new connection string and to point OTM at the new database, the connection info in the glog.properties is changed accordingly. But it appears that the PRIMARY_JTS doesn't seem to be updated when restarting the app server if the connection_pool has a timeout specified.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.