Closed GoogleCodeExporter closed 8 years ago
Thanks for the report, investigating.
Original comment by pcnoordh...@gmail.com
on 22 Apr 2011 at 6:52
Can you provide the script you're using to trigger the segfault?
Original comment by pcnoordh...@gmail.com
on 22 Apr 2011 at 7:17
Sure thing. Apologies that it's not a more simple script. I'm doing an eval
of Redis as a potential queueing solution, so I wrote some scripts that I'm
using to test RabbitMQ, ActiveMQ, HornetQ, and Redis.
BTW, Redis is the front-runner. If we can get this issue sorted out then we're
moving forward with it. Thanks for looking into this issue so quickly!
To run:
pip install redis
pip install stomp.py (just so imports don't blow up)
export BROKER_TYPE=redis
performance_test.py 4 4 100000
performance_test.py accepts
- # of producers
- # of consumers
- # of messages to queue
4 4 100000 were the inputs I used when I got the segfault
Original comment by jamespco...@gmail.com
on 22 Apr 2011 at 8:01
Attachments:
Thanks, I was able to reproduce the fault within 5 runs. Now on to solving it
;-).
Original comment by pcnoordh...@gmail.com
on 22 Apr 2011 at 8:12
Fantastic. I figure with something like this, getting a consistent repro is
one of the harder parts. Thanks again for your help.
Original comment by jamespco...@gmail.com
on 22 Apr 2011 at 8:14
Have you had any luck tracking the cause of this one down? Thanks very much.
Original comment by jamespco...@gmail.com
on 13 May 2011 at 8:56
Hello James, should be ok now in the 2.2 branch on github. Please can you
verify? Thank you.
Original comment by anti...@gmail.com
on 13 May 2011 at 9:05
p.s. this is fixed into 2.2.7 as well
Original comment by anti...@gmail.com
on 13 May 2011 at 9:08
fantastic! thank you very much!
Original comment by jamespco...@gmail.com
on 13 May 2011 at 9:56
Original issue reported on code.google.com by
jamespco...@gmail.com
on 22 Apr 2011 at 5:24