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).
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]>

Reply via email to