[rabbitmq-discuss] Channel crashes after basic.cancel_ok.
0x6e6562 at gmail.com
Sat May 10 00:07:29 BST 2008
On 8 May 2008, at 21:11, Ben Hood wrote:
> On 8 May 2008, at 15:04, Edwin Fine wrote:
>> Thanks for looking into this. In the "real" code, all the setup is
>> actually done within a single Erlang process, and the only thing
>> the consumers do is handle the basic.deliver, as well as any
>> basic.consume_ok or basic.cancel_ok messages that may arise. In
>> the test code, I rearranged some things specifically to be done
>> concurrently, which I now see was a mistake. However, this is a bug
>> in the test code, not in the production code. I will change the
>> test code so that there is no concurrent work being done on a
>> channel other than responding with basic.ack to basic.deliver
> I've begun a discussion on this topic and it looks like we will add
> the intelligence to the amqp_channel module to be able to serialize
> concurrent RPC requests to the channel. I understand that you have a
> workaround anyway, but on reflection, it seems like a good idea to
> put this capability into the client. will let you know when it is
This feature is now implemented in the trunk of the repo. There is
also a test case to test the serialization of concurrent RPC requests.
I will now look into the next 2 issues you raised.
BTW, I am also in the process of moving the mtn repo to hg, so this
might happen very soon as well.
More information about the rabbitmq-discuss