Question
Cognizant
CH
Last activity: 5 Oct 2017 17:09 EDT
Errors on JBoss server: PRESENCECLEANER_DAEMON, ConcurrentModificationException
Hi,
I have a Pega 7.3 installed on a JBoss server (7.0 EAP).
It generally works, but I have a lot of errors which stacktrace end with lines like these:
Caused by: com.pega.pegarules.pub.PRException: Failed to execute Resource Adapter function: PRESENCECLEANER_DAEMON {ExecutionDelay=18, NodeID=e326d698c9e20b4dce52b25451054687, ClientID=PegaRULES-PresenceS
essionStateTrackerDaemon}
From: (unknown)
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:136)
at com.pega.pegarules.session.internal.presence.PresenceSessionStateTrackerDaemon.requeueETierInvocation(PresenceSessionStateTrackerDaemon.java:176)
... 164 more
Caused by: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437)
at java.util.HashMap$EntryIterator.next(HashMap.java:1471)
at java.util.HashMap$EntryIterator.next(HashMap.java:1469)
at java.util.HashMap.putMapEntries(HashMap.java:511)
at java.util.HashMap.putAll(HashMap.java:784)
at com.pega.pegarules.resadap.RAClient.execute(RAClient.java:213)
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:132)
... 165 more
I have seen many ConcurrentModificationException issues and solutions listed on PDN, but they look different, the PRESENCECLEANER_DAEMON part do not appear in them.
Has anyone encountered this error before? What could be the root cause of it and what is the possible fix?
Hi,
I have a Pega 7.3 installed on a JBoss server (7.0 EAP).
It generally works, but I have a lot of errors which stacktrace end with lines like these:
Caused by: com.pega.pegarules.pub.PRException: Failed to execute Resource Adapter function: PRESENCECLEANER_DAEMON {ExecutionDelay=18, NodeID=e326d698c9e20b4dce52b25451054687, ClientID=PegaRULES-PresenceS
essionStateTrackerDaemon}
From: (unknown)
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:136)
at com.pega.pegarules.session.internal.presence.PresenceSessionStateTrackerDaemon.requeueETierInvocation(PresenceSessionStateTrackerDaemon.java:176)
... 164 more
Caused by: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437)
at java.util.HashMap$EntryIterator.next(HashMap.java:1471)
at java.util.HashMap$EntryIterator.next(HashMap.java:1469)
at java.util.HashMap.putMapEntries(HashMap.java:511)
at java.util.HashMap.putAll(HashMap.java:784)
at com.pega.pegarules.resadap.RAClient.execute(RAClient.java:213)
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:132)
... 165 more
I have seen many ConcurrentModificationException issues and solutions listed on PDN, but they look different, the PRESENCECLEANER_DAEMON part do not appear in them.
Has anyone encountered this error before? What could be the root cause of it and what is the possible fix?
Best regards,
Attila
***Updated by moderator: Lochan to add SR details***
Accepted Solution
Cognizant
CH
From our conversation in the SR:
Create a DSS " prconfig/operatorpresence/enabled/default " in the Pega-Engine (Owning Ruleset) and set the value to false.
This disables the Operator Presence feature and solves the symptom. I tested it on a JBoss EAP 6.4 server for 8 days, there is no more ConcurrentModificationException in the server.log.
I'm waiting for the answer what Operator Presence is good for, there is still an ongoing investigation from Pega's side regarding that issue, I will update this thread as soon the question is closed.
Pegasystems Inc.
IN
Hello Attila,
Could you please share us the complete pega rules log file to check further more on the issue .
I did some search on the stack trace i have found below article which is related to MQ configuration however not sure if it's related .
Once we go through the stack trace will tell you more on this .
Thanks,
Arun
Cognizant
CH
Hi Arun,
Thank you for the fast response and your idea. You are right, it has something to do with MQ. We use JBoss EAP 7 and the default ActiveMQ messaging.
I attached the PegaRULES.log and the server.log as well as it contains more helpful information.
Thanks for your help,
Attila
Pegasystems Inc.
IN
Hello Attila,
As your using Pega 7.3 we doesn't support officially Jboss EAP 7 .
So will recommend you to go through below platform support guide and use a Application server which supports Pega 7.3 .
https://collaborate.pega.com/discussion/prpc-5x-6x-platform-support-guide-easy-find
Let me know if you have any other questions .
Thanks,
Arun
Cognizant
CH
Hi Arun,
Yeah, I know, JBoss Redhat EAP 6.4.x is the latest supported version.
Take this question as a developer's curiosity not as an error report to Pega. :-) We just wanted to use a newer version of the app server, but I guess we will go with the EAP 6.4.x then.
Thanks for your help,
Attila
Cognizant
CH
Hello Arun,
I moved Pega to a JBoss EAP 6.4 server using Java 8 (it is a supported config according to the Platform Support Guide) and the exact same error occurs.
Attached a new log from this server. As I understand from the stack trace the issue has to do something with modifying a collection while iterating over it, just like here: https://community.pega.com/support/support-articles/concurrentmodificationexception-cleatmessages-api
Perhaps there is an existing fix for the issue, but there are multiple hotfixes listed on PDN in connection with ConcurrentModificationException, I don't know, which could be applicable to my case.
Please help debugging the root cause of the exception or check if there is an applicable existing hotfix.
Thanks,
Attila
ANZ
IN
Hi Arun, Attilo,
We are facing same issue. We use WAS Proprietary information hidden.
Can you share the hotfix that will fix this issue.
Thanks, Naveen
Pegasystems Inc.
US
Naveen - Attilo has raised SR-B73244 with GCS team and its being under progress, you can wait for a while to get the resolution once the SR has been fixed or you can raise your own SR to seek help from GCS team.
Accepted Solution
Cognizant
CH
From our conversation in the SR:
Create a DSS " prconfig/operatorpresence/enabled/default " in the Pega-Engine (Owning Ruleset) and set the value to false.
This disables the Operator Presence feature and solves the symptom. I tested it on a JBoss EAP 6.4 server for 8 days, there is no more ConcurrentModificationException in the server.log.
I'm waiting for the answer what Operator Presence is good for, there is still an ongoing investigation from Pega's side regarding that issue, I will update this thread as soon the question is closed.
Pegasystems Inc.
US
Thanks for sharing this information Attila, @naveen you can try with this change and let us know if it had fixed your issue.
Cognizant
CH
From the SR:
Presence information record is created by engine upon first session for the operator and destroyed when last session goes away. Presence information is per operator, it is not per requestor session.
With that I accept the above modification as a final solution for now.