Support Article
JVM hang analysis
SA-3337
Summary
JVM was unresponsive/crashed/unavailable
Currently 1 of 4 JVMS required restart
Error Messages
2014-11-02 08:02:54,462 [ WorkManager(2)-27] [ STANDARD] [ MyApp:06.03.01] ( internal.access.Opener) ERROR - There was a problem opening a database instance SYSTEM-CACHEDCONCLUSION PROPERTY!PXRDBERROR!34
com.pega.pegarules.pub.database.ConnectionException: Database-General There was a problem opening a database instance SYSTEM-CACHEDCONCLUSION PROPERTY!PXRDBERROR!34 -4499 08001 [jcc][t4][2030][11211][3.62.56] A communication error occurred during operations on the connection's underlying socket, socket input stream,
or socket output stream. Error location: Reply.fill() - insufficient data (-1). Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001
Steps to Reproduce
NA
Root Cause
The root cause of this problem is in a third-party product integrated with PRPC. Database Connection Pool / DB connectivity issues.
Resolution
This issue is resolved by making the following change to the PRPC operating environment: Increating max pool size of DB connection pool to create more connecitons, also monitoring connection pool usage.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.