Hi all, I've got a problem, my web application works just fine, untill I start stress testing it. I click on the same link 2,3,more times. All of the pages are havily acessing castor objetcs. Everything works fine for a while, then (I could not determine what the conditions are)the CPU starts spinning at 100%, and the JVM starts eating up memory untill it dies.
There are no error messages written in the log. The application is still functional when that happens, it just becomes very slow and eventually dies. I have no clue where to start with this one. I actually tries some profiling tools, but they are so slow. I'm expecting that the unswer will be 'it might be something else but castor', well, never happenes when I'm doing the same thing on pages that are not accessing castor objects. Any thought, sugestions? I'm using jboss3.0.0 with jetty and castor-0.9.3.9. Thanks... P.S. Also, what is org.exolab.castor.debug=true in castor.properties? I tried to change it and put the file on my class path, didn't seem to have any effect, so would it be possible to see if it's really castor that's eating up the memory and the cpu? Where does the file go? Is there anything else to do to make it work? _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
