connection.stop() hangs when using async listener on a non-empty queue

[GoogleCodeExporter]

You can reproduce this easily by modifying asynclistener.py to use queues
instead of topics.

Original issue reported on code.google.com by de...@nighttale.net on 8 Jul 2009 at 1:09

[GoogleCodeExporter]

Thanks for the report. I'm on vacation right now, so I'll take a look when I 
get back 
in about 2 weeks. If you have time, it would be useful to know if we have the 
same 
problem using C++ code.

Original comment by fullung@gmail.com on 11 Jul 2009 at 4:39

[GoogleCodeExporter]

I'm hitting this exact issue right now (very annoying).  :)

Here's what I'm using:
 - openSUSE 11.1 x86_64
 - Python 2.6.4
 - pyactivemq-0.1.0.tar.gz
 - activemq-cpp-2.2.6-src.tar.gz

Any idea if this is still being looked at?

...by the way, pyactivemq is awesome!

Original comment by ben.camp...@gmail.com on 4 Feb 2010 at 2:22

[GoogleCodeExporter]

I haven't had time to come back to this issue, but I'll look into it again in 
the next 
few days. Watch this space.

Original comment by fullung@gmail.com on 4 Feb 2010 at 5:01

[GoogleCodeExporter]

...I forgot to mention also that my python code is connecting to ActiveMQ 5.3.0.

Original comment by ben.camp...@gmail.com on 4 Feb 2010 at 10:30

[GoogleCodeExporter]

Any word on this yet?  

Would it help if I re-built pyactivemq using activemq-cpp 3.1.x instead of 
2.2.6?  

Is pyactivemq0.1.0 source compatible with activemq-cpp 3.1.x or would I need to 
use
the version of pyactivemq from the svn trunk?

Thanks

Original comment by ben.camp...@gmail.com on 18 Feb 2010 at 7:05

[GoogleCodeExporter]

I had a thought.  I read through issue 26 and 25 and through this link
(https://issues.apache.org/activemq/browse/AMQCPP-199).  Do you know if the 
issue
remains when using Python 3.x (instead of Python 2.6)?

Original comment by ben.camp...@gmail.com on 18 Feb 2010 at 7:37

[GoogleCodeExporter]

Hello

Still looking at it, but I haven't had much time though. The API of AMQ-CPP has 
changed  a lot between 2.2.6 and 3.1.x, so a simple rebuild of 0.1.0 isn't 
going to 
work. Right now I would suggest keeping the AMQ-CPP version unchanged and 
trying to 
understand the bug better before we try upgrading AMQ-CPP.

I'll look into this more this weekend.

Cheers

Albert

Original comment by fullung@gmail.com on 19 Feb 2010 at 6:08

[GoogleCodeExporter]

One thing I have noticed is that this issue does not happen on Windows XP 
32bit.  I'm
using the downloaded binaries of pyactivemq.  On Linux (spec's above) I'm 
building
activemq-cpp and pyactivemq both from source.

Ben

Original comment by ben.camp...@gmail.com on 12 Mar 2010 at 4:28

[GoogleCodeExporter]

Is this project still being worked on?  I believe I'm experiencing this same 
issue. If I break the connection to the activeMQ (pull the ethernet cable or 
kill the connection using tcpview) python hangs and appears to be deadlocked.  
If I run python in the debugger I did get it to throw an exception.  See below. 
 I'm attempting to harden a script so that it can recover from the connection 
going away by either shutting down gracefully or re-connecting, but there 
appears to be no hope...

I'm running windows 7. Python 26 (32 bit).  

The thread 'Win32 Thread' (0x27e0) has exited with code 0 (0x0).
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
decaf::io::IOException at memory location 0x0027d0d8..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
decaf::lang::Exception at memory location 0x0027d024..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
decaf::io::IOException at memory location 0x0027cf58..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
decaf::io::IOException at memory location 0x0027d2a0..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
decaf::io::IOException at memory location 0x0027d5dc..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
activemq::exceptions::ActiveMQException at memory location 0x0027d960..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
cms::CMSException at memory location 0x0027dd5c..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
cms::CMSException at memory location 0x0027e088..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
cms::CMSException at memory location 0x0027e378..
First-chance exception at 0x76b7b727 in python.exe: Microsoft C++ exception: 
cms::CMSException at memory location 0x0027e564..
First-chance exception at 0xcccccccc in python.exe: 0xC0000005: Access 
violation.
Unhandled exception at 0xcccccccc in python.exe: 0xC0000005: Access violation 
reading location 0xcccccccc.
The program '[10296] python.exe: Native' has exited with code -1073741819 
(0xc0000005).

Original comment by st...@kelker.net on 9 Mar 2011 at 11:18