Different locking behaviour from jetty to WAS

Question

I am working on a web application with processes running on separate threads using spring's taskexecutor (uses workmanager on WAS and threadpool on jetty).

The app uses spring/hibernate/db2(udb).

The async process creates a record with the status and progress, which can be viewed in a page with the process history.

When running on websphere and attempt to access the list of processes, it seems to be waiting for the process to finish and finally throws a "file in use" sql exception and rollbacks the changes. This does not happen on jetty with same database.

My question is, why am I seeing different locking behaviors from jetty to websphere and how can I fix this. jdbc driver settings are default on both.

Answer 1

Looks like the two containers use different transaction isolation levels. See if this helps for WAS: http://www-01.ibm.com/support/docview.wss?uid=nas8N1012999. To quote, "This document will discuss how, what, and where transaction isolation levels are set in WebSphere Applications by default and for specific resource references."