Why am I not seeing my PX log file

I have installed some PXs to assist in processing data for an integration. I set up a log file for them as follows :

    <appender name=”PLMBLog” class=”org.apache.log4j.RollingFileAppender”>
            <param name=”File”   value=”${agile.log.dir}/sdk.log” />
            <param name=”Append” value=”true” />
            <param name=”MaxFileSize” value=”1MB”/>
            <param name=”MaxBackupIndex” value=”5″/>
            <layout class=”org.apache.log4j.PatternLayout”>
                <param name=”ConversionPattern” value=”%dt%tt&lt;%c{1}:%p&gt;t%mn”/>
            </layout>
    </appender>
    <category name=”com.xyz” additivity=”false”>
        <priority value=”DEBUG” />
       <appender-ref ref=”PLMBLog” />
    </category>

 But the log file is never created, so I am sitting blind trying to do testing of the PXs.
 Would a good next step be to replace “${agile.log.dir}” with an actual file path?  Note that the value is used in many other log file definitions, and they seem to be where expected.
 This is for Agile 9360, running on Linux.

Add Comment
4 Answer(s)

I have experienced that the old log4j logging for PXs does not work with java 1.8, which is what 9.3.6 is using. I have gone with tinylog instead. Have not verified tinylog works on linux.

Agile Angel Answered on March 7, 2018.
Add Comment

Pardon me if it sounds to basic but i too faced similar issue in 9.3.5 recently. The only different thing i did was to give the actual path of log file on server.  Since i was in analysis phase so i kept the logger level to INFO and verified that am printing logger.info(“”) only.

Agile Angel Answered on March 7, 2018.
Add Comment

Hi Kevin,

Not sure if your problem has been already resolved or not. If not, then have you tried setting the log4j config file in Agile’s start up script?

Agile Professional Answered on July 2, 2018.
Add Comment

On A9 936 RUP 8, ended up writing a “logging” code that programmatically modifies the existing log4j2 log context used by A9 by inserting my own RollingFileAppender logger if it doesn’t already exist.

Replaced the log4j2  jar files in agileDomain/lib folder with the latest from log4j 2 Apache website.

Each PX gets it’s own log file => easy to debug.  I also have configurable means to set the “root” logger level to DEBUG dynamically during PX startup/execution, so any not configured PX’s log will show up in the stdout (which is the way A9 sets p the root logger for log4j 2 )

Agile Talent Answered on March 27, 2019.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.