Continous thread dump while fetching Parent and Child cases by using OOTB default Search feature.
We are using default OOTB search feature to fetch Parent & Child cases. Under one parent there will be around 10 to 60 child cases and is implemented as cover and covered objects. if one parent is having 10 to 30 child cases search is working fine and are able to fetch child case by using OOTB search feature. if the child cases are more than 30 to 60 under one parent query is taking long time and while fetching continuous thread dump is created and system is hanging without any search results.
We have business requirement/need to show all the child cases at a time under parent when end user clicks on parent work object. Please suggest any alternate approach to overcome this issue. Also would like to know from Product Support Community any limitations between Parent and number of child cases that PRPC supports. We are using PRPC 6.3 sp1 version, Apache Tomcat and MS SQL server.
Please let me know if you need any additional information regarding implementation/issue for your valuable suggestions.
Thanks in Advance!!!
***Updated by moderator: Lochan to remove proprietary information; add SR Exists group tag***
I suggest you study both your Pega and alert log files for error message details and stack trace details to get more info about why you are getting a thread dump. For instance, do the details show that an out-of-memory condition exists? Or some other specific error? Since you mentioned that the issue only occurs for highly prolific parents, that could be a clue. /Eric