connection.authenticate() ending script. RabbitMQ spec

[Devin Bhushan]

Hi,

I am using txAMQP with RabbitMQ. I have had success with this in the past but something about this application is causing it to act weirdly. I am able to use ClientCreator() and then add a callback to that for gotConnection(). gotConnection(conn) calls the line "yield conn.authenticate("guest", "guest")" and this is where it dies. I have the rest of the function after this line but it never gets that far. I traced this down to protocol.py in txamqp files by logging progress from that file. It looks like it gets through authenticate until "yield self.start(response, mechanism, locale)" and then it doesn't get past the line "channel0.connection_open(self.vhost)" from that function...this seems to be the point where it dies. Any idea what I might be doing wrong if I've used this before and it's working in other applications. I'm using all the same setup, not sure why it's just dying in authentication.

Thanks!

[Devin Bhushan (bhushan1-l)]

So we did some more digging and I think it comes down to the invoke function in protocol.py when it executes the connection_open function. It calls "yield responses.get()" from Queue.py and that deferred never fires. I went into the get code in Queue.py and confirmed that it reaches the end of the function and returns a deferred but the yield never responds in protocol.py so I think the queue is empty since the deferred containing the next element is empty. Now I'm not entirely sure why this is happening...but I was hoping you guys could point me in the right direction?