Hmmm.. that's a bug for sure...
We should fix it...
Do you want to open a JIRA? If you have a fix... feel free to commit it.. you are still a committer :-)
Forgot to mention it's on 2.2.5.Final release.
I'll check if it also on the trunk and provide a fix for it if it's still there
Trunk is a bit unstable right now.... I'm working on that...
Right now we are doing work on Branch_2_2_EAP and Branch_2_2_AS7....
I'm working on bringing trunk fixed an up to date as we speak. It's all my fault but it's just a lot of work to be done now :-)
Actually, I observe such a behaviour since 2.2.0.
I am just starting to contribute to the project working my way from minor to major bugs. I can see that although this thread is relatively old, the issue still exists, so I gave it a try.
From what I can understand there are 2 ways to deal with this:
1) Assign an InVMNodeManager in case of no persistence
2) Assign a different lock file to each server instance
I went with the 1st approach and made a pull request, but if you are more keen to use the 2nd (or any other) feel free to state it in the PR. I would be more than happy to give it another try.