Hello Everyone,

we are facing slowness issue in our development environment which also leads to multiple thread-dumps and then we have to go of an env-restart.

i have found from previous posts in pdn with the same thread dump exception however there is no helpful information.

its hindering our development activities, need your suggestions.

Steps done already:-

1- restarted admin server and PRPC App after clearing the caches and clearing the active threads

2- stopped agents and started only the one we need as of now

3- checked for tablespace issue(no trouble here)

4- JVM allocation is also fine, and there is below average usage of the machine and memory.

Thanks in advance for your quick suggestion.



Keep up to date on this post and subscribe to comments

December 7, 2018 - 9:18am


have you got a chance to review the complete PRPC logs to see what operations are taking time?


1. Any long running queries?

2. Whats the requestor count? Can i get the environment details? Have the capacity planning is done for the environment, like how much the system is capable to respond for the number of requestor / other operations?

3. Are there any frequent RD's running which are taking huge time?

4. Depending on the kind of operations, have you reviewed the alert logs, to see what is frequently hitting the system?

5. Why is thread dump being triggered?

Whether any operations like activity / any thread which is stuck and executing for long time, making other many threads getting piled up?

6. DB Intensive operations?

7. How many users are accessing the application? Requestor Count?

8. How many nodes? Environment details? 

It goes on.. 

I would suggest you to send us the Pega-Rules and Alert Logs, from startup till application going down. 


December 7, 2018 - 9:42am

Even we are facing same issue in production.

Kindly share the work around for this (if any)


Divya Sri Padarthy

December 7, 2018 - 9:48am
Response to divyasripadarthy

Divya - Can you please share the Pega-Rules and Alert Logs - Complete file from start up. 

December 7, 2018 - 10:04am
Response to DilipLingaraju

We are getting same log message what Swagat had already attached.

Whenever we try to open case from list of class instances, we are facing this issue.

December 7, 2018 - 10:19am
Response to divyasripadarthy

Hello Divya, 

Provided logs containing just 1 thread dump and is NOT sufficient to review the entire application performance. 

Hence, we wanted Complete Pega-Rules Logs file, starting from app server startup. & respective Pega-Alerts log file




December 7, 2018 - 9:48am

Divya - Can you please share the Pega-Rules and Alert Logs - Complete file from start up.