delta/rabbitmq-server.git, branch bug22938hg.rabbitmq.com: Obsolete (use rabbitmq-server-git)
Ensure that after asking the writer to exit, we unlink from it. We're usually in the channel when we ask it to exit anyway, which has trap_exits on, so the selective receive is appropriate. In the erlang client we're in amqp_network_connection, which also has trap_exits on, so it's fine there too. However, the point is to ensure the *writer* isn't destroyed early by the channel exiting too quickly, not the other way around, and without turning on trap_exits in the writer.2010-07-05T15:35:15+00:00Matthew Sackmanmatthew@rabbitmq.com2010-07-05T15:35:15+00:00cef5c164fe09d12befde719fd086736e710e55cd
minor simplification of test2010-07-02T13:46:51+00:00Matthias Radestockmatthias@rabbitmq.com2010-07-02T13:46:51+00:008650193ea850ec9c39b0ae5fc741cecdcc15b31d
This isn't quite the same since rabbit_basic:build_content only
creates decoded properties, but for the test in question that doesn't
matter.
This isn't quite the same since rabbit_basic:build_content only
creates decoded properties, but for the test in question that doesn't
matter.
minor refactor2010-07-02T12:34:24+00:00Matthias Radestockmatthias@rabbitmq.com2010-07-02T12:34:24+00:0045e37ef127ec961f1aa194f7369a3cdc1084f2ea
Merged bug22925 into default2010-07-02T11:26:05+00:00Emile Joubertemile@rabbitmq.com2010-07-02T11:26:05+00:001c884db9e4ec744745af7fc7f54fb470392fded6