What's Changed
This is a patch release to improve performance and stability for postgres and rabbitmq.
Improve Postgres stability - #420
Shortly after deploying 3.0.0, a bug was found where postgres connections were getting overloaded when more than 100 workers were deployed. To fix this we modified the pgbouncer configuration slightly so that the max number of user connections and max number of db connections were the same, plus a few extra connections for the db to allow for superuser processes. Currently this number is set at 200, so that is the max workers that should be deployed currently.
Also in this release is a slight refactor to close database connections from the java client using a try-with-resources pattern to ensure connections are not stranded.
Recover RabbitMQ dropped connections
This was a minor but important change - sometimes an exception was thrown when trying to recover a connection because the channel was already closed. In the catch block that does the connection recovery, we removed the channel.close() and only closed the connection before reopening both.