Logging being intercepted from stdout and being logged at the trace level

[gavintranter]

Good morning,

We have an old commandline application that we have "wrapped" and are trying to deploy into AS 7.  Everything works fine except for the logging.

The applciation has no log4j properties file (it was usual supplied via command line option), the log statements appear to be being logged to stdout, which in turn is being intercepted by AS 7 and written to server.log, additionally for some reason the logging is taking place at the TRACE level rather than DEBUG level (everything else is currently set to DEBUG).

This is causing something of a performance issue for us and I can find nothing in the AS 7 configuration that, to my eyes suggests the log should being logged at TRACE level, nor that it should be going to stdout.

When debugging the code I find that the application has been given a jboss logger (org.jboss.logmanager.Logger) which appears to have its level parameter set to ALL.

Is this some sort of default behaviour for application that are missing their log4j properties, or some sort of default logger that all applications are supplied which they then override if they have a log4j properties file?

If this is default behavior, is it configurable?

Thanks

G

[jaikiran]

Gavin, welcome to the forums!

Which logging library are you using in your application? What exactly does your code (including the import statements for the logging library) look like?

As for the mismatch between the logging levels, perhaps this is relevant https://community.jboss.org/wiki/UsageOfLoggingLevels ?

[gavintranter]

Hi, thank you for the welcome

Logging library:  log4j (1.2.16), slf4j seemes to be included in the libraries but I havent found any imports for it.

import: import org.apache.log4j.Logger;

init: static final Logger LOG = Logger.getLogger(AggregateDiagnosticsImpl.class);

usuage: LOG.trace("current stats :" + currentStats);

Its pretty standard really.  In our newer webservice based apps we do tend to use slf4j rather than log4j directly, but while it is included as a library I actual cant see it being used.

Will check out the link.

Thanks

[jaikiran]

I forgot to ask. Which exact version of AS7 is this?

[gavintranter]

Ah, yeah that might be helpful, its 7.1.2.Final

[gavintranter]

Adding sample problem log output taken from server.log

14:49:16,330 INFO  [|] [stdout] (task-scheduler-1) 8075367 [task-scheduler-1] TRACE net.blah.system.diagnosis.AggregateDiagnosticsImpl  - reporting stats tt: 2899 ept:1359

(redacted the package name to protect the guilty )

So, as can be seen we have a TRACE level message being logged to stdout, which in turn is being intercepted by AS 7 logging and written to the log file.  So each log statement is in effect being logged and written twice, once to stdout then being intercepted and rewritten to the server.log file.

[gavintranter]

Ok, we seem to have solves this by making the log4j library "provided" in the POM file.