commit | 608f6e731e22babb0f9cbd7424c9b1d12bfb2e27 | [log] [tgz] |
---|---|---|
author | David Åkerman <davidak@axis.com> | Fri Jan 19 14:25:51 2024 +0100 |
committer | David Åkerman <davidak@axis.com> | Thu Jan 25 10:32:32 2024 +0100 |
tree | 681b3358aeba45aa6fce57208095b12b4bc1e469 | |
parent | dbaf0adcbcdcbd1eaf684250d6bf2a95ddba5130 [diff] |
Catch exceptions that consumers throw As exceptions that are thrown by consumers are considered to originate from the application, they cause a closure of the channel that the consumers use. Neither channel nor consumer are recreated. As consumers may still be able to process other events, we should not close the channels due to exceptions. Instead warn, log the exception and continue. Change-Id: If4e85412af324568ef6ab5162e692529473298da
Publish gerrit stream events to a RabbitMQ queue. This plugin works with any version of Gerrit starting from v2.8. This plugin also implements most of the events-broker API, so RabbitMQ can be used as a message-broker in a multi-master setup. The one part that is missing is the implementation of the replayAllEvents method. However, this method is not needed by the multi-site plugin.
linux
java-1.8
Bazel
[amqp] uri = amqp://localhost [exchange] name = exchange-for-gerrit-queue [message] routingKey = com.foobar.www.gerrit [gerrit] name = foobar-gerrit hostname = www.foobar.com
3.14 (Freezed)
stable-2.10
master
is permanently latest but would not be updated by author anymore.3.1
3.0
2.0
1.4
1.3
1.2
1.1
monitor.failureCount
1.0
The Apache Software License, Version 2.0
Copyright (c) 2013 rinrinne a.k.a. rin_ne