Unable to log in to RabbitMQ 2.4.1

Bug #766783 reported by Philip K. Warren
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
txAMQP
Fix Released
Undecided
Unassigned

Bug Description

This is a continuation of problems which are still persisting when connecting to RabbitMQ 2.4 after the fix for Bug 741147. The new error is due to failing to parse a boolean value in the table (there are four boolean values - publisher_confirms, exchange_exchange_bindings, basic.nack, and consumer_cancel_notify).

To resolve the issue, I propose the following fix to codec.py:

=== modified file 'src/txamqp/codec.py'
--- src/txamqp/codec.py 2011-04-04 14:41:10 +0000
+++ src/txamqp/codec.py 2011-04-07 21:26:20 +0000
@@ -189,6 +189,8 @@
         value = self.decode_long()
       elif type == "F":
         value = self.decode_table()
+ elif type == "t":
+ value = (self.decode_octet() != 0)
       else:
         raise ValueError(repr(type))
       result[key] = value

Revision history for this message
Philip K. Warren (pkwarren) wrote :
Revision history for this message
Thomas Herve (therve) wrote :

It would be nice to add a decode_bool procedure instead. It would also be nice to have a test case.

Revision history for this message
Maarten Damen (m-damen) wrote :

I tried this patch using both the 0.9 and 0.9.1 spec but it didn't work for me. I get the following traceback:
[Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.]

0.8 spec still works fine. Any thoughts?

Changed in txamqp:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Patches

Remote bug watches

Bug watches keep track of this bug in other bug trackers.