Hello Andrea, i think i race exactly this behavior with 100% constantly due to a bug in the JVM described in GEOS-3873 issue track.
I run GeoServer 1.7.5 with JDK 1.6.0_06 and for a week i had this problem. The java process had 100% percent cpu consumption and could only be bing back to normal state by a restart. I had read the Jetty issue track: http://jira.codehaus.org/browse/JETTY-937 and it seems to going on right my behavior. Question is, how can i use the upgrade.patch distributed in GEOS-3873 issue track? A upgrad of Jetty from version 6.1.8 to 6.1.24 will fix this bug, but i don't know how i have to handle with this patch discrition. Thank for reply and best wishes, Lg 2StepForward -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/jira-Created-GEOS-3873-GeoServer-binary-distribution-might-use-100-constantly-due-to-a-bug-in-the-JVM-tp6128411p6286892.html Sent from the GeoServer - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
