How to fix java net SocketException Broken pipe

Question

I am using apache commons http client to call url using post method to post the parameters and it is throwing the below error rarely    java net SocketException  Broken pipe         at java net SocketOutputStream socketWrite0 Native Method          at java net SocketOutputStream socketWrite SocketOutputStream java 92          at java net SocketOutputStream write SocketOutputStream java 136          at java io BufferedOutputStream write BufferedOutputStream java 105          at java io FilterOutputStream write FilterOutputStream java 80          at org apache commons httpclient methods ByteArrayRequestEntity writeRequest ByteArrayRequestEntity java 90          at org apache commons httpclient methods EntityEnclosingMethod writeRequestBody EntityEnclosingMethod java 499          at org apache commons httpclient HttpMethodBase writeRequest HttpMethodBase java 2114          at org apache commons httpclient HttpMethodBase execute HttpMethodBase java 1096          at org apache commons httpclient HttpMethodDirector executeWithRetry HttpMethodDirector java 398    Can someone suggest what is causing this Exception and how to debug it

User · Answer

SocketException  Broken pipe  is caused by the  other end   The client or the server  closing the connection while your code is either reading from or writing to the connection   This is a very common exception in client server applications that receive traffic from clients or servers outside of the application control  For example  the client is a browser  If the browser makes an Ajax call  and or the user simply closes the page or browser  then this can effectively kill all communication unexpectedly  Basically  you will see this error any time the other end terminates their application  and you were not anticipating it   If you experience this Exception in your application  then it means you should check your code where the IO  Input Output  occurs and wrap it with a try catch block to catch this IOException  It is then  up to you to decide how you want to handle this semi-valid situation   In your case  the earliest place where you still have control is the call to HttpMethodDirector executeWithRetry - So ensure that call is wrapped with the try catch block  and handle it how you see fit   I would strongly advise against logging SocketException-Broken Pipe specific errors at anything other than debug trace levels  Else  this can be used as a form of DOS  Denial Of Service  attack by filling up the logs  Try and harden and negative-test your application for this common scenario

User · Answer

All the open streams  amp  connections need to be properly closed  so the next time we try to use the urlConnection object  it does not throw an error  As an example  the following code change fixed the error for me   Before   OutputStream out   new BufferedOutputStream urlConnection getOutputStream     BufferedWriter bw   new BufferedWriter new OutputStreamWriter out    bw write  Some text    bw close    out close      After   OutputStream os   urlConnection getOutputStream    OutputStream out   new BufferedOutputStream os   BufferedWriter bw   new BufferedWriter new OutputStreamWriter out    bw write  Some text    bw close    out close    os close       This is a must

User · Answer

The above answers illustrate the reason for this java net SocketException  Broken pipe  the other end closed the connection  I would like to share experience what happened when I encountered it    in a client s request  the Content-Type header is mistakenly set larger than request body actually is  in fact there was no body at all  the bottom service in tomcat socket was waiting for that sized body data  http is on TCP which ensures delivery by encapsulating and      when 60 seconds expired  tomcat throws time out exception   Servlet service   for servlet  dispatcherServlet  in context with path    threw exception java net SocketTimeoutException  null client receives a response with status code 500 because of the timeout exception  client close connection  because it receives response   tomcat throws java net SocketException  Broken pipe because client closed it    Sometimes  tomcat does not throw broken pip exception  because timeout exception close the connection  why such a difference is confusing me too

User · Answer

In our case we experienced this while performing a load test on our app server   The issue turned out that we need to add additional memory to our JVM because it was running out   This resolved the issue   Try increasing the memory available to the JVM and or monitor the memory usage when you get those errors

User · Answer

I noticed I was using the incorrect HTTP request url while making it  later which i changed that it resolved my problem  my upload url was   http   192 168 0 31 5000 uploader while i was using http   192 168 0 31 5000  that was a get call  and got a java net SocketException  Broken pipe  exception  That was my reason  might lead you to check one more point when this issue   public void postRequest                Security insertProviderAt Conscrypt newProvider    1            System out println  quot mediafilename-- gt  gt  quot    mediaFileName           String   dirarray   mediaFileName split  quot   quot            String file name   dirarray 6             Thread sleep 10000            RequestBody requestBody   new MultipartBody Builder                        setType MultipartBody FORM                       addFormDataPart  quot file quot  file name  RequestBody create MediaType parse  quot video mp4 quot    new File mediaFileName    build            OkHttpClient okHttpClient   new OkHttpClient              ExecutorService executor   newFixedThreadPool 20             Request request   new Request Builder   post requestBody  url  quot https   192 168 0 31 5000 uploader quot   build            Request request   new Request Builder   url  quot http   192 168 0 31 5000 uploader quot   post requestBody  build              Request request   new Request Builder   url  quot http   192 168 0 31 5000 quot   build            okHttpClient newCall request  enqueue new Callback                  Override             public void onFailure  NotNull Call call   NotNull IOException e                         call cancel                     runOnUiThread new Runnable                          Override                     public void run                             Toast makeText getApplicationContext    quot Something went wrong  quot     quot   quot   Toast LENGTH SHORT  show                                                               e printStackTrace                                 Override             public void onResponse  NotNull Call call   NotNull Response response  throws IOException                     runOnUiThread new Runnable                          Override                     public void run                              try                               System out println response body   string                               catch  IOException e                                e printStackTrace                                                                                          System out println  quot Response    quot    response body   toString                       Toast makeText getApplicationContext    response body   toString   Toast LENGTH LONG  show                    System out println response

User · Answer

I have implemented data downloading functionality through FTP server and found the same exception there too while resuming that download  To resolve this exception  you will always have to disconnect from the previous session and create new instance of the Client and new connection with the server  This same approach could be helpful for HTTPClient too

User · Answer

I d the same problem while I was developing a simple Java application that listens on a specific TCP  Usually  I had no problem  but when I run some stress test I noticed that some connection broke with error socket write exception   After Investigation I found a solution that solves my problem  I know this question is quite old  but I prefer to share my solution  someone can find it useful   The problem was on ServerSocket creation  I read from Javadoc there is a default limit of 50 pending sockets  If you try opening another connection  these will be refused  The solution consist simply in change this default configuration at server side  In the following case  I create a Socket server that listen at TCP port 10 000 and accept max 200 pending sockets   new Thread    - gt          try  ServerSocket serverSocket   new ServerSocket 10 000  200             logger info  Server starts listening on TCP port      port            while  true              try               ClientHandler clientHandler   clientHandlerProvider getObject serverSocket accept    this               executor execute clientHandler  start               catch  Exception e                logger error e getMessage                                    catch  IOException   SecurityException   IllegalArgumentException e            logger error  Could not open server on TCP port     Reason       port  e getMessage                    start      From Javadoc of ServerSocket      The maximum queue length for incoming connection indications  a request to connect  is set to the backlog parameter  If a connection indication arrives when the queue is full  the connection is refused

User · Answer

This is caused by    most usually  writing to a connection when the other end has already closed it  less usually  the peer closing the connection without reading all the data that is already pending at his end    So in both cases you have a poorly defined or implemented application protocol   There is a third reason which I will not document here but which involves the peer taking deliberate action to reset rather than properly close the connection

User · Answer

The cause is that the remote peer closes its socket  crash for example   so if you try to write data to him for example  you will get this  to solve that  protect read write to socket operations between  try catch   then manage the lose connection case into the catch  renew connection  stop program     etc     try            your code       catch  SocketException e          e printStackTrace             insert your failure processings here

User · Answer

The issue could be that your deployed files are not updated with the correct RMI methods  Check to see that your RMI interface has updated parameters  or updated data structures that your client does not have  Or that your RMI client has no parameters that differ from what your server version has   This is just an educated guess  After re-deploying my server application s class files and re-testing  the problem of  Broken pipe  went away

User · Answer

JavaDoc       The maximum queue length for incoming connection indications  a   request to connect  is set to 50  If a connection indication arrives   when the queue is full  the connection is refused    You should increase  backlog  parameter of your ServerSocket  for example  int backlogSize   50   new ServerSocket port  backlogSize

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

Examples related to java

Examples related to exception

Examples related to post

Examples related to sockets