Question
Anthem
US
Last activity: 17 Apr 2018 1:55 EDT
Log data not getting populated although prlog4j2.xml has been configured correctly.
Hi Team,
Although prlog4j2.xml has been configured correctly,we couldnt find the log data getting populated.
PFA for the screenshot.
PRPC version : 7.3.1
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
Can you provide your prlog4j2.xml file?
Anthem
US
PFA for the requested file.
Pegasystems Inc.
US
Try changing this
"'D:/PEGA_LOGS/COMPASS5D/PegaRULES_1D002-'yyyy-MMM-dd'.log'"
to this
"D:/PEGA_LOGS/COMPASS5D/PegaRULES_1D002-{yyyy-MMM-dd}.log"
Also change this
Try changing this
"'D:/PEGA_LOGS/COMPASS5D/PegaRULES_1D002-'yyyy-MMM-dd'.log'"
to this
"D:/PEGA_LOGS/COMPASS5D/PegaRULES_1D002-{yyyy-MMM-dd}.log"
Also change this
<Configuration status="WARN">
to this
<Configuration status="debug">
This will cause log4j to explain itself during startup (output to console)
something like this - hopefully enough other info to let you know what is happening:
DEBUG Building Plugin[name=logger, class=org.apache.logging.log4j.core.config.LoggerConfig].
DEBUG createLogger(additivity="true", level="DEBUG", name="com.pega.pegarules.integration.engine.internal.services.ServiceAPI", includeLocation="null", ={
00/webapps/prweb/WEB-INF/classes/prlog4j2.xml), Filter=null)
DEBUG Building Plugin[name=loggers, class=org.apache.logging.log4j.core.config.LoggersPlugin].
DEBUG createLoggers(={root, com.pega.pegarules.session.internal.mgmt.SecurityEventLogger, com.pega.pegarules.data.internal.access.ExtractImpl, com.pega.pe
, com.pega.pegarules.data.internal.access.DatabaseUtilsCommonImpl, com.hazelcast, org.apache.ignite, com.pega.pegarules.integration.engine.internal.servic
gine.internal.services.ServiceAPI})
DEBUG Configuration XmlConfiguration[location=file:/C:/TestSystems/P7300/webapps/prweb/WEB-INF/classes/prlog4j2.xml] initialized
DEBUG Starting configuration XmlConfiguration[location=file:/C:/TestSystems/P7300/webapps/prweb/WEB-INF/classes/prlog4j2.xml]
DEBUG Starting AsyncLoggerConfig disruptor for this configuration with ringbufferSize=262144, waitStrategy=TimeoutBlockingWaitStrategy, exceptionHandler=o
ConfigDefaultExceptionHandler@47151bfb...
DEBUG Started configuration XmlConfiguration[location=file:/C:/TestSystems/P7300/webapps/prweb/WEB-INF/classes/prlog4j2.xml] OK.
DEBUG Shutting down OutputStreamManager SYSTEM_OUT.false.false-1
DEBUG Stopped org.apache.logging.log4j.core.config.DefaultConfiguration@2e38e75b OK
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=StatusLogger
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=ContextSelector
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=com.pega.pegarules.data.internal.access.ExtractParameters
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=com.hazelcast
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=org.apache.ignite
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=com.pega.pegarules.session.internal.mgmt.SecurityEventLogger
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=,subtype=RingBuffer
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=com.pega.pegarules.data.internal.access.ExtractImpl
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=com.pega.pegarules.integration.engine.internal.services.listener
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=com.pega.pegarules.integration.engine.internal.services.ServiceAPI
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Loggers,name=com.pega.pegarules.data.internal.access.DatabaseUtilsCommonImpl
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Appenders,name=CONSOLE
DEBUG Registering MBean org.apache.logging.log4j2:type=445eb59,component=Appenders,name=PEGA
Anthem
US
Hi Jim,
The above mentioned changes has been implemented followed by a restart.But still the same issue.
Please help.
Pegasystems Inc.
US
Hi Pradeep,
Can you attach the DEBUG logs from the server as Jim had suggested in his post earlier? Reviewing that would help us with finding the root cause of the issue.
Thanks,
Ankur
-
Prashasti Panirajaindra
Anthem
US
Hi Ankur,
I believe you are looking for a PEGARules log ? As I have mentioned above,I dont have any log data getting populated.
Ucare
US
Did your issue get resolved ? We are having same issue after update to 7.3.1 .
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.