Are there any specifc pattern of Problem Cases where the Classloader problems occur for Pega on WebSphere Application Server ? Interested to know about a sample problem case or a sample log which indicates us to go for enabling the Classloader traces.
For example, if you have a memory leak issue where you want to understand why certain are not marked for garbage collection; or you are troubleshooting the classloading conflict issues in Pega product (e.g., why a specific class is loaded by Websphere but not from the Pegaclassloader (from the database).
Classloading problems can take various forms. You may get noclassdeffoundexception, classcastexception or compilation errors since the loaded class does not have the necessary method for Activity/Library compilation.