[
https://issues.apache.org/jira/browse/QPID-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864856#action_12864856
]
Alan Conway commented on QPID-2532:
-----------------------------------
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.
> stale lock file
> ---------------
>
> Key: QPID-2532
> URL: https://issues.apache.org/jira/browse/QPID-2532
> Project: Qpid
> Issue Type: Test
> Components: C++ Broker
> Affects Versions: 0.7
> Environment: Fedora Rawhide
> Reporter: Jan Sarenik
> Assignee: Alan Conway
> Fix For: 0.7
>
>
> 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:
> (relevant part of `make check' output follows)
> 2010-04-22 11:54:31 warning Connection closed
> 2010-04-22 11:54:31 warning Connect failed: Connection refused
> 2010-04-22 11:54:31 warning Connection closed
> Failed: Cannot establish a connection
> 2010-04-22 11:54:31 critical Unexpected error: Removing stale lock file
> /home/jsarenik/.qpidd/qpidd.41519.pid
> Errors stopping brokers on ports: 41519
> FAIL: cluster_read_credit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
