It probably has to do with the memory issue - in devlopement time new
classes are generated every time you restart the webapp. Class objects
are not being collected as garbage, also when not in use, resulting in a
huge class-definition.
This is an issue in dev-time, should not differ on production.
Look at the mailing list under "memory", there are some threads about
that...
ציטוט Lukasz Kucharski:
I have a pretty strange problem with Tomcat and I don't know what's
causing it. Maybe some of you can help me out with this.
There are only two frameworks I use in my web app - Hibernate and
Tapestry. Problem is that after a few requests (20-30 requests) tomcat
gets more and more cpu time to actually preform request. It is clearly
visible in my log files when messages are being written slower and
slower. In the end even simple initialization of Class takes ages to
finally stop responding.
I didn't figure out what's causing this problem yet . I close my
sessions properly - that I'm sure of - I use thread local pattern. My
webapp work in reloadable mode - i use
-Dorg.apache.tapestry.disable-caching=true
and reloadable in tomcat configuration set to true.
Has anyone got a clue?
Thanks in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
