Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Aaron Bosley (abosley)
PNC
Technology Engineer Senior
PNC
US
abosley Member since 2012 2 posts
PNC
Posted: Dec 24, 2018
Last activity: Mar 8, 2019
Posted: 24 Dec 2018 11:34 EST
Last activity: 8 Mar 2019 15:14 EST
Closed
Solved

Truncated binary stream encountered when test Agent in PRPC 8.1.1

We upgraded from 7.3.1 to 8.1.1 for our application recently and I am testing the application agents to ensure that they are working properly in 8.1.1 . One of agents have issue that seems to be persist when I test it few times. Here is the error from the log:

2018-12-24 10:59:00,597 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ xxxxx] (ard.StandardEnvironmentAdapter) ERROR - Truncated binary stream encountered; expected one of size 21294, but actually got 9216
2018-12-24 10:59:00,598 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ xxxxx] (ard.StandardEnvironmentAdapter) ERROR - Read 4000 of the total 4000 bytes of compressed input (0 remaining); more input is required
com.pega.pegarules.data.internal.clipboard.directstream.BadStreamDataException: Truncated binary stream encountered; expected decompressed size of 21294, but actually got 9216
at com.pega.pegarules.data.internal.clipboard.directstream.InflaterV7.inflateV7(InflaterV7.java:51) ~[prdirectstream.jar:?]
It does not seem to be database error but internal Pega error ? I searched in Pega Community and I am not able to find anything similar to this.
So, anyone know whats up with this issue or have ideas on what I can do to fix this ?
Thanks
Aaron
***Edited by Moderator Marissa to update SR Details***
To see attachments, please log in.
Pega Platform
Updates
Support Case Created

Posted: 6 years ago
Posted: 9 Jan 2019 10:33 EST
Vipin Kumar (DHEER_GCS)
PEGA
Director, Technical Support, Cloud Service
Pegasystems Inc.
US

There are many factors that can cause this. We may need you to run some tools against the BLOBs also. Please submit an SR for GCS to investigate.

To see attachments, please log in.
Posted: 6 years ago
Posted: 9 Jan 2019 11:04 EST
Aaron Bosley (abosley)
PNC
Technology Engineer Senior
PNC
US

Hello, I submitted SR on this. We identified what caused this issue and it is local issue to my application and environment. It has to do with BLOB column in DB as you guessed. We are looking for solutions to fix. Thanks.

To see attachments, please log in.
Posted: 6 years ago
Posted: 9 Jan 2019 16:48 EST
Marissa Rogers (MarissaRogers)
MOD
Principal Knowledge Management Specialist
Pegasystems Inc.
US

Please let me know the SR ID on this so that I may track for you.

Thank you!

To see attachments, please log in.
  • Preethi Ganesh Victor Arokoyu Naveed Akhter Sudha Konatham Suswagata Chakraborty

Accepted Solution

Posted: 5 years ago
Posted: 8 Mar 2019 15:14 EST
Marissa Rogers (MarissaRogers)
MOD
Principal Knowledge Management Specialist
Pegasystems Inc.
US

Upon reviewing the associated SR, the following local-change resolved this:

Restore the blob content

To see attachments, please log in.

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

Pega Collaboration Center 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