Based on the comment [1], it appears that the following scenario should not result in errors:

1. Obtain a shallow open-scoped lock on a node and set timeout hint to 1 second.
2. Wait for 1 minute to ensure that the lock is expired.
3. Lock the node without any errors.

However, the steps outlined above would result in the exception that looks like this:

Caused by: javax.jcr.lock.LockException: The node at '/6269cc6c-9253-4db8-bd16-b319a1bc779f' is already locked
	at org.modeshape.jcr.JcrLockManager.lock(JcrLockManager.java:267)
	at org.modeshape.jcr.JcrLockManager.lock(JcrLockManager.java:238)

If this is indeed a valid problem and it is addressed, it would effectively eliminate the need for [2] and [3].

[1] https://developer.jboss.org/message/963202#963202
[2] https://issues.jboss.org/browse/MODE-2631
[3] https://github.com/ModeShape/modeshape/pull/1596