pjrosello's account

Hi Duo, 

Many thanks for the answer - unfortunately our Camel route does work around 95% of the times, but from time to time it throws the SocketException (connection reset by peer) so I was wondering if there's any particular configuration we have to set up like SSL, TSL, etc that you guys might be aware of? 

Best,

Pedro

We're filtering out the header "keep-alive" before we send the request - do you think this might have something to do with it?

Pedro

Hi Duo,

We don't have a custom socket configuration; in fact, we call the endpoint in a very similar fashion to your first response. 

We've tried not filtering out the "keep-alive" header but the problem persist. The only pattern we see is that when we haven't made any requests in some time (for example around 20 minutes), then we make a new request it'll throw the exception. It's almost as if the connection is closed whenever there's no traffic and when we try to open it again we get the connection closed by peer exception. Is there a way to bypass this?

Pedro

Hi Duo,

Many thanks for your continuous effort! 

Our situation is indeed very similar to your last example, and it's slightly reassuring that you're able to reproduce it. The flow at the moment looks like

User (e.g Postman) -> Spring Boot Application (Camel) -> OSS.

So is your suggestion that the issue could lie in User -> Spring Boot and not in Spring Boot -> OSS?

Pedro

Hi Duo,

Many thanks for your continuous effort! 

Our situation is indeed very similar to your last example, and it's slightly reassuring that you're able to reproduce it. The flow at the moment looks like

User (e.g Postman) -> Spring Boot Application (Camel) -> OSS.

So is your suggestion that the issue could lie in User -> Spring Boot and not in Spring Boot -> OSS?

Pedro