There are currently several implementations of the pluggable Broker Configuration Store:
- JSON
the default one which persists content to disk in a JSON file
- Memory
operates only in-memory and so does not retain changes across broker restarts and always relies on the current 'Initial Configuration' to provide the configuration to start the broker with.
- DERBY
stores configuration in embedded derby store
- BDB
stores configuration in Berkeley DB store
- JDBC
stores configuration in external RDBMS using JDBC
The command line argument -st (or --store-type) can be used to override the default json)configuration store type and allow choosing an alternative, such as Memory)
$ ./qpid-server -st memory
This can be useful when running tests, or always wishing to start the broker with the same 'Initial Configuration'
Another example of broker startup with configuration in DERBY network server
$ ./qpid-server -st JDBC \
-prop "systemConfig.connectionUrl=jdbc:derby://localhost:1527/path/to/store;create=true" \
-prop "systemConfig.username=test" -prop "systemConfig.password=password"
Apache Qpid, Messaging built on AMQP; Copyright © 2015 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners