Howdy, If your OS requires patches in order to run the JDK (whatever version you're trying to run), make sure those patches are installed. I had this exact issue happen on Solaris, and installing the proper Solaris patches made it go away.
You say "The same behavior can be reproduced with both JDK1.4.0 and JDK1.4.1" and yet "I cannot create a test case to reproduce my problem." Which one is it? ;) If you can reproduce it, the full details of how to reproduce it can be posted to Sun's bug parade, and they'll track down whatever tools they need in order to mimic your environment. If you can't reproduce it, there's no bug as far as they're concerned. Finally, I'm not sure I understand this bullet: >- I works fine with TC4.1 So your app works fine on TC 4.1? I thought that was the whole problem? Or did you mean it works fine with TC 4.0 and not 4.1? If it's the latter, as I suspect, perhaps you could start by deploying a very small subset of your app and repeating the test. Then increase the deployed subset and retest. The idea is that a certain feature of tomcat as used by your app is crashing the VM, and to find out which section of your app is causing this. The more you can narrow it down, the better. Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
