PRIMARY_JTS Not Updated When Timeout Value Is Set In Connection Pool
Last updated on MARCH 08, 2017
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***
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.
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