Red Hat Bugzilla – Bug 485112
Cluster client hangs with --cluster-read-max=1
Last modified: 2015-11-15 19:06:41 EST
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible: easy on my laptop
Steps to Reproduce:
1. start a cluster broker with --cluster-read-max=1
2. while ./perftest --count 1 -s ; do true ; done
After about 50 iterations the client hangs.
On multi-core box a different problem occurs before the hang, see bug 479326.
Fxied in revision 743416
I am not able to reproduce the bug on version qpidd-0.4.741135-1.el5
even after >200 iterations. What particular version have you been
using when the problem occured?
Can not reproduce it even on MRG1.1 version:
I reproduced this easily on my laptop, a dual-core thinkpad T61 running fedora 10. I never was able to reproduce it on any of the multi-core RHEL5 boxes I use for testing.
Excuse me, but the version of qpidd please. I am trying
to reproduce it on laptop as well - dual-core, X61
on RHEL5.3 i386.
Do you use x86_64? Perhaps the bug is visible just there?
I was seeing it on trunk prior to revision 743416 when I checked in the fix.
[aconway@rolf ~]$ uname -a
Linux rolf 18.104.22.168-170.2.5.fc10.i686.PAE #1 SMP Wed Jan 21 01:54:56 EST 2009 i686 i686 i386 GNU/Linux
[aconway@rolf ~]$ cat /etc/redhat-release
Fedora release 10 (Cambridge)
I'm using the PAE kernel, perhaps that's the trick. If you can't reproduce this then I think its safe to close it.
While unable to reproduce the bug, I consider it
being solved as I did not experience any client