On Thu, May 12, 2011 at 4:23 AM, Ben Caradoc-Davies <[email protected]> wrote: > Hari's full logs are too large for the list, so I have included some > excepts of the geoserver, catalina, and localhost logs. Ideas, anyone? > > > The geoserver log contains hundreds of these: > > 11 May 04:02:17 INFO [geoserver.ows] - Problem writing exception > information back to calling client: > ClientAbortException: java.net.SocketException: Broken pipe > at
This is a client shutting down the connection in GS face. Nothing to worry about (indeed it is reported just at INFO level, not warn or error) > 10-May-2011 09:27:25.987 SEVERE > org.apache.catalina.connector.CoyoteAdapter.service An exception or > error occurred in the container during the request processing > java.lang.IllegalStateException: Cannot call sendRedirect() after the > response has been committed > at > org.apache.catalina.connector.Response.sendRedirect(Response.java:1331) > at > org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:509) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:296) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:409) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > This one might have some merit, thought only the GUI uses redirects afaik, so not a concern for services. > localhost log contains: > > 10-May-2011 09:27:31.272 SEVERE > org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() > for servlet dispatcher threw exception > java.lang.IllegalStateException > at > org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:435) > at > javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:126) > at Same as before, a failing redirect, but not sure why. None of these error are patologic. If the GS was not responding at some point and then started responding afterwards it might just be sign of an overload, too much requests in parallel for the connection pool to handle them in parallel, maybe some of them very long lived and were keeping the connections busy for a long time. If this is the case it's more a case of dimensioning the connection pool according to the load one wants to handle, setting the service limits accordingly, and using control-flow to make sure GeoServer does not try to bite more than it can chew. Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
