AnsweredAssumed Answered

Why does the use of Message Streaming assertion still utilize disk/memory space?

Question asked by robbiej on Jul 26, 2017
Latest reply on Aug 13, 2017 by Stephen_Hughes

We are trying to allow large response payloads for a REST service. After looking at Configure Message Streaming Assertion and Streaming large files through API Gateway the service was configured to allow unlimited response size with streaming enabled (no buffering). In testing, we discovered, large responses still buffered and written to disk at <SSG>/node/default/var/attachments/. In simple tests, the file-system quickly filled and caused "java.io.IOException: No space left on device" to be thrown, the connection to be terminated, and the ssg to send 500s. My assumption was that streaming would send the data to the client as it receives it without buffering on heap or disk. Is that assumption incorrect or is the policy/gateway configured improperly?

Attachments

Outcomes