----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Steve-
> But it works flawlessly with JServ 1.1b3
The reason for this probably stems from improvements/fixes applied to
the JServ Java code. However, at no time should the JVM crash; if there
is any problem the JVM should throw and Exception and either continue or
exit normally. While it may be true that a code change between 1.1b3
and 1.1 is responsable for the new behavior, it is an error in the JVM
coding that is actually causing the problem.
Therefore, since its highly unlikely that anyone here is going to roll
back improvements/fixes because of errors in JVM coding, your best bet
would probably be to report the problem (stack dump does no one any
good, btw - you need to track down the exact code) to the respective JVM
vendors and either hope that they eventually respond or just go with
whatever JVM works. Until that time I'd stick with 1.1b3 and start
taking a look at Tomcat and Jakarta.
- MG
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
