jbas015852 could not index class java.lang.IllegalStateException: Unknown tag

11
votes

This error happens when deploying to a local JBOSS server. Is there a way to resolve this warning?

22:31:22,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015852: Could not index class com/company/core/security/AuthRealm.class at /C:/DevTools/jboss-eap-6.3/bin/content/platform-ws-0.1.war/WEB-INF/lib/com.company.platform-platform-core-0.1.jar: java.lang.IllegalStateException: Unknown tag! pos=20 poolCount = 133 at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] at org.jboss.jandex.Indexer.index(Indexer.java:640) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31]

An explanation of what is going on would be much appreciated, too.

1
javajboss6.x
The error seems to say that this class is corrupt: com/company/core/security/AuthRealm.class. Try rebuilding your application. – yole
Getting this too. JBoss AS 7, Java 7. Luckily it appears to be just a warning. Seems to deploy ok. Started happening when I added tika jar file to war file. – E L

1 Answers

17
votes

I'm using JBoss EAP 6.3 with patch 6.3.3 but to solve the problem I need to use jandex from JBoss EAP 6.4. I just replace "jandex-1.0.3.Final-redhat-2.jar" for "jandex-1.2.2.Final-redhat-1.jar" in JBoss modules and problem was solved.

There is a issue in JBoss of it, maybe problems with Java 8 or lambda expressions that Jandex can´t index. See this link This is the link of the issue Bug 1193113 I hope that help you