Export to GitHub

pyactivemq - issue #3

StompConnector::enforceConnected - Not Connected! when running tests

Posted on Jan 21, 2007 by Massive Kangaroo

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.

Comment #1

Posted on Jan 21, 2007 by Massive Kangaroo

(No comment was entered for this change.)

Comment #2

Posted on Jan 21, 2007 by Massive Kangaroo

(No comment was entered for this change.)

Comment #3

Posted on Jan 24, 2007 by Massive Kangaroo

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

Comment #4

Posted on Jun 1, 2007 by Massive Kangaroo

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

Status: Fixed

Labels:
Type-Defect Priority-High