| Summary: | QPID Unexpected command start frame, iWARP configuration qpid-perftest hangs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | ppecka <ppecka> | ||||
| Component: | qpid-cpp | Assignee: | Andrew Stitcher <astitcher> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | ppecka <ppecka> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 1.3 | CC: | astitcher, gsim, iboverma | ||||
| Target Milestone: | 2.0 | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-13 03:37:02 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
ppecka
2011-01-31 13:51:46 UTC
this also appeared in qpid-perftest.log tested as described above except qpid-perftest option changed --npubs 2 2011-01-31 08:47:38 error RDMA: qp=0x2db8dc0: Deleting queue before all write buffers finished 2011-01-31 08:47:38 error Caught exception in state: 3 with event: 7: Success 2011-01-31 08:47:38 error Caught exception in state: 3 with event: 7: Success Additional info: after qpidd restart not reproducible again This may be the same underlying bug as bug 674011, it seems to have the same actual symptom (qpid-perftest hanging on exit) Created attachment 476550 [details] The issue reproducer More details on reproducibility: quite easy with attached script, triggers the issue within 30 minutes. How to run: on one machine [root@mrg4 bz484691]# ./run.sh 192.168.1.5 0 +Hit enter after 10 seconds (once the other is up) on second machine [root@mrg5 bz484691]# ./run.sh 192.168.1.4 0 +Hit enter after 10 seconds (once the other is up) I think this is very likely to have the same underlying cause as bug 681313 *** This bug has been marked as a duplicate of bug 681313 *** |