ansaurus

Question

How to fix java.net.SocketException: Broken pipe ?

Answer 1

A:

I'm not sure that this is the case, but I got something similar when I transferred objects (through object streams) too often. As I remember, 15-20 calls per seconds were enough to overload pipes and exception was thrown (something like 'ObjectStream corrupted').

The only solution I found was to reduce number of calls due to enlarging amount of data transferred per one call.

Roman 2010-02-22 08:40:50

'ObjectStream corrupted' would only occur if your application corrupted it. It isn't a function of load. Neither is this thread.

EJP 2010-02-22 09:13:59

Believe me, I spent about a month and almost was banned at google before found suitable solution.

Roman 2010-02-22 09:45:42

Read this article for more info http://www.javamex.com/tutorials/io/StreamCorruptedException.shtml. In nutshell: we have some maximum capacity, let's assume 10 calls per second. When we want to make 20 calls we get huge problem.

Roman 2010-02-22 09:55:09

@Roman - how does the the linked article describe your problem? I don't see the connection.

Stephen C 2010-02-22 10:08:47

@Stephen C: I actually don't have any problem, it was solved more than a year ago. Text in the beginning of the article describes my former problem a little. Let's stop this discussion, please.

Roman 2010-02-22 10:56:20

Answer 2

+1 A:

This is caused by writing to a connection when the other end has already closed it.

So you have a poorly defined or implemented application protocol.

EJP 2010-02-22 09:13:02

Can you please help me to identify and correct it? Basically, how to confirm the reason and fix?

Mani 2010-02-22 10:33:41

I *have* confirmed the reason. You are writing while the other end has already closed the connection. The fix is not to do that. As the other end isn't reading it, there isn't any point anyway. As I also said, if this is happening there is something wrong with your application protocol specification or implementation, most probably that you don't even have one.

EJP 2010-02-22 22:33:36

Thanks. Server side app has been implemented using HTTP protocol. It is running under tomcat. Am I doing any mistake in specifying headers? Also, Is it possible to identify whether the other end has already closed the connection in the client side code?

Mani 2010-02-23 07:52:07

If the server side HTTP application is getting Broken Pipe exceptions it just means the client browser has exited/gone to another page/timed out/gone back in the history/whatever. Just forget about it.

EJP 2010-02-23 11:20:49

In my case, it is happening in client side only.

Mani 2010-02-25 06:44:46

So the *server* is closing the connection early. You're probably sending it something invalid.

EJP 2010-02-25 12:54:17

ansaurus

tags:

views:

answers:

How to fix java.net.SocketException: Broken pipe ?

related questions