MG>you have a saved session state in one of your jboss caches that is
conflicting with your new Basic.war Session State
MG>clean out ALL your jboss caches
MG>rm -rf tmp
MG>rm -rf data
MG>rm -rf log
MG>recompile the whole lot with runtime jdk provided by JBOSS
MG>restart jboss
un saludo
________________________________
From: José Antonio Delgado Trujillo <jadt...@gmail.com>
Sent: Friday, December 29, 2017 9:25 AM
To: Struts Users Mailing List
Subject: Re: log4j problem
After clone the GitHub and deploy basic-struts in Wildly:
log4j is in lib folder
It isn’t any log4j output after test in the browser
(localhost:8080/basic-struts/index.action)
I don’t think is a level problem in WildFly because...
If i did manually the first project basic-struts i can see more info log than
the 2 in the tutorial.
I realise that when i deploy the project (man wildly:deploy) i found a warning
about log4j-api
14:21:11,532 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3)
WFLYSRV0003: Could not index class module-info.class at
/content/basic.war/WEB-INF/lib/log4j-api-2.10.0.jar:
java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 24
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)
What is it happening?
