Hi Bruno, Thanks for reporting an issue with upgrade from "modelVersion: 2.0". The upgrade functionality unconditionally adds logback loggers into the broker configuration on model upgrade. It is a defect. The upgrader should actually check whether logback loggers are available before making any assumptions.
As for `qpid-broker-plugins-amqp-1-0-protocol-bdb-link-store` dependency, I am surprised to hear that you had to add it for a Memory virtual host. You should be able to embed the broker without this module. It only make sense to use BDB link store with a bdb message store or bdb-ha virtual host node. It cannot be used with Memory store. I suspect that something wrong with your configuration. If you could provide the details of the errors you are getting without bdb-link-store dependency, I might be able to help you to resolve the issue. Kind Regards, Alex On Fri, 7 Feb 2020 at 11:54, queimadus <[email protected]> wrote: > Thanks Alex, I managed to work it out with your example. > > For the record, my initial config was using `modelVersion: 2.0` and that > seems to be what was causing the unknown category BrokerLogger. > > One peculiar thing is that even though I ended up using the `Memory` for > the > `virtualHostInitialConfiguration` I still have to include the > `qpid-broker-plugins-amqp-1-0-protocol-bdb-link-store` dependency to have > it > all work. At first I thought it may be because of some transitive > dependency > but that didn't seem to be the case. > > Thanks again for the fast reply and standalone example, > Bruno > > > > > > -- > Sent from: > http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
