struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <>
Subject Re: log4j problem
Date Fri, 29 Dec 2017 14:49:06 GMT

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 <>
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
I realise that when i deploy the project (man wildly:deploy) i found a warning about log4j-api

14:21:11,532 WARN  [] (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(
        at org.jboss.jandex.Indexer.index(
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(
        at org.jboss.msc.service.ServiceControllerImpl$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

What is it happening?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message