"jmesnil" wrote : As part of the management task, I'm implementing receiving management notifications over JBM core connections. | | The idea is that a Core client can subscribe to notifications by asking the server to send a message to a given destination every time a notification is triggered on the server (e.g. a queue is full, a queue is added to the server) | | - the client creates a "management message", a Core message with well-known properties: | * the ObjectName it wants to observe | What if there is no jmx server running? All this stuff should work with no JMX server too. anonymous wrote : | * the destination where the notification messages must be sent (specified by the client, can be any kind of destination, more likely either a topic or a temp queue) | - it sends the message to the server | | - the server handles the message | * the PostOffice detects it is a management message and pass it to the management service | I think it might be better to introduce a new packet on the wireformat ManagementMessage and send via that, then there's no need for special routing in the post office - it can be intercepted at the session level anonymous wrote : | * the management service creates a NotificationListener for the given ObjectName | This seems JMX dependent to me anonymous wrote : | - Later on, when a notification is received by the listener (e.g. a queue is full) | Are notifications supposed to be persisent (i.e. do they survive after the session that created them has died?) If not, then the listener could just be the session, and you could use the standard session send functionality to send the notification View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177354#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...