Agent message: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
search cancel

Agent message: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

book

Article ID: 248138

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

Agent wrapper.log has lot of entries of such kind of message. What are these messages ?

INFO   | jvm 1    | 2022/05/20 14:45:49.482 | 14:45:49,450 [job-12360348-jobServer-16983692-3:Get Deployment Status(P12758.F1874055.E1874087.E1874156.E1874140):REST Operation] WARN  (org.apache.commons.httpclient.HttpMethodBase:682) - Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

l

 

Environment

Release : 6.7

Component : CA RELEASE AUTOMATION CORE

Resolution

This message are logged by default when the response body extends the 1MB size. It does not affect the system's behavior. 
We can specify the http.method.response.buffer.warnlimit parameter to extend this "limit" but for now i don't see any 
strong reason to do this as you dont have wrong behavior. The fact that we have this message in the log does not mean the 
response is truncated or broken.

We have a lot of places where streams might be used instead of using getResponseBody or getResponseBodyAsString methods and 
we may create the task for further improvements but again - there is no issue in using these methods and in getting this log entries.