Well I think these two issues aren't as related as I thought. The headers not in content happens when you:
* have a publisher, send to a queue. * disconnect the publisher, make sure the queue is still alive aka, no auto_delete * send to the response queue, which no longer exists, and this happens. I do think the command_invalid thing is related to the aforementioned problem. But I will have to investigate deeper. Tell me what you think, On Sat, Sep 5, 2009 at 3:26 AM, Dan Di Spaltro<[email protected]> wrote: > So I keep running into this problem in our production system since the > addition of the basic return, that I either get a truckload of these: > * 'headers' not in msg.content > - or - > * txamqp.client.Closed: Method(name=close, id=60) (503, > 'COMMAND_INVALID - expected content header for class 60, got non > content header frame instead', 0, 0) content = None > > Which leads me to believe that frames are getting sent out of order. > Now I haven't been able to confirm or deny whether I am doing > something weird or if it is the fact that basic return is sharing the > same channel as the normal messages going out and there seems to be > nothing preventing them from interleaving and thus getting that > message. So I made a new branch with a quick fix and that problem > doesn't seem to be happening much anymore. Obviously, this change > has side effects because now no longer are you creating a single > channel so any code that creates multiple channels will probably > notice that second open will fail. > > http://bazaar.launchpad.net/~dan-dispaltro/txamqp/fixed-queue-order/revision/39 > > Tell me what you think or if there is a better proper solution. > > Thanks, > > -- > Dan Di Spaltro > -- Dan Di Spaltro _______________________________________________ Mailing list: https://launchpad.net/~txamqp-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~txamqp-dev More help : https://help.launchpad.net/ListHelp
