Seeing hung connections
SummaryThe user recently upgraded from 6.3 to 7.2.1 in their QA environment. They are seeing frequent hung threads related to the db environment that they did not experience in the 6.3 environment. There are hung thread messages in the attached SystemOut.log file.
Error Messages[1/13/17 21:17:10:317 GMT] 000001c1 AppServerBrid E com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega Problem during method invocation (invokeEngine)java.lang.NoClassDefFoundError: com/pega/apache/log4j/spi/ThrowableInformationat com.pega.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:155)at com.pega.apache.log4j.Category.forcedLog(Category.java:391)at com.pega.apache.log4j.Category.error(Category.java:322)
Steps to ReproduceHappens during normal processing as well as occassionally on jvm recycles
Root CauseA defect or configuration issue in the operating environment .In the above trace we can see that server is not able to load classes correctly from database.
ResolutionSet the below DSS setting and restart the server:Ruleset: Pega-EnginePurpose: prconfig/initialization/preloadengineclasses/defaultValue: com.pega.pegarules.priv.util.StackTracecom.pega.apache.log4j.spi.ThrowableInformationTo set via DSS - refer https://pdn.pega.com/how-set-prconfig-values-dynamic-system-setting-value The DSS setting is to circumvent this, to forcibly pre-load that class. Even from the thread dump trace we can see that it is looking for the same package.
Published February 14, 2017 - Updated February 18, 2017