Question
1
Replies
489
Views
Accenture
Posted: August 13, 2018
Last activity: August 13, 2018
Closed
Experiencing Slowness in Application due to Thread Dumps / RequestorLockException
We experience slowness in our Pega Marketing application. It left the entire UI unresponsive, and we were also unable to access Pega when we tried a new session, leaving us to resort to restarting the server.
Upon checking the logs, there were a few thread dumps accompanied by RequestorLockException. Our user base is small, less than 10 users.
Can anyone pinpoint the cause of the thread dumps by looking at the pegarules log? I assume the slowness was caused by the thread dumps. Correct me if I'm wrong.
Thanks!
***Edited by Moderator Marissa to update platform capability tags****
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Hi
I suspect it may be an issue of the urandom, all the thread dumps were blocked by thread running below stack
"https-jsse-nio-8443-exec-6" Id=117 in RUNNABLE (running in native)
BlockedCount : 83, BlockedTime : -1, WaitedCount : 4882, WaitedTime : -1
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:255)
at sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)
at sun.security.provider.NativePRNG$RandomIO.implGenerateSeed(NativePRNG.java:441)
- locked java.lang.Object@2b7a403c
at sun.security.provider.NativePRNG$RandomIO.access$500(NativePRNG.java:331)
at sun.security.provider.NativePRNG.engineGenerateSeed(NativePRNG.java:226)
at java.security.SecureRandom.generateSeed(SecureRandom.java:533)
at com.pega.pegarules.exec.internal.util.PRRandom.reseedGenerator(PRRandom.java:119)
at com.pega.pegarules.exec.internal.util.PRRandom.checkToReseed(PRRandom.java:124)
at com.pega.pegarules.exec.internal.util.PRRandom.nextInt(PRRandom.java:87)
at com.pega.pegarules.data.internal.dictionary.ClassMapImpl$ClassAncestors.<init>(ClassMapImpl.java:7586)
Please check the following support articles and suggest to apply the solution and check if that helps
https://community.pega.com/support/support-articles/agent-thread-stops-working-while-reading-random-device
https://community.pega.com/support/support-articles/pega-application-stopped-responding-10-15-min
https://community.pega.com/support/support-articles/requestorlockexception-developer-environment