"clebert.suconic(a)jboss.com" wrote : | I thought the management address won't have a queue, if there are no consumers.. what would mean messages are dropped on that case. (Right?) | Just a clarification as the management address behviour is quite particular. There is no queue bound to the management address. When a message is sent to the management address, it bypasses regular code path and is handled by the management service. A server message reply is created containing the management operation result and *this reply* is routed to the management message's reply-to. The management message itself is never routed. | private void handleManagementMessage(final ServerMessage message) throws Exception | { | ... | | ServerMessage reply = managementService.handleMessage(message); | | SimpleString replyTo = (SimpleString)message.getProperty(ClientMessageImpl.REPLYTO_HEADER_NAME); | | if (replyTo != null) | { | reply.setDestination(replyTo); | | send(reply); | } | } | The issue is that the reply message is paged and the management client will never receive the operation result. In addition, when JMX is enabled, the MBean uses underneath the Core API to ensure management operations are replicated. This also means that, in that case, the server will always have a "management reply queue" so that the MBean can receive the operation result synchronously. If we want the management to work transparently, we must not page messages send to "management reply" address (as I proposed in http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159288&a...). If we do not want to treat the management case specifically, the user must configure the management reply address settings to disallow paging. But requiring explicit configuration for management reply address puts the burden on the user... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248469#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...