Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-12680

[7.1] Config Guide - Defining "timeout" property generates WARN messages

    XMLWordPrintable

Details

    • Documentation (Ref Guide, User Guide, etc.)
    • Hide

      Steps :

      Define below "timeout" property for configuring a tcp based cluster

      ~~~~~~~~
      <protocol type="TCPPING">
      <property name="initial_hosts">
      ${jboss.cluster.tcp.initial_hosts}
      </property>
      <property name="port_range">
      0
      </property>
      <property name="timeout">
      2000
      </property>
      </protocol>
      ~~~~~~~~

      2) Start the cluster

      Below WARN messages will be observed :

      ~~~~~~~~
      WARN [org.jgroups.stack.Configurator] (MSC service thread 1-7) JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead
      ~~~~~~~~

      Show
      Steps : Define below "timeout" property for configuring a tcp based cluster ~~~~~~~~ <protocol type="TCPPING"> <property name="initial_hosts"> ${jboss.cluster.tcp.initial_hosts} </property> <property name="port_range"> 0 </property> <property name="timeout"> 2000 </property> </protocol> ~~~~~~~~ 2) Start the cluster Below WARN messages will be observed : ~~~~~~~~ WARN [org.jgroups.stack.Configurator] (MSC service thread 1-7) JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead ~~~~~~~~

    Description

      While defining "timeout" property in TCPPING as below generates WARN messages.

      TCPPING configuration as per link [1] EAP 7 high availability configuration guide

      ~~~~~~~~
      <protocol type="TCPPING">
      <property name="initial_hosts">
      ${jboss.cluster.tcp.initial_hosts}
      </property>
      <property name="port_range">
      0
      </property>
      <property name="timeout">
      2000
      </property>
      </protocol>
      ~~~~~~~~

      Below is the WARN message generated :

      ~~~~~~~~
      WARN [org.jgroups.stack.Configurator] (MSC service thread 1-2) JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead
      ~~~~~~~~

      Resolution :

      Remove "timeout" property from TCPPING and run the TCP cluster.

      Using the above solutions were not generate the WARN messages.

      We need to EDIT these changes in the EAP 7 high availability documentation.

      Root Cause :

      Discovery is a superclass of TCPPING hence the above WARN message is logged.

      [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html/configuration_guide/configuring_high_availability

      Attachments

        Activity

          People

            sgilda_jira Sande Gilda (Inactive)
            rhn-support-abhati Arnav Bhati (Inactive)
            Richard Janik Richard Janik
            Richard Janik Richard Janik
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: