[ https://hibernate.onjira.com/browse/HHH-1512?page=com.atlassian.jira.plug... ] Steve Ebersole commented on HHH-1512: ------------------------------------- Strong, as I said here 5 years ago, I think the correct solution is to alter thew DB2 dialect to use {{for read only with rs use and keep update locks}} or {{for read only with rr use and keep update locks}}. But as I also said, I am not a DB2 expert and we need help from DB2 users to verify this. Ideally we'd really just have someone to take ownership of these dialects, but we've been asking for that for 5 years as well, so I am not holding my breath on that. I am using the following resources: * http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db2z... * http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db2z... It sounds like the type of lock to request in the {{use and keep}} portion is what we need to resolve. Using {{for read only with[rs|rr]}} seems absolutely correct. That second link describes the "lock modes". We need to choose between: * {{use and keep update locks}} Will allow other transactions to read the locked row(s) but only with shared lock mode (aka only if the other transaction does not request pessimistic lock) * {{use and keep exclusive locks}} Will not allow other transactions to read the locked row(s) at all. So we are back to where we were 5 years ago :) I think we should use {{for read only with rs use and keep update locks}} or {{for read only with rr use and keep update locks}} but need some DB2 users to verify that changing the dialect that way works as anticipated by description here. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira