Thanks for the feedback.
When I ran my load tests I used -Xmx512m -Xms512m as heap settings.
I also tried increasing or decreasing it but it didn't change the
results.
I am running on Solaris and I have all the recommended patches for
JDK1.4.1 installed.
I can reproduce the problem: it is always crashing during the test,
but it can be after 2 minutes or 20 minutes depending on the run.
My problem is that I cannot create a simple test case that will crash
the
server because of the complexity of our environment ( it includes multiples
Oracle databases and LDAP connectivity).
I tried to isolate the problem to a single jsp like you recommend
it but that didn't work.
(I could fine several combinations that would trigger the crash).
So I am not sure what I could provide as a test case except our full dev
environment.
I can deploy the same application on TC4.0.4 and it runs fine. I tried many
versions
of Tomcat 4.1 (4.1.7, 4.1.12, 4.1.14 and 4.1.16) and are all failing.
I attached the VM log.
Thanks,
Aymeric
>>> [EMAIL PROTECTED] 12/10/02 04:48PM >>>
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]>
hs_err_pid13559.log
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>