commit | 7926e59b8aa229ebf5db88ee21372f07d2713eb6 | [log] [tgz] |
---|---|---|
author | David Åkerman <davidak@axis.com> | Mon Nov 27 15:04:54 2023 +0100 |
committer | David Åkerman <davidak@axis.com> | Thu Jan 04 12:48:51 2024 +0100 |
tree | d451eb83d70c68929251a9b437de1e095863d01a | |
parent | 32dbdcea9b1096566b9db48ae5aa006f9ea06b93 [diff] |
Split session into one session for publishing and one for subscribing When using RabbitMQ it is recommended that: * A channel is only used by one thread. * A subscriber should use its own channel * One connection is used for publishing and one is used for subscribing Currently a connection is mapped to one channel. But by splitting Session into one session for publishing and one for subscribing we can can create different number of channels per connection for the different cases. Change-Id: I283ac18409dcb75eea37a930a8b7632034a1dbca
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