Access Keys:
Skip to content (Access Key - 0)

How to decode Lock IDs in Rhino logs

Print this page

Investigating lock timeouts

Sometimes you may see reports in Rhino logs of lock timeouts. For example this may happen under load. The log messages refer to a lock ID. The lock ID contains potentially useful information about the resource Rhino is attempting to lock.

This how-to guide explains how you can decode these lock IDs and relate them to what your application is doing. This is potentially helpful for tuning your application and detecting lock contention.

Application-level (not language-level) locks
The locks this guide discusses are application-level locks, which Rhino (2.0 and previous versions) uses to control access to transactional SLEE state. These locks are not related to Java's language-level locks (synchronized) or java.util.concurrent.locks library.

Below are an introduction to tracing locks using Rhino logs, investigating the distributed locks your applications have acquired, and decoding their lock IDs, making reference to common examples.

Adaptavist Theme Builder Powered by Atlassian Confluence