Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9132

mbeans jboss.jgroups:type=channel,cluster=... do not get re-registered

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.2
    • Clustering
    • None
    • Hide

      start 2 nodes clustered together.
      Pause one of them until it's kicked (Ctrl-Z in Linux), then resume it ("fg" in Linux).
      See if the org.jgroups:* MBeans for the shunned channels have disappeared.

      Show
      start 2 nodes clustered together. Pause one of them until it's kicked (Ctrl-Z in Linux), then resume it ("fg" in Linux). See if the org.jgroups:* MBeans for the shunned channels have disappeared.
    • Release Notes
    • Hide
      In earlier versions of JBoss Enterprise Application Platform, if a non-responsive cluster node was kicked from the cluster, shunned, and then reconnected the JMX MBeans for the JGroups channels were no longer available. This version of EAP ensures the JMX MBeans for the JGroups channels are added back on reconnection. This resolves the issue as the JMX MBeans for the JGroups channels are available even after the node has been shunned from the cluster and reconnects.
      Show
      In earlier versions of JBoss Enterprise Application Platform, if a non-responsive cluster node was kicked from the cluster, shunned, and then reconnected the JMX MBeans for the JGroups channels were no longer available. This version of EAP ensures the JMX MBeans for the JGroups channels are added back on reconnection. This resolves the issue as the JMX MBeans for the JGroups channels are available even after the node has been shunned from the cluster and reconnects.
    • Documented as Resolved Issue
    • NEW

    Description

      An instable network communication can cause JChannel to be closed. When this happens, mbeans jboss.jgroups:type=channel,cluster=... get unregistered as a result of receiving a jgroups EXIT event. The unregistration is done in org.jboss.ha.framework.server.JChannelFactory through JChannelFactory$ChannelCloseListener.
      When the network comes back the channel reconnects. But the mbeans don't as the listener only pays attention to close events, and not reconnected events.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue JBPAPP-9503 EAP 5_1_2 ChannelFactoryManagedObjectsTestCase failures

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-support-dereed Dennis Reed
              rhn-support-sappleton Shaun Appleton
              Scott Thomas Scott Thomas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: