-
15. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
The application I'm working on has no EJB, JNDI, etc. It's simply a Struts based app using JSP, a servlet, and beans.
It's interesting that both jboss with jetty and jboss with tomcat both core.
We spent the afternoon doing load tests on Tomcat without any crashes. The bad news is we need to commit to a product for production this week and I will have to go with Tomcat if I can't resolve this issue.
That's dissapointing for me since I've pushed open source products at this company for over 7 years and we are finaly putting an open source into a production environment. I want JBoss! -
16. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
Well we did the rebuild of 3.0.3 under jdk 1.4 (unfortunately we DIDNT use 1.4.1 but 1.4.0.01) but with the same result. Occassional hotspot errors, but generally the jvm simply stop running. The servers stay up all night under light load but when it gets heavy they only stay up for about an hour.
One odd thing we do see occasionally when the server dies is a message saying that the windows 2000 event log is full. When we go to empty the log there is little activity in it!?
Here's the hotspot output:
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Server VM (1.4.0_01-b03 mixed mode)
#
# Error ID: 47454E45524154452F4F502D41500E4350500848
#
# Problematic Thread: prio=5 tid=0x1FD0A440 nid=0xd28 runnable
#
Press any key to continue . . .
I'm downloading 3.2 now to build and try tomorrow... -
17. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
During testing I noticed something interesting. If I use the -server option when running Tomcat, I get a core dump pretty quick. This also leads me to believe that there is something wrong in the JVM. I just wish I knew of a work around for now.
-
18. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
In that case make sure your script (run.sh) does not add the -server option to the JVM. Seems the server side hotspot jitter is buggy.
-
19. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
What is very confusing is that JBoss will run longer with the -server options than without, but Tomcat will crash very quickly with the -server, and not at all without.
I'm very confused at this point. We are moving forward with Tomcat in hopes that by the next deployment we will be able to replace it with JBoss(jetty).
Thanks all for your input. -
20. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
Do you run it as a service on Windows or from bat file?
I have noticed that I can run it without any problems when run from the bat file but when run it as a service under JavaService it crushes under load. -
21. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
We have been experiencing this exact description running jBoss 3.2 beta distro on a 1.3.1_03 JVM. We are going to do a build as recommended on the target platform and see where we get to. This is a vexing problem, we have only today started getting core files.
-
22. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
Hi,
We were getting a similar problem. However in our case it was related to using the -server option. Without using this option JBoss seems to run fine.
Kam -
23. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
This problem has been reported at www.javasoft.com under the bug id: 4724356. It appears to occur in VMs from 1.3.1 up. The bug is open many are having trouble reproducing the error but it holds many of the symptoms that we have all reported so far.
-
-
-
26. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
Well, we had to switch to Tomcat 4.1.12 :(
The product goes into production tonight. I hope the issue is resolved before we need the functionality that JBoss provides. -
27. Re: JBoss 3.0.3(jetty) jvm (1.4.0/1.4.1) crash on Solaris/Wi
I just tried our app with JBoss/Jetty 3.2B2.
With the -server option it core dumps within about 150 hits.
I sure wish Sun would fix this, or someone would figure out a work around in JBoss.