HornetQ server.lock file created when no persistency is enabled.

Solution Verified - Updated -

Issue

I did not expect the attached server.lock file to be created based on my configuration for HornetQ server. It seems to be a bug in HornetQ code; I believe I have the same issue as the one described be in this URL1

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content