• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Broken Pipeline in Tomcat

Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Guys,

We are running around 50 apps on Apache Tomcat/7.0.57, all are client API accessible via SOAP call. The problem we are facing is that we are getting broken pipeline error (ClientAbortException). Now I assume I cannot avoid this issue completely, the problem I am facing is the server is not recovering from this issue. It starts giving the error in a series. I need to restart the service/server to rectify the issue, that is not a very good idea for live servers.

Tomcat is running with these parameters:

And the error log is as follows:

Please let me know if anyone needs any more information to help me rectify this.
Ranch Hand
Posts: 808
Android Eclipse IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My guess is that the HTTP connections are pooled and reused and the software is not able to detect the broken connections.

According to https://axis.apache.org/axis2/java/core/docs/http-transport.html

CommonsHTTPTransportSender utilizes HttpClient. Here you have some configuration description:



given that you use MultiThreadedHttpConnectionManager. Anyhow, make sure that Stale Connection check is activated:

http://hc.apache.org/httpclient-3.x/preference-api.html -> http.connection.stalecheck

You will probably need to configure HttpClient through Axis interface.
Shubh Bose
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually, This exception cause a request long time to process, which will make other subsequent requests to be in queue, then they will take more time to process and execute, Later at one point, all request takes more time to process, which hang up the service and further on there are only "Broken Pipe" error exception in the logs.
bacon. tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic