Page History

...

* GS: I'm very much in favour of aligning the two brokers. We would however need to come up with a mechanism for allowing the c++ broker to retain backwards compatibility with a schema as currently defined. E.g. support for multiple schemas?

• The java broker exposes an interface for conducting live User Management, eg add/delete/view users, set password, set management access rights (read only, read/write, or admin which is read/write plus access to the more sensitive management mbeans such as UserManagement itself). It would be good to expose this type of management via QMF as well.

• The Java broker exposes an interface for viewing and adjusting its logging levels while running. This too would be useful to expose via QMF.

General comments on QMF

• have a generic way to be able to create new entities,
• have a way to modify the mutable properties of existing entities.
• when sending schema, where a particular value is of a restricted domain (e.g. has min and/or max values; or takes a value from a restricted enumerated set) then that restricted domain is communicated.
• add ability to "reset" statistic counters... This would actually make low watermark counts useful.
• add ability to query for objects based on criteria (e.g. get me all exchanges whose vhostRef is X)

...

• ability to create virtual hosts
• shutdown/restart broker?
• reload (security) configuration.

Agent

The Java Broker does not currently support the Agent class

...

• create queue
• create exchange
• create binding
• delete queue
• delete exchange
• delete this vhost

Queue

Properties

...

• age of oldest message on the queue (and high watermark),
• high watermark for message size
• high watermark for queue depth (bytes)
• high watermark for message count
• messages/bytes expired due to TTL

...

• mechanisms to move / copy messages to another queue .(with filters to allow specifying arbitrary messages, not first X msg)
• rename this queue
• delete this queue
• mechanism to inspect messages on the queue

...