tree d451eb83d70c68929251a9b437de1e095863d01a
parent 32dbdcea9b1096566b9db48ae5aa006f9ea06b93
author David Åkerman <davidak@axis.com> 1701093894 +0100
committer David Åkerman <davidak@axis.com> 1704368931 +0100

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