On Tue, 22 Jan 2002, Dan Diodati wrote: > The main reason that we wanted to change to tomcat 3.3 is for the > hierarchical classloading support. > I guess we'll have to wait.
If your VM is crashing with 3.3a ( or anything else !) - you should fix the vm. No combination of java bytecodes should be able to break the VM - if it happens with some 3.3 bytecode it may happen with some random user code as well, in the midle of the night on the production server. A vm that crashes on any java program is _bad_, and adding workarounds in the java program is the worse solution since it hides a _critical_ problem in the system. I wouldn't wait... Be happy you found about the problem, and look for OS patches/newer or older VMs, etc until you get a vm that is stable. > Of course, there is always the issue that there is absolutely no need to run > 3.3a on a Solaris box (which is why I really can't be bothered to download > it to check this out, since my primary production environment is Solaris). The issue is that the VM is crashing when running a valid java program - period. If something in 3.3a is causing this - same thing may happen when you run some code in one of yours webapps or libs or anything - at a random time, eventually corupting data and taking down a production server. Costin > If you're not running Windows, than there is no advantage to using 3.3a over > 3.3.0. There are lots of advantages to using 3.3.1-dev (aka nightly, soon > to be 3.3.1-B1) reguardless of the OS. see: > http://cvs.apache.org/viewcvs/jakarta-tomcat/RELEASE-NOTES-3.3.1.txt > > ----- Original Message ----- > From: "Bojan Smojver" <[EMAIL PROTECTED]> > To: "Tomcat Developers List" <[EMAIL PROTECTED]> > Sent: Monday, January 21, 2002 6:15 PM > Subject: RE: jdk1.3.1 and tomcat 3.3a core dumping? > > > > Quoting Dan Diodati <[EMAIL PROTECTED]>: > > > > > > > > I don't think the java code has any issues because it has been in > > > production > > > with jdk1.2.2 and tomcat 3.2.4. > > > > Maybe I wasn't clear enough. The point is that this is a JVM issue, it has > > nothing to do with Java classes you run on it (except that some of them > might > > trigger a particular bug within the JVM). > > > > > I tried using tomcat 3.2.4 and jdk 1.3.1_02 it this issue does NOT > > > occur, > > > making me suspicious of > > > tomcat 3.3a. > > > > As above. > > > > Bojan > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
