| Summary: | clustered qpidd can enter unresponsive state | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Frantisek Reznicek <freznice> | ||||
| Component: | qpid-cpp | Assignee: | messaging-bugs <messaging-bugs> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | MRG Quality Engineering <mrgqe-bugs> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 1.3 | CC: | aconway, esammons | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-01-25 07:51:44 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Frantisek Reznicek
2011-01-24 16:40:21 UTC
Created attachment 474987 [details] The issue reproducer and logs This is the script which reproduces the problem. Dependencies: openais configured and running. java-openjdk 1.6 installed main + devel qpid-java-* pkgs installed python-qpid installed How to run: ./bz667428 3 Then do: ps auxw | grep qpidd netstat -nlp | grep qpidd qpid-config qpid-cluster and you should see something like this: [root@dhcp-26-233 bz667428]# ps auxw | grep qpidd root 27457 0.4 4.2 207016 16128 pts/2 Sl 17:22 0:00 qpidd --auth=no --truncate yes --cluster-name=bz667428_at_dhcp-26-233.brq.redhat.com --log-enable=debug+ -p 10000 --data-dir=./dd10000 root 27673 0.0 0.1 61228 748 pts/2 R+ 17:24 0:00 grep qpidd [root@dhcp-26-233 bz667428]# netstat -nlp | grep qpidd tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 27457/qpidd [root@dhcp-26-233 bz667428]# qpid-config Failed: error: (111, 'Connection refused') [root@dhcp-26-233 bz667428]# qpid-cluster Failed: error - (111, 'Connection refused') In comment 1, you can see from the ps and output that the broker that is still running is listening on port 10000. There is no broker listening on the default port 5672. So it is normal to get "connection refused" when running qpid-config or qpid-cluster with no arguments, as they will try to connect to 5672. However these work fine for me: qpid-config -a localhost:10000 qpid-cluster -a localhost:10000 I repeated about 15 times and didn't see a non-responsiveness problem. Am I missing something? I apologize, this is indeed correct and I concur. The defect has no content and I'm going to close it as NOT-A-BUG. |