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

[GSS](7.2.z) JDK 11 Multi-Release jars - Classes for newer versions are not loaded and VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.2.2.CR1, 7.2.2.GA
    • None
    • Server, VFS
    • None

    Description

      JDK 11 Multi-Release jars - Classes for newer versions are not loaded and VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value

      Caused by: java.lang.UnsupportedOperationException: No class provided, and an appropriate one cannot be found.
	at deployment.log4j-2.9.0.war//org.apache.logging.log4j.LogManager.callerClass(LogManager.java:525)
	at deployment.log4j-2.9.0.war//org.apache.logging.log4j.LogManager.getLogger(LogManager.java:550)
	at deployment.log4j-2.9.0.war//org.apache.logging.log4j.LogManager.getLogger(LogManager.java:537)
	at deployment.log4j-2.9.0.war//reproducer.Init.<clinit>(Init.java:11)
	... 42 more

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4266 Classes for newer versions are not loaded from Multi-Release-JARs in WARs

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4298 Multi-release jar resource loading in VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value

          • 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
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-16580 (7.2.z) Upgrade WildFly Core from 6.0.12 to 6.0.14

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

          Web Link KCS

          Activity

            People

              chaowan@redhat.com Chao Wang
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: