We are using your stompclient and CoilMQ, but we encountered this problem on windows, on linux sometimes we encounter it, but most of the time its OK, but on windows its the other way around.
we tried running coilmq and stompclient on same machine still we encountered same problem
We are using CoilMQ-0.4.3,CoilMQ-0.4.4,CoilMQ-0.5.0, stompclient-0.3.1, Python 2.6
Traceback (most recent call last): File "cxstompware.py", line 132, in <module> File "cxstompware.py", line 20, in init File "stompclient\duplex.pyc", line 202, in connect Exception: Expected CONNECTED frame, but none received. }}}
Anyways, we would like to thank you for this project, we are using it with our cafe management system.
we tried editing the following: "duplex.py" connect function starting line 199. instead of raising an exception, re-try connection.
this solves our issue/problem, I don't know if this is a good approach or solution, anyways just to give you an idea.
try: return self.connected_queue.get(timeout=self.queue_timeout) except Empty: #raise Exception("Expected CONNECTED frame, but none received.") self.connect(login, passcode, extra_headers) }}}