Douglas Ferguson <douglas <at> douglasferguson.us> writes:
>
> I will definitely share my findings. I saw 400% CPU (we have 4 proc box),
> the other day!
>
> What debugging approach are you taking?
>
> Douglas
>
I've tried a couple monitoring tools for Tomcat, but they where too
intrusive (required installation on the server). There was one in particular
that only required configuring Java for JMX (Management Extensions) but I had to
do other things and I will get into it in a few days I hope.
My suspicion is that the problem can be memory leaks in the library we use
to access the database. It was withdrawn from sourceforge recently and I plan to
change it to something else.
For your interest, I can tell you that the response and performance greatly
improved when I changed the model for a couple of data tables to
LoadableDetachableModel.
This is our first Java web app so a lot of inexperience with all the tools,
but Tomcat not only get stuck to 30-80% CPU from time to time but it even
crashes sometimes, I'm afraid I'm missing some obvious configuration.
Cheers,
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
