Simple logging configuration made complex in Wildfly !

[giridhar.shankar]

Folks,

     I am struggling to get log4j working in my Wildfly setup.  It is such a simple thing that JBOSS team has made it complicated unnecessarily.  Such tools must aid developers but instead it is adding more pain to the development process.  Can somebody please send me steps to get logging working in JBOSS server?  Here is my environment:

1. Version: Wildfly 8.2.1

2. JDK 1.8.0u51

3. Error I get (at run time - at the line that loads Logger class): java.lang.ClassNotFoundException: org.jboss.logmanager.Level

4. I tried all these things but in vain

     a) Tried deployment level logging

          Followed instructions posted by JBOSS and a couple of folks who claimed it worked for them - Logging Configuration - WildFly 8 - Project Documentation Editor, Using Log4J with JBoss AS 7 and WildFly.  None of these worked and I still get the same error

     b) Tried app level logging.  Disabled deployment level logging using <use-deployment-logging-config value="false" /> and specifying logging profile in the MANIFEST file

    Is there a right way to get this working?  Anybody please?

Thanks,

Giri

[mayerw01]

I cannot confirm your impression that logging had been made complicate in WildFly.

I've just unpacked the wildfly-8.2.1.Final.zip, added the administrator account and run ./standalone.sh  -c standalone-full.xml.

Then deployed a war containing a servlet where I just added the 2 lines

private static final Logger log = Logger.getLogger("ServletName");

log.info("The information to be logged ...");

I did no configuration at all.

[jameslivingston]

Can you post the stack trace of the ClassNotFoundException? Deployments generally shouldn't see the log manager's Level class, only the main j.u.l one.