Slow Startup / Compilation Issues
Compilation and Slow Startup issues are being experienced with multiple 7.1 ML 7 applications. This behavior is experienced most acutely when following a clear cache (deletion of temp directory and extract marker file).
User's application is a cluster of 2 servers which in turn have 4 jvm’s each (CAQServer01, CAQServer02, CAQServer03 and CAQServer04). Due to hazelcast time-out issues, user changed our startup strategy to one server (cluster of 4 jvm’s) at a time. User is still running into myriad of compilation issues on one or the other node.
Error compiling: ...
com.pega.pegarules.pub.generator.FirstUseAssemblerException: Failed to compile generated Java
Steps to Reproduce
Start multiple server / multiple application server environment following a clear cache.
In Pega 7.1.7, the main folder extractedFiles/apploader is getting created in JVM temp folder. In case the JVM is restarted, these files will be deleted, which is happening in this case. Customer is having Cluster with multiple nodes. When they re-start the cluster the nodes starts all at once then it is most likely that the folder extractedFiles/apploader created by one node is being deleted by another node. Ideally, extractedFiles/apploader should be created in the temp folder location of each node. This issue is specific to WAS ear deployment prpc_j2ee14_ws.ear file in Pega 7.1.7 and similar issue SR-A10012 for the same customer.
Specify a JVM argument java.io.temp to redirect the files to a location which is different for each nodes in the cluster.
0% found this useful