Same user id is getting logged in all the logs in PegaRULES.log
User has seen that all the log statements from master agent are being logged with the same user id other than "System" in their production server.They do not see any exceptions. User does not have this issue with other jvm on the same cluster.
This functionality works fine in the past, but this seems to be having issue after the last release or two weeks ago), no configuration change was done in the last release, only application rules were deployed, this rules change is same for both the application servers in the cluster.
Below is their system configuration:
- PRPC 7.1.6
- Websphere Application Server
- Oracle 11g
Also the requestor lock exceptions are logged in with only one user even though, user is not logged into the system.
No error, but all the logs show the same user id irrespective of the user that is throwing the exception.
2015-12-08 01:08:32,613 [.PRPCWorkManager : 1] [ STANDARD] [ PegaRULES:07.10] ( internal.async.Agent) INFO kandikoa - System date: Tue Dec 08 01:08:32 EST 2015 Total memory: 3,837,552,640 Free memory: 1,451,829,016 Requestor Count: 14 Shared Pages memory usage: 0%
Above log has “kandikoa” instead of “System”
The above log must be
2015-07-19 00:07:37,716 [.PRPCWorkManager : 1] [ STANDARD] [ PegaRULES:07.10] ( internal.async.Agent) INFO - System date: Sun Jul 19 00:07:37 EST 2015 Total memory: 2,767,337,472 Free memory: 1,042,896,832 Requestor Count: 11 Shared Pages memory usage: 0%
Steps to Reproduce
1) Go to logging level setting landing page.
2) Reset the logging level and check the logs for this behavior.
The issue is coming after logging level setting reset by user . Once the logging level is re-set. User id is coming in all the entries of the master agent in the logs.
After the reset of logging level for requestor1, all the logging information (hashtable inside MDC map) are copied onto the dispatcher thread which is used to write the loggers to console and file asynchronously and never cleared. Hence after this operation, the contents of the dispatcher thread remain same.
Apply HFix-25560 to solve the issue.
Published February 9, 2016 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.