After migration from jboss to spring-boot 2.0.6 I got a rare reproduce problem with some SOAP web services. Sometimes when application get a huge response from another server and try to forward to client the following exception is occurred: java.io.IOException: Broken pipe.
It doesn't connect with timeout or problem with size of header, I've checked it. So I don't understand what can be a reason else.
Version of cxf 3.1.6
This usually is because of an infarction against the transport protocol.
I didn't look into your trace but if this is SOAP over TCP, the TCP protocol wasn't adhered to and one of the parties stopped the connection due to that and raised this exception.
Question: is this reproducible or happens sometimes?
Typically this could be:
1. Client or Server are shutting down too fast. Like, Server provides response and stops the connection rather than complete the protocol and shutdown properly.
2. Internet is unstable.
Try to put some delays around the program, see if this helps. The delays should give the parties enough time to finish the transfer.
Then you need to figure out if you implemented the protocol correctly, or you need better internet, or something else is wrong.
Diagnosed with autism. Please excuse me if I miscommunicated anything.
@Negar Zamiri, May I know How the problem was solved by Increasing the Buffer size?
I am eagarly Know about that. Could you please give the ans for this?
posted 8 months ago
Welcome to the Ranch
NZ hasn't posted here since that one post, so you might not get a reply, I am afraid. Have you read that SO link, although it was downvoted quite badly and might therefore not be helpful? Sorry not to be able to give you anything better.
Everybody's invited. Except this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop