Bunny 2.9.1 is released to rubygems.org.
2.9.1 is a minor feature release that drops support for Ruby 2.2 and earlier.
GitHub issue: #539.
Contributed by Carl Hörberg.
Bunny now requires Ruby 2.2.
GitHub issue: #534.
Contributed by Andrew Babichev.
This release has minor breaking public API changes.
Bunny::Channel#close on a Closed Channel Now Raises a Sensible ExceptionBunny::Channel#close on an already closed channel will now raise a sensible exception.
If the channel was closed due to a channel-level protocol exception, that exception will
be mentioned.
GitHub issue: #528, see 9df7cb for details.
A JRuby 9K compatibility issue was corrected by Marian Posăceanu. Note that JRuby users are recommended to use March Hare, a JRuby-oriented client, instead of Bunny.
GitHub issue: #529
When automatic recovery is enabled, connection errors are now logged as warnings and not errors.
Contributed by Merten Falk.
GitHub issue: #531
It is now possible to specify a server-defined heartbeat value as a string ("server"), not just
a symbol. This makes it easier to load settings from YAML files.
Contributed by Tyrone Wilson.
GitHub issue: #524
Bunny now correctly handles scenarios where server is configured to disable heartbeats (which is a terrible idea, don’t do it!)
GitHub issue: #519.
Bunny::Channel#basic_get invoked with a non-existent queue now
throws a channel exception instead of a generic operation timeout.
GitHub issue: #518.
BUNNY_CERTIFICATE_DIR environment variable now can be used
to override local CA and client certificate/key pair directory.
The directory is expected to be the result directory generated
by the basic tls-gen profile.
TLSv1.0 is no longer used in tests because it’s being disabled by default by more and more installations as it has known vulnerabilities and is no longer considered to be acceptable by several compliance standards (e.g. PCI DSS).
channel.close handler will now acquire a lock . This avoids concurrency
hazards in some rare scenarios when a channel is closed due a protocol
exception by the server and concurrently opened by user code
at the same time.
Sometimes users attempt to open a channel on a connection that
isn’t connected yet because Bunny::Session#start was never invoked.
Bunny::Session#create_channel will now provide a more sensible exception message
in those cases.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>Bunny 2.7.0 is released to rubygems.org.
2.7.0 is a maintenance release that introduces a couple of minor
breaking changes.
In case your applications use Date/Time/DateTime serialisation with Bunny,
all of them must upgraded to 2.7.0 at the same time.
Minimum amq-protocol version is now [2.2.0]](https://github.com/ruby-amqp/amq-protocol/blob/master/ChangeLog.md#changes-between-210-and-220-may-11th-2017) which includes
a change in how timestamps are encoded.
Bunny::ContinuationQueue#poll Less Prone to Race ConditionsBunny::ContinuationQueue#poll was reworked with feedback from Joseph Wong.
GitHub issue: #462
Previous behehavior is not unreasonable but is not what many users and even RabbitMQ team members come to expect. Therefore it can be considered a bug.
Previously a reconnection counter was preserved between successful recoveries. This made the integration test that uses server-sent connection.close possible.
With this change, the counter is reset after successful reconnection but there’s an option to go back to the original behavior. We also do a hell of a lot more logging.
GitHub issue: #408
Contributed by Jared Smartt.
GitHub issue: #492.
Contributed by Alessandro Verlato.
GitHub issue: #465
Bunny::ConsumerWorkPool#shutdown(true) waited for consumer shutdown
even if the pool wasn’t active (there were no consumers on its
channel).
GitHub issue: #438.
EAGAIN, EWOULDBLOCKGitHub issue: #456
Bunny now can work with frozen host arrays.
GitHub issue: #446
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>Bunny 2.6.6 is released to rubygems.org.
2.6.6 is a maintenance release.
System call exceptions now will trigger connection recovery.
Contributed by Alessandro Verlato.
GitHub issue: #491.
Contributed by Jared Smartt.
GitHub issue: #492.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>Bunny 2.6.4 is released to rubygems.org.
2.6.4 is a maintenance release.
Bunny::ContinuationQueue#poll Less Prone to Race ConditionsBunny::ContinuationQueue#poll was reworked with feedback from Joseph Wong.
GitHub issue: #462
Previous behehavior is not unreasonable but is not what many users and even RabbitMQ team members come to expect. Therefore it can be considered a bug.
Previously a reconnection counter was preserved between successful recoveries. This made the integration test that uses server-sent connection.close possible.
With this change, the counter is reset after successful reconnection but there’s an option to go back to the original behavior. We also do a hell of a lot more logging.
GitHub issue: #408
Contributed by Alessandro Verlato.
GitHub issue: #465
EAGAIN, EWOULDBLOCKGitHub issue: #456
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>March Hare 3.0.0 is released to rubygems.org.
With this release March Hare switched to RabbitMQ Java client 4.x under the hood.
RabbitMQ Java client dependency has been updated to the final version of 4.1.0.
java.lang.StringGitHub issue: #109
Contributed by Andrew Cholakian.
RabbitMQ Java client dependency has been updated to the final version of 3.6.6.
Please consult the change log to learn about the changes.
Michael on behalf of the Ruby RabbitMQ Clients Team
]]>Bunny 2.6.2 is released to rubygems.org.
2.6.2 is a maintenance release.
EAGAIN, EWOULDBLOCKGitHub issue: #456
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>March Hare 2.20.0 is released to rubygems.org.
This is a maintenance release.
When an intermediary such as HAproxy with no backends online (or a problematic server node) doesn’t respond to a protocol header sent to it, RabbitMQ Java client will throw a generic operation timeout exception because the heartbeat mechanism is not yet enabled (it has not yet negotiated a timeout value for it!)
March Hare should handle this exception and retry, as if it was an I/O or skipped heartbeats exception.
Kudos to Andrew Cholakian and Jordan Sissel for digging this issue out.
GitHub issues: #107, logstash-plugins/logstash-input-rabbitmq#76
RabbitMQ Java client dependency has been updated to a milestone version of 3.6.6
to include a number of bug fixes early.
GitHub issue: #97.
Contributed by Michael Reis.
March Hare relies on RabbitMQ Java client for consumer dispatch but one (unused) thread pool was still instantiated.
GitHub issue: #96.
Contributed by Ivo Anjo.
GitHub issue: #98.
Contributed by Michael Reis.
Please consult the change log to learn about the changes.
Michael on behalf of the Ruby RabbitMQ Clients Team
]]>Bunny 2.6.1 is released to rubygems.org.
2.6.1 is a maintenance release.
Bunny::ConsumerWorkPool#shutdown(true) waited for consumer shutdown
even if the pool wasn’t active (there were no consumers on its
channel).
GitHub issue: #438.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>Bunny 2.6.0 is released to rubygems.org.
2.6.0 is a maintenance release.
Consumer work pool will now allow for a grace period before stopping pool threads so that delivery processing in progress can have a chance to finish.
GitHub issue: #437
Contributed by Stefan Sedich.
Bunny::Channel#wait_for_confirms Now Throws When Used on a Closed ChannelGitHub issue: #428
Contributed by Dimitar Dimitrov.
Bunny::Channel#wait_for_confirmsGitHub issue: #424
Contributed by Dimitar Dimitrov.
Bunny::ConsumerWorkPool#join and Bunny::ConsumerWorkPool#pause
no longer fails with a NoMethodError on nil when executed
on a work pool that doesn’t have active threads (consumers).
This change is largely cosmetic and won’t affect the majority of of projects in any way.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>Bunny 2.5.1 is released to rubygems.org.
2.5.1 is a maintenance release.
Bunny::ConsumerWorkPool#join and Bunny::ConsumerWorkPool#pause
no longer fails with a NoMethodError on nil when executed
on a work pool that doesn’t have active threads (consumers).
This change is largely cosmetic and won’t affect the majority of of projects in any way.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>March Hare 2.18.0 is released to rubygems.org.
This is a maintenance release.
RabbitMQ Java client dependency has been updated to 3.6.5.
It is now possible to provide a custom consumer tag instead of relying on RabbitMQ to generate one.
GH issue: #92
Contributed by Eger Andreas.
RabbitMQ Java client dependency has been updated to 3.6.2.
Please consult the change log to learn about the changes.
Michael on behalf of the Ruby RabbitMQ Clients Team
]]>Bunny 2.5.0 is released to rubygems.org.
2.5.0 is a maintenance release.
GitHub issue: #410
Contributed by Andrew Bruce.
Bunny::Channel#wait_for_confirms Awaits While There’re Outstanding Unconfirmed MessagesGitHub issue: #424
Contributed by Dimitar Dimitrov.
:no_declare OptionQueue recovery now respects the :no_declare option.
Bunny::Channel#wait_for_confirms Throws EarlyBunny::Channel#wait_for_confirms now throws an exception
early when invoked on a closed channel.
GitHub issue: #428.
Contributed by Dimitar Dimitrov.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>Bunny 2.4.0 is released to rubygems.org.
2.4.0 is a minor feature release.
Channels will now reset their unconfirmed delivery tag set after recovery.
GitHub issue: #406
Contributed by Bill Ruddock.
GitHub issue: #383.
Contributed by Jeremy Heiler.
Since transport is replaced by a recovering connection anyway, and this produces confusing errors up the stack.
GitHub issue: #359
Contributed by Donal McBreen.
:properties Merged with DefaultsClient-Provided Session :properties will now be merged with defaults
instead of replacing them. This makes it much more convenient to
override a single key.
RABBITMQ_URL no longer will be used if any other
connection options are provided. This makes it possible
to use RABBITMQ_URL for some connections and options
for others in a single OS process.
GitHub issue: #403
Contributed by Jimmy Petersen.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>Bunny 2.3.1 is released to rubygems.org.
2.3.1 is a maintenance release.
GitHub issue: #383.
Contributed by Jeremy Heiler.
Since transport is replaced by a recovering connection anyway, and this produces confusing errors up the stack.
GitHub issue: #359
Contributed by Donal McBreen.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>amqp gem 1.6.0 is released to rubygems.org.
This is a maintenance release that has no new features but updates
amq-protocol dependency and drops Ruby 1.9 support.
Minimum amq-protocol version is now 2.0.1.
Contributed by Neil Hooey.
GH issue: #222.
Ensures frameset is cleared after an unhandled exception. This avoids confusing exceptions such as
1
| |
Contributed by Michael Lutsiuk.
GH issue: #218
Full change log can be found on GitHub.
Michael on behalf of the Ruby RabbitMQ Clients Team
]]>amqp gem 1.5.3 is released to rubygems.org.
This is a maintenance release.
Contributed by Neil Hooey.
GH issue: #222.
Ensures frameset is cleared after an unhandled exception. This avoids confusing exceptions such as
1
| |
Contributed by Michael Lutsiuk.
GH issue: #218
Full change log can be found on GitHub.
Michael on behalf of the Ruby RabbitMQ Clients Team
]]>Bunny 2.3.0 is released to rubygems.org.
2.3.0 is a minor feature release.
Bunny::Session#create_channel now supports a 3rd argument that,
when set to true, makes consumer work pool threads to have
Thread#abort_on_exception set on them.
GH issue: #382
Contributed by Seamus Abshere.
Bunny now will explicitly close previosly used transport before starting connection recovery.
GitHub issue: #377.
Contributed by bkanhoopla.
Makes sure that TLS sockets are not double-initialized.
GH issue: #345.
Contributed by Carl Hörberg.
GH issue: #375
Contributed by Omer Katz.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>Hutch 0.21.0 is released to rubygems.org.
This is a bug fix release.
Contributed by Jesper Josefsson.
Rails application detection now won’t produce false positives
for applications that include config/environment.rb. Instead,
bin/rails and script/rails are used.
Contributed by @bisusubedi.
Contributed by Jesper Josefsson and Olle Jonsson.
Full change log can be found on GitHub.
Michael on behalf of the Hutch maintainers Team.
]]>March Hare 2.16.0 is released to rubygems.org.
This is a maintenance release.
RabbitMQ Java client dependency has been updated to 3.5.7.
Please consult the change log to learn about the changes.
Michael on behalf of the Ruby RabbitMQ Clients Team
]]>Bunny 2.2.2 is released to rubygems.org.
2.2.2 is a maintenance release.
Minimum required amq-protocol version is now 2.0.1 which includes
bug fixes.
Full change log can be found on GitHub.
Michael maintains Bunny and several other RabbitMQ client libraries.
]]>