testQueryTimeout & testQueryTimeoutEMProps expect a QueryTimeoutException to be thrown when attempting to read-lock a write-locked entry. Since the read & lock used to be 1 query, the timeout would have worked fine originally. But now, since the read succeeds immediately and the read-lock isn't applied until afterwards, is the QueryTimeoutException no longer thrown?

Does the test need to change? Or, does the Query timeout need to be applied to the follow-on lock instead of the read?

I believe testContendedPessimisticLock is the same or related issue.

Hopefully that makes sense – might be using the wrong terms.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira