Cool stuff (or maybe not so cool). The question now is it a memory leak
(likely yes)...and is the leak caused by the container or by Daytrader.
The key now is to get a profiler on it and identify the culprit.
Maxim Berkultsev wrote:
> Hi, Jeff!
>
> With 512M of heap Geronimo has stopped responding in three hours under
> the same initial workload conditions. The console has indicated OOM.
>
> --
> Best regards,
> Maxim Berkultsev, Intel Middleware Products Division
>
>
> 2006/3/29, Jeff Genender wrote:
>
> Did you try upping the memory? Set your environment JAVA_OPTS to:
>
> "-Xms512M -Xmx512M"
>
> Maxim Berkultsev wrote:
> > Hi, all!
> >
> > I'm trying to make some performance evaluations of Geronimo with a
> help
> > of JMeter.
> >
> > It has appeared relatively simple to get Geronimo out of work. I've
> > tried to load it with JMeter and a web primitive called
> > **PingServlet2MDBQueue** from Daytrader bundle. I've created immediate
> > load for 10 virtual users and unlimited number of requests. Within a
> > minute or two Geronimo stopped responding to any request logging to
> > console something like
> >
> > ...
> > 18:32:56,180 WARN [ThreadedServer] EXCEPTION
> > java.lang.OutOfMemoryError
> > 18:32:57,211 WARN [ThreadedServer] EXCEPTION
> > java.lang.OutOfMemoryError
> > ...
> >
> > Has someone used any specific VM options to run Geronimo smoothly? (As
> > for me I've tried starting Geronimo with Java 1.4.2 Hotspot(TM) VM
> with
> > -server option enabled).
> >
> > Any advice or reference could be helpful. Thank you.
> >
> > --
> > Best regards,
> > Maxim Berkultsev, Intel Middleware Products Division
>
|