I'm seeing my Jetty stand-alone servers chew up available memory under load (-Xmx4g eventually all gets used). Based on Java Object histograms, it seems like the problem has to do with Jetty, or how I have Jetty configured. Here's the info I have:
Server: Jetty Hightide 7.0.0 (problem occurred before upgrading, tho, previously 6.1.11).
Setup: Stand-alone, running one production Java webapp: Spring 2.5, JSP
Load: ~20-250 req./second over the course of a day, distributed across three server instances on separate machines
There are no comparable/suspicious counts for my-domain-level objects. Based on a session-scoped object, there appear to be about 29K active sessions when this snapshot was taken, which seems a bit high, but not inconceivable, given our traffic type (Facebook apps). There are <100 active requests present at the time of the snapshot.
Seems like maybe old, fulfilled requests are not getting GCed and are hanging around in the idle pool? Any ideas?