Bug 485112 - Cluster client hangs with --cluster-read-max=1
Summary: Cluster client hangs with --cluster-read-max=1
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.1
Hardware: All
OS: Linux
high
high
Target Milestone: 1.1.1
: ---
Assignee: Alan Conway
QA Contact: Frantisek Reznicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-11 16:54 UTC by Alan Conway
Modified: 2015-11-16 00:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-16 13:07:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alan Conway 2009-02-11 16:54:20 UTC 
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.
  
Additional info:

On multi-core box a  different problem occurs before the hang, see  bug 479326.
Comment 1 Alan Conway 2009-02-11 17:37:53 UTC 
Fxied in revision 743416
Comment 2 Jan Sarenik 2009-02-12 10:22:17 UTC 
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?
Comment 3 Jan Sarenik 2009-02-12 11:03:30 UTC 
Can not reproduce it even on MRG1.1 version:
qpidc-0.4.732838-1.el5
qpidd-0.4.732838-1.el5
qpidd-cluster-0.4.732838-1.el5
qpidc-perftest-0.4.732838-1.el5
Comment 4 Alan Conway 2009-02-12 15:21:34 UTC 
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.
Comment 5 Jan Sarenik 2009-02-13 14:53:13 UTC 
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?
Comment 6 Alan Conway 2009-02-13 15:27:58 UTC 
I was seeing it on trunk prior to revision 743416 when I checked in the fix. 

[aconway@rolf ~]$ uname -a
Linux rolf 2.6.27.12-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.
Comment 7 Jan Sarenik 2009-02-16 13:07:03 UTC 
While unable to reproduce the bug, I consider it
being solved as I did not experience any client
hang.
Note You need to log in before you can comment on or make changes to this bug.