Support of several embedded HornetQ brokers by default #1063
Description
Our test suite has shown the following when an application context is alive and another one attempts to enable the HornetQ auto config
- If the existing application context has an hornetQ broker already, the attempt to start one in the other context fails in the background
- The connection factory of the other context is registered properly and connects to the existing one
We should support several embedded hornetQ brokers out of the box. Not that this is representative of a typical use case (it probably isn't) but since we are embedding by default, we should do it in such a way that it "just works".
This SO thread provides an answer as what should be done here, that is assigning a serverId to each server and make sure that the connection factory reuse that id.