Question2Replies278Views×Close popoverPradeep Chowdary Pydi (PradeepPydi) Anthem Senior PEGA DEVOPS and Cloud Administrator Anthem IN View ProfileSend Message PradeepPydi Member since 2017 208 posts Anthem Posted: July 2, 2018Last activity: July 3, 2018Posted: 2 Jul 2018 19:25 EDTLast activity: 3 Jul 2018 8:58 EDT Closed Thread Dumps related to Hazlecast on a single development JVM.Hi Team,A lot of thread dumps related to Hazlecast has been observed in the Development JVM logs which slows down the environment.1) How Hazlecast behaves in a environment with Single JVM setup (No clustering topology)2) Any recommendations to get rid of the attached Hazlecast related thread dumps. Low-Code App Development System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post 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. Posted: 2 years agoPosted: 3 Jul 2018 4:09 EDT×Close popoverUjjwal Kumar Shukla (UjjwalShukla_GCS) PEGA Technical Lead Pegasystems Inc. IN View ProfileSend MessageUjjwalShukla_GCS PEGA replied to PradeepPydiHi There, Real issue lies with DB query execution which might have got APPServer to unresponsive state. Thread dumps just shows that Hazelcast thread were running at that time. Please check below lines at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1877) at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:6642) - locked com.microsoft.sqlserver.jdbc.TDSReader@172d3fea at com.pegarules.generated.html_section.ra_stream_ruleformmain_ccbe470dface05f9add5cb8d64195642.buildSection_15(ra_stream_ruleformmain_ccbe470dface05f9add5cb8d64195642.java:361) Regards, Ujjwal Posted: 2 years agoPosted: 3 Jul 2018 8:58 EDT×Close popoverNick Loving (NickLoving_GCS) PEGA Senior Software Solutions Engineer Pegasystems Inc. US View ProfileSend MessageNickLoving_GCS PEGA replied to PradeepPydiHazelcast is not typically the cause of thread dumps, but is often blamed because hazelcast is using many threads, but that is expected.