| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
rabbit must not be the monorepo root application, as other applications depend on it
|
|
|
|
| |
118b448631a699736f1380d7990989c7e61f94ff, back out my changes
|
|
|
|
|
|
|
|
|
| |
They were bumped to x10 the values in 118b448631a699736f1380d7990989c7e61f94ff
by mistake.
Kudos to Chris Friesen for reporting this.
Closes #1659.
|
|
|
|
|
|
|
|
|
|
|
| |
Covers the following variables:
* RABBITMQ_SCHEDULER_BIND_TYPE & SCHEDULER_BIND_TYPE
* RABBITMQ_DISTRIBUTION_BUFFER_SIZE & DISTRIBUTION_BUFFER_SIZE
* RABBITMQ_MAX_NUMBER_OF_PROCESSES & MAX_NUMBER_OF_PROCESSES
* RABBITMQ_MAX_NUMBER_OF_ATOMS & MAX_NUMBER_OF_ATOMS
(cherry picked from commit 118b448631a699736f1380d7990989c7e61f94ff)
|
|
|
|
| |
RABBITMQ_, adjust Unix and Windows files accordingly
|
|
|
|
|
|
|
| |
This was the only property in SERVER_ERL_ARGS that was not configurable.
Even though it's unlikely that this will need to be increased above the
existing 5 million default, we are consistent in allowing all properties
in SERVER_ERL_ARGS to be cofigured.
|
|
|
|
|
|
|
| |
This property is essential for nodes that need to handle many
connections / channels / queues.
Related to #1513
|
|
Prior to this change, setting RABBITMQ_DISTRIBUTION_BUFFER_SIZE
and/or RABBITMQ_SCHEDULER_BIND_TYPE would not be added to
SERVER_ERL_ARGS because the latter variable was built prior to
reading rabbitmq-env.conf
Fixes #1338
[#150452491]
Signed-off-by: Luke Bakken <lbakken@pivotal.io>
|