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

Truncated binary stream encountered opening WOs in production



AES Weekly Scorecard report for production environment was reviewed and it was discovered that the top exception indicates some level of blob corruption 

Error Messages

Exception-98318 Truncated binary stream encountered; expected decompressed size of 928119, but actually got 653832 

Steps to Reproduce

Unknown.  It was a random and very rare event.

Root Cause

The root cause of this problem is in a third-party product integrated with PRPC.   The 
Sun JVM version 1.6_14 is fairly old and we have seen this same type of behavior with this version previously.  Confirmed if we look at the compressed blob in the database the first part of the blob contains valid data but the remaining part of the blob contains nulls.  


This issue is resolved by making the following change to the PRPC operating environment: U
pgraded the JDK version to 64 Bit - 1.6_045.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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