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

[GSS](7.2.z) "WFLYSRV0003: Could not index class ..." happens during application deployment when the packaged library contains module-info.class

    XMLWordPrintable

Details

    Description

      "WFLYSRV0003: Could not index class ..." happens during the application deployment when the packaged library contains module-info.class.

      For example, module-info.class is included in log4j2 since 2.10.0 or later. So, when an application uses and packages the latest log4j2, the following WARN message is logged at the deployment:

      WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0003: Could not index class META-INF/versions/9/module-info.class at /content/example.war/WEB-INF/lib/log4j-api-2.11.1.jar: java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 32
	at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:1417)
	at org.jboss.jandex.Indexer.index(Indexer.java:1451)
	at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99)
	at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

      I think this is not harmful, but it's better to suppress this WARN log.

      This is the same issue to JANDEX-40 which was already fixed in jandex 2.0.4.Final or later. (JANDEX-41 is also related, but EAP 7.1 does not support JDK 9+. So, JANDEX-40 is enough for EAP 7.1.z.)

      Please upgrade jandex to 2.0.4.Final or later (2.0.5.Final would be better as it's the latest at this moment).

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15261 [GSS](7.1.z) "WFLYSRV0003: Could not index class ..." happens during application deployment when the packaged library contains module-info.class

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15261 [GSS](7.1.z) "WFLYSRV0003: Could not index class ..." happens during application deployment when the packaged library contains module-info.class

          • 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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-15262 [GSS](7.2.z) Update jandex from 2.0.3.Final-redhat-1 to 2.0.5.Final

          • 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
          is related to

          Feature Request - Feature requests from customers and/or users JANDEX-40 Ignore module-info.class files when running under Java8

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

          Web Link KCS#3568471

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: