I just did some memory profiling. I started jetty server (5.1.3)
running Cayenne service, and sent a constant stream of client
requests, each one inserting 500 new objects. Once an equilibrium was
reached between session termination and session creation, the heap
memory peaked and would not grow further. Then I stopped the client
requests and all remaining sessions were eventually terminated. At
this point the heap memory dropped back to a very low value (~ 2.4 Mb).
So I am fairly certain that the service doesn't leak. You can email
me privately if you need help with your app - there has to be
something app-specific.
Ok, I am going offline for tonight...
Andrus
On May 21, 2006, at 11:47 PM, Andrus Adamchik wrote:
I don't embed it in an application per se, but I would imagine
there is no difference in a general case (when the rest of your app
doesn't maintain references to the things inside web app context).
Andrus
On May 21, 2006, at 11:29 PM, Marcin Skladaniec wrote:
Andrus are you testing on embedded jetty ? We are, and I start to
think that it might be it causing the problem.
Marcin
On 22/05/2006, at 1:11 PM, Andrus Adamchik wrote:
On May 21, 2006, at 10:59 PM, Marek Wawrzyczny wrote:
Thanks, we do have a much simpler test application that
experiences the same
behaviour.Coincidently, which version of Jetty are you using?
I've done most of the testing with Jetty 5.1.3. A few days ago I
switched to 6.0 Beta (as it has a nifty Maven plugin that starts
your container with all dependencies from pom) - don't have much
data for 6.0 yet.
Andrus
