|
| Our server is WebSphere v.5.0.2. We are having occasional problems with blocks that won't release. The application does the following:
gets that database connection using jdo.getDatabase()
calls db.begin()
produces the select string with OQL and calls DB.getOQLQuery
binds the arguments
calls oql.execute to get the resultset
processes the resultset
closes the resultset
closes the OQL
closes the DB connection
The problem is that the connection starts blocking other connections within MS SQL. This is fine as the first connection might run for a while. But there are times that the first connection never finishes. According to MS SQL admin screens the connection
should be done(sleeping). But the application is still setting at the oql.execute statement. The execute never finishes. The first connection keeps all of the blocks in the DB and other connections are not able to complete. To get the processes running ag
ain we kill the connection from within MS SQL. This returns a stale connection error to the application and all of the other connections will start flowing. MS SQL DBAs tell me that it's something within the Java code. I cannot find any errors there.
Has anyone ever run across this before?
|
|