This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Why is my Service Callout policy sometimes throwing unchecked exception "Reason: End of stream"?

Posted on 10-18-2017 04:59 AM
Not applicable
Reply posted on --/--/---- --:-- AM

I am running tests against an api with npm test. Sometimes when I run the full suite of tests, one of the service callouts fail with "Reason: End of stream" although I can see part of the response in the trace. The flow terminates with an unchecked exception and the test receives an error 500 response.

The downstream system continues to run with no issues and no errors in its log file. If I reduce the number of tests, the call succeeds.

Have anyone seen this before?

We are running a private cloud (SAP branded) version 4.17.01.01.

0 2 200
Topic Labels
0 Likes
2 REPLIES 2

Posted on --/--/---- --:-- AM
ylesyuk
New Member
Reply posted on --/--/---- --:-- AM

So far it sounds like your backend aka downstream system cannot cope with a load of your test.

"Reason: End of stream" hints that it might be a .NET application and deserialization operation involved? Is it?

0 Likes

Posted on --/--/---- --:-- AM
Not applicable
In response to ylesyuk
Reply posted on --/--/---- --:-- AM

No, actually it is an Apache Camel-based Spring Boot application and the "load" doesn't even deserve to be called that.

I've managed to reproduce the issue with a curl command, so I've removed Apigee from the equation. Thanks for the quick response.

0 Likes