We have an application that creates non-session-scoped locks which mean that sometimes if the application is not shut down cleanly we somtimes have orphaned/dangling locks on some nodes.
The API for lock manager .unlock says ... --- Note however that the system may give permission to a non-owning session to unlock a lock. Typically such "lock-superuser" capability is intended to facilitate administrational clean-up of orphaned open-scoped locks. --- Is there anyway I can do this in jackrabbit out of the box ? - how can I get the "system" to "give permission" in the described way ?. Id also be interested in knowing how node level locks are physically implemented for a file based respository. Cheers. -- View this message in context: http://jackrabbit.510166.n4.nabble.com/lock-administration-tp3936482p3936482.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
