Question
Anthem
US
Posted: Jul 2, 2018
Last activity: Jul 3, 2018
Last 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.
Posted: 6 years ago
Pegasystems Inc.
IN
Hi 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: 6 years ago
Pegasystems Inc.
US
Hazelcast is not typically the cause of thread dumps, but is often blamed because hazelcast is using many threads, but that is expected.