tag:github.com,2008:https://github.com/aspone/rabbitmq-java-client/releases 2014-06-17T10:09:02Z tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_4 2014-06-17T10:09:02Z tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_3 2014-06-12T15:20:16Z tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_2 2014-05-22T01:44:16Z michaelklishin tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_1 2014-04-28T14:17:45Z rade tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_0 2014-03-25T15:15:39Z tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_4 2014-02-17T11:50:36Z tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_3 2013-12-23T23:23:04Z <p>fix timing and failure handling in testRestartingExpiry</p> <p>...which was failing nearly all the time on my laptop <br />- publishing is async, so we don't know when the message has it the <br /> server and hence the expiry timer starts. We could introduce a <br /> confirm, but it's easier to just use the server restart as an <br /> indicator. <br />- when the assertion fails we still need to delete the <br /> queue. otherwise other tests using the same queue name, but <br /> different params, will fail.</p> rade tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_2 2013-11-07T15:22:00Z tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_1 2013-10-25T17:19:47Z tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_0 2013-10-17T13:23:09Z