[rabbitmq-discuss] ANN Bunny 0.9.0.pre6 is released

Wed Jan 16 20:17:14 GMT 2013

Hi guys,

Bunny 0.9 is fantastic so I really don't want to be a pain with this: 
please do let me know if it is not the right place or too early to discuss 
these potential issues.

I just tried pre7 - it works better on basic_get, thank you! Yet:

- the automatic_recovery_with_client_named_queues.rb example does not work 
anymore (if you stop the server, then start it again, messages are not 
received anymore - it used to work on pre6).
- in the basic_get case, when the server is down, q.pop still hangs 
indefinitely. Is it expected and it should be handled by the client?

Thanks
PJ

On Wednesday, January 16, 2013 11:05:36 AM UTC, PJ wrote:
>
> Hi Michael,
>
> First of all: this is a fantastic addition. Thank you so much.
>
> Just one thing though: is network failure recovery supposed to work with 
> q.pop as well? The reason I am asking is I can't get it to work. I modified 
> slightly one of your examples:
>
> require 'bunny'
>
> broker = Bunny.new
> broker.start
> channel = broker.create_channel
> exchange = channel.default_exchange
>
> loop do
>   sleep 2
>   puts "Tick"
>   
>   q = channel.queue("foo")
>   delivery_info, properties, payload = q.pop
>   
> end
>
>
> If you run the script and stop the RabbitMQ server while the script is 
> executing, the script hangs on q.pop.
> If you then restart the server, the script will pass the q.pop once, then 
> hang again and nothing happens anymore.
>
> Is this expected?
>
> Thanks a lot
> PJ
>
>
> On Monday, January 14, 2013 5:48:15 PM UTC, Michael Klishin wrote:
>>
>> TL;DR
>>
>> -----------------------------------------------------------------------------------------------------------------------
>>
>> Bunny 0.9.0.pre6 is released to rubygems.org [1].
>>
>> This release includes one major feature and a few bug fixes. It is 100% 
>> backwards
>> compatible.
>>
>> The major feature is automatic network failure recovery. This includes 
>> recovery of
>> exchanges, queues, bindings and consumers that were declared/added on the
>> recovered Bunny connection.
>>
>> In addition, documentation guides on error handling and recovery is now 
>> up online:
>> http://rubybunny.info/articles/error_handling.html<http://rubybunny.info/articles/exchanges.html>
>>
>> Change log
>>
>> -----------------------------------------------------------------------------------------------------------------------
>>
>> Change log is available on GitHub:
>>
>> https://github.com/ruby-amqp/bunny
>> /blob/master/ChangeLog.md#changes-between-bunny-090pre5-and-090pre<https://github.com/ruby-amqp/bunny/blob/master/ChangeLog.md#changes-between-bunny-090pre4-and-090pre5>
>> 6
>>
>>
>> Plans for 0.9.0 Final
>>
>> -----------------------------------------------------------------------------------------------------------------------
>>
>> There is still a few things we need to do before Bunny 0.9 can be 
>> declared complete:
>>
>>  * Make network failure recovery configurable
>>  * Bring back TLS support
>>  * Add logging
>>  * API reference documentation
>>
>> Changes are, the next release will be RC1.
>>
>>
>> 1. https://rubygems.org/gems/bunny/versions/0.9.0.pre<https://rubygems.org/gems/bunny/versions/0.9.0.pre5>
>> 6
>> -- 
>> MK
>>
>> http://github.com/michaelklishin
>> http://twitter.com/michaelklishin
>>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130116/1bd1791a/attachment.htm>