qpidd critical error: Cannot lock file continues in running
Issue
A standalone (non-clustered) broker prints error "critical Unexpected error: Cannot lock" on start up. Despite the highest severity it continues in running.
Moreover, all durable queues are not accessible then (qpid-stat -q shows no durable queue present).
Why the error was hit?
Shouldn't this critical error prevent the broker from starting up?
Environment
- MRG Messaging 2.0, 2.1 and 2.2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.