On 25/08/2015 19:42, Matthew Madey wrote: > I use an application called Spacewalk to manage RHEL systems in an > enterprise environment. The application provides an API that I use for > automation purposes. While load starts to increase on the application > server, we reach a breaking point where the application becomes > unresponsive, and throws 500 internal server errors. Listed at the bottom > are some of the errors I see when this happens. I'm looking for advice on > how to better diagnose and\or tune my settings to optimize Tomcat > performance. I feel like the system is beefy enough to handle this load, > but Tomcat appears to be my bottleneck.. How should I go about resolving > this? I have played around with the AJP connector settings quite a bit, but > can't seem to find suitable parameters.
<snip/> > Aug 25, 2015 1:33:23 AM org.apache.jk.core.MsgContext action > WARNING: Unable to send headers > java.net.SocketException: Broken pipe Insufficient threads on the Tomcat side? How does max threads on the httpd side compare to the Tomcat side? > SEVERE: Exception initializing page context > java.lang.IllegalStateException: Cannot create a session after the response > has been committed That is an application bug. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
