Log entries in EAP 7 do not show the module and line number correctly

[erichardesty1]

I am converting from EAP 6.4 and EAP 7 but am having issues with log entries.  The module and line number are not correct, they are always module(log) & linenumber(134) for every log entry.

Is this a bug or do I need to specify something else to include the correct location in each log entry?

Eric

Here is my configuration:

            <periodic-rotating-file-handler name="LTP" autoflush="true">

                <formatter>

                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c.%M.%L] (%t) %s%E%n"/>

                </formatter>

                <file relative-to="jboss.server.log.dir" path="ltp.log"/>

                <suffix value=".yyyy-MM-dd"/>

                <append value="true"/>

            </periodic-rotating-file-handler>

            <logger category="com.bull" use-parent-handlers="false">

                <level name="DEBUG"/>

                <handlers>

                    <handler name="LTP"/>

                </handlers>

            </logger>

output from EAP 6.4:

09:29:15,545 DEBUG [com.bull.opentp.rts.cobol.CobolRuntimeSupport.start.69] (ResourceAdapter.runtimeThread) ENTER

09:29:15,546 DEBUG [com.bull.opentp.rts.cobol.CobolRuntimeSupport.start.83] (ResourceAdapter.runtimeThread) EXIT

output from EAP 7

14:21:53,622 DEBUG [com.bull.opentp.rts.cobol.CobolRuntimeSupport.log.134] (ResourceAdapter.runtimeThread) ENTER

14:21:53,622 DEBUG [com.bull.opentp.rts.cobol.CobolRuntimeSupport.log.134] (ResourceAdapter.runtimeThread) EXIT

[jaikiran]

Can you show us the code which logs this message? Also, what Java vendor and version do you use to compile your code? Did you maybe recompile it while deploying it to the newer EAP version?

[erichardesty1]

This was attempted using both the 7.1.0.Alpha & 7.1.0.Beta  EAP versions but both fail in the same manner.  It is compiled with Oracle jdk 1.8.  It is compiled on Windows but deployed on Linux.

Here are the Log pieces of code:

import org.apache.commons.logging.Log;

import org.apache.commons.logging.LogFactory;

static final String logName = CobolRuntimeSupport.class.getName();

private static final Log log = LogFactory.getLog(logName);

public void start() throws ResourceAdapterInternalException {

log.debug("ENTER");

....

log.debug("EXIT");

}

Every log message in that file handler have the same values for module and line number from every other class in the Resource Adapter.

Eric

[jaikiran]

Thanks for these details. This does look like a bug.

Based on what I see in your code (which uses the Apache commons logging), the pattern format string that you use and what's being logged, I think what's happening here is that the methodName (which the M represents) and the lineNumber (that L represents) are being picked up from the method and line number of the JBoss Logging adapter for Apache commons logging here commons-logging-jboss-logmanager/JBossLog.java at master · jboss-logging/commons-logging-jboss-logmanager · GitHub

jamezp or dmlloyd might be able to confirm this.

[jamezp]

Jaikiran is correct. This is a bug in the commons-logging-jboss-logmanager project. This PR should fix it.

If you need a fix for EAP 7 feel free to file a bug. The workaround would be to not use commons-logging and use something like slf4j or jboss-logging for your logging facade. Though I realize swapping out a logging facade isn't always that simple.

--

James R. Perkins