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

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

XMLWordPrintable

      "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).

              chaowan@redhat.com Chao Wang
              rhn-support-mmiura Masafumi Miura
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: