To modify the isolation level of the JDBC Connection DB2 database in a WebSphere environment

*

Web project Framework

Struts2.3.24.3,spring,jdbctemplate

Database: DB2

webserver:webspherev8.5

Scenario: When developing with Tomcat, if the lock table, then update, will appear deadlockloserdataaccessexception, after catching the exception, Tomcat normal;

However, after posting to WebSphere, deadlock or timeout,

Found that the problem is not on the update, but locked the table after the table's select operation caused;

Workaround:

1, go to the WebSphere console page, resources >jdbc> data Source > select the data source to use, click on Enter, customize properties on the right,

On the third page of the custom list, find Webspheredefaultisolationlevel, edit as 2, default is 4

*

To modify the isolation level of the JDBC Connection DB2 database in a WebSphere environment