Geocoder Chached Session Leads To Thread Contention
Last updated on FEBRUARY 08, 2017
Applies to:Oracle Spatial - Version 220.127.116.11 to 18.104.22.168 [Release 11.2]
Information in this document applies to any platform.
Geocoder application 22.214.171.124
Geocoder retrieves only one database connection from JDBC DataSource, caches it and then shares it among all threads requiring access to database:
Every thread spawn from a request to GCServer servlet that need a connection to database calls method Geocoder.getConnection().
The problem is that the first time the method is called, it caches the connection in ConnectionManager.conn public instance member,
and further calls to this method will always return the same connection.
This behavior leads to thread contention since most of the methods of the underlying implementation of java.sql.Connection are synchronized.
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