Support Article

Log not written at the expected location



Log files are not written in the expected location despite the log location is being set correctly using a JVM parameter. Log subsystem is not taking this path into account and log files are written directly in the profile path of the application.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

The prlogging.xml file from the problematic node was not present in the directory structure.
This led us to believe that the user had probably externalised the prlogging.xml and hence the JVM setting was most likely wrong.


Setting the following JVM argument on its own is not enough to change the location of the log file


The JVM flag above just points to a directory path, this by itself is not enough to set where the log files are to be located, this has to be done along with a change to the prlogging.xml file.

For example taking the JVM setting above you would then need to modify the following entry in the prlogging.xml file to reflect the variable set as the JVM argument

<param name="FileNamePattern" value="'${PegaLogLocation}/PegaRULES-'yyyy-MMM-dd'.log'"/>

The variable defined in the JVM argument is then used alongside with the value setting in the prlogging.xml to produce the full path for the log file in the example above:


Published February 24, 2017 - Updated March 1, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.