stale lock file

Details

Description

This happents quite regularly in last week but still pretty randomly
(sometimes whole make checks works well on the same revision
on which it did not a while ago). I do `rm -rf ~/.qpidd; qpid clean -xfd'
before every compilation. And still cluster_read_credit test fails because
of following error:

Jan Sarenik
added a comment - 04/May/10 11:27 I found this issue already reported, reassigning to you
as requested in e-mail Message-ID: <4BDEDEBE.7030008@redhat.com>
You can find my unsuccessful try to cope with this issue at
http://github.com/jsarenik/qpid/commit/23713b2fc999a1fc4119ba06a7296ecd3f8260d4

The stale lock file is just a symptom. The real problem here is that the broker is crashing or exiting before the client connects. The stale lock file just indicates that we tried to stop a broker that was not running.

I have not been able to reproduce this so far. If you can reproduce it I'd like to see if the cluster0.log file has any useful information. I'll keep trying to reproduce it.

Alan Conway
added a comment - 06/May/10 17:44 The stale lock file is just a symptom. The real problem here is that the broker is crashing or exiting before the client connects. The stale lock file just indicates that we tried to stop a broker that was not running.
I have not been able to reproduce this so far. If you can reproduce it I'd like to see if the cluster0.log file has any useful information. I'll keep trying to reproduce it.

Jan Sarenik
added a comment - 10/May/10 15:01 - edited I am attaching a recent cluster0.log file which should contain
some relevant info because the cluster_read_credit failed
during that run.
This was done on qpid r942293.