Page History

...

For general questions, please subscribe to the qpid-users@incubatorusers@qpid.apache.org mailing list (archive).

For development questions, please subscribe to the qpid-dev@incubatordev@qpid.apache.org mailing list (archive).

More details on these lists are available on our mailing lists page.

How can I change a user's password while the broker is up ?

You can do this via the management console if you're using the base64password file (rather than plain text) Qpid JMX Management Console. To do this simply log in to the management console as an admin user (you need to have created an admin account in the jmxremote.access file first) and then select the 'Manage UsersUserManagement' pane. There is a 'Change Password' tab which you can then usembean. Select the user in the table and click the Set Password button. Alternatively, update the base64password password file and use the management console to reload the file , in with the button at the bottom of the 'Manage UsersUserManagement' paneview. In both cases, this will take effect when the user next logs in i.e. will not cause them to be disconnected if they are already connected.

For more information on the Management Console please see our Qpid JMX Management Console User Guide.If you're using plain text passwords, then simply update your file and the content is read on every connection.more information on the Management Console please see our Qpid JMX Management Console User Guide

How do I know if there is a consumer for a message I am going to send?

...

The Java broker does not currently implement producer flow control. Publishes are currently asynchronous, so there is no ability to rate limit this automatically. While this is something which will be addressed in the future, it is currently up to applications to ensure that they do not publish faster than the messages are being consumed for signifcant periods of time.

Why can't I connect the management console to the broker?

The CRAM-MD5 JMX authentication is currently broken in the broker, disable it by editing qpidmc.sh or qpidmc.bat and removing '-Dsecurity=CRAM-MD5' and setting security-disabled to false in the broker configuration filebe addressed in the future, it is currently up to applications to ensure that they do not publish faster than the messages are being consumed for signifcant periods of time.

The broker keeps throwing an OutOfMemory exception?

...

These threads are part of the thread pool used by Mina to process the socket. In the future we may provide tuning guidelines but at this point we have seen no performance implications from the current configuration. As the threads are part of a pool they should remain inactive until required.

"unable to certify the provided SSL certificate using the current SSL trust store" when connecting the Management Console to the broker.

You have not configured the console's SSL trust store properly, see Management Console Security for more details.