[jboss-jira] [JBoss JIRA] (JBMESSAGING-1935) The MessagingClusterHealthMBean does not provide JMX Notifications

Doug Grove (JIRA) jira-events at lists.jboss.org
Mon Oct 8 12:07:03 EDT 2012


    [ https://issues.jboss.org/browse/JBMESSAGING-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724772#comment-12724772 ] 

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


More information about the jboss-jira mailing list