Kbase P154953: Lock Table continuing to grow for a JDBC client even though they have a transaction Isolation level
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/08/2010 |
|
Status: Verified
SYMPTOM(s):
Lock Table continuing to grow for a JDBC client
promon showing 2 million record get locks in the Activity screen for the period when the JDBC application is being ran against the database.
FACT(s) (Environment):
Auto commit is being used for the JDBC connection.
JDBC client that is accumulating locks has an transaction isolation level of READ_UNCOMMITTED within the application.
All Supported Operating Systems
OpenEdge 10.x
CAUSE:
Transaction isolation level was not being set for a single connection within the application. The JDBC application was making use of multiple connections to gather data.
FIX:
Set the transaction isolation level to READ_UNCOMMITTED for all connections occurring within the application where a Record lock is not needed. or Change the application to only make use of a single connection to the database when gathering data.