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

JGroups subsystem logs "version is missing in the configuration file" warning on startup

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.4.0.CD20
    • 7.4.0.CD20
    • Clustering
    • None

    Description

      We are seeing Warning on server startup

      17:29:06,996 WARN  [org.jgroups.conf.XmlConfigurator] (ServerService Thread Pool -- 90) version is missing in the configuration file

      This seems to be already fixed on WF master so we should cherrypick the fix to CD20 not to introduce new warning

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-13590 JGroups subsystem logs "version is missing in the configuration file" warning on startup

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-13657 JGroups subsystem logs "version is missing in the configuration file" warning without a log code on deployment using JPA 2LC

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19787 JGroups subsystem logs "version is missing in the configuration file" warning without a log code on deployment

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              jbliznak@redhat.com Jan Blizňák
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: