commit | 386c08a6e60494e2216726bce6f12bd16f3a5731 | [log] [tgz] |
---|---|---|
author | David Åkerman <davidak@axis.com> | Thu Nov 23 15:38:20 2023 +0100 |
committer | David Åkerman <davidak@axis.com> | Fri Dec 08 10:30:10 2023 +0100 |
tree | c66fe7f8446d3105a82045a12b5986fe0cd3f14b | |
parent | a37a4156338e87549209a0a3913fc4d7233b7c02 [diff] |
Remove MonitorTimer With the RabbitMQ client library you can set automatic connection recovery with setAutomaticRecoveryEnabled and topology(channels etc) recovery with setTopologyRecoveryEnabled. Since client version 4.0.0 these flags have been enabled by default and we currently rely on 5.10.0. So no extra logic for recovery is needed anymore. Change-Id: Ie03e61cf0d76728caf819bdd44260d8c99e40a1b
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