StompConnector::enforceConnected - Not Connected! when running tests

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run unit tests repeatedly in quick succession
2.
3.

What is the expected output? What do you see instead?

Expected output:

<pyactivemq.TextMessage object at 0x009EB6C0>
<pyactivemq.BytesMessage object at 0x009EB6C0>

Actual output:

<pyactivemq.TextMessage object at 0x009EB6C0>
<pyactivemq.BytesMessage object at 0x009EB6C0>
<pyactivemq.CMSException object at 0x009EB6C0> :
StompConnector::enforceConnected - Not Connected!

Sometimes the Python crashes.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by fullung@gmail.com on 21 Jan 2007 at 10:19

[GoogleCodeExporter]

Original comment by fullung@gmail.com on 21 Jan 2007 at 10:22

• Changed title: StompConnector::enforceConnected - Not Connected! when running unit tests

[GoogleCodeExporter]

Original comment by fullung@gmail.com on 21 Jan 2007 at 10:22

• Changed title: StompConnector::enforceConnected - Not Connected! when running tests

[GoogleCodeExporter]

An exception listener might have to be set to see this bug.

Original comment by fullung@gmail.com on 24 Jan 2007 at 8:08

[GoogleCodeExporter]

Haven't seen this bug in many, many runs of the test suite. Might have been an 
AMQCPP
issue. Closing for now.

Original comment by fullung@gmail.com on 1 Jun 2007 at 7:02

• Changed state: Fixed