Hello Christopher thanks for the reply >>This sounds like a memory leak. it could be, but....
>>Are you sure that you always close your connections, statements, and >>ResultSets in "finally" blocks (or are using a library that does this)? >>This is sometimes the cause of memory leaks. i work with hibernate and spring, so it is manged by them and i use too JdbcTemplate, so ResultSets is not used >>One thing you can do (if you're getting an OutOfMemoryException, which >>it sounds like you are) i had other type of exception, already resolved in the link that i wrote no exceptions i have or recieve . >>This will (at least, on the Sun JVM) give you a heap dump if you get an >>OOME. You should be able to look through that to see what types of >>objects are taking up all the space. Once you have that information, you >>can either make your own guesses or come back to us for some additional >>direction. before to work in production area, i used the thread dump in windows, and of course i saw the wonderful problem of resources not closed, already fixed now more ideas are appreciate regards Christopher Schultz-2 wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ash, > > dr_pompeii wrote: >> after to test my project in tomcat 5.5.23 and jdk 5 update 12 >> in network(intranet-only until now with 2 clients) i see that this is >> fast, >> after of a some time i can see a wonderful exception >> related with java heap exception thrown by the tomcat > > [snip] > >> ok, its works, the point is that after to restart the server, the system >> is >> fast again, >> but then again after of some time the performance go to very slow > > This sounds like a memory leak. > >> BTW: i am using pool connections related with the db area > > Are you sure that you always close your connections, statements, and > ResultSets in "finally" blocks (or are using a library that does this)? > > This is sometimes the cause of memory leaks. > > One thing you can do (if you're getting an OutOfMemoryException, which > it sounds like you are) is set this in your environment: > > JAVA_OPTS=-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp > > This will (at least, on the Sun JVM) give you a heap dump if you get an > OOME. You should be able to look through that to see what types of > objects are taking up all the space. Once you have that information, you > can either make your own guesses or come back to us for some additional > direction. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGzE409CaO5/Lv0PARAuiBAJ0QZz7Z4AhLJl6Hcb7I2s3Vt61VRACgiDYG > 5etY/5MvSa1Ww6hN1oSB/R4= > =sS9W > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/wierd-performance-in-tomcat-java%3A-help-consult-tf4311308.html#a12277145 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
