Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

JVM hang analysis



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 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


Root Cause

The root cause of this problem is in a third-party product integrated with PRPC. Database Connection Pool / DB connectivity issues.


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

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us