[
https://issues.jboss.org/browse/JBMESSAGING-1935?page=com.atlassian.jira....
]
Doug Grove commented on JBMESSAGING-1935:
-----------------------------------------
As per discussion with Brad, I added:
Notification msg = new
Notification("org.jboss.jms.server.MessagingClusterHealthMBean.restartJBMNode",
this, getNextNotificationSequenceNumber());
msg.setUserData(getServiceName());
sendNotification(msg);
for the starting and stopping of JBM.
The MessagingClusterHealthMBean does not provide JMX Notifications
------------------------------------------------------------------
Key: JBMESSAGING-1935
URL:
https://issues.jboss.org/browse/JBMESSAGING-1935
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.8.SP5
Reporter: Doug Grove
The MessagingClusterHealthMBean effectively shuts down JBoss Messaging on certain error
conditions. Loss of connectivity to the database is one such condition.
JMX notification of stop and start events should be provided so that management tools can
be made aware of these events and take appropriate action.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira