Hi,
As tomcat is written in Java and runs on 1.3.1 I would think that it wouldn't
make a difference. Of course, if it was compiled with 1.2.2 and there's some
extremely weird error then you might be write.
I still don't understand why ppl are getting a memory leak error. It seems to
happen on all boxes but to few ppl.
Has anyone actually traced this error to a specific area? Is it mod_jk usage
only? (works on mine) Is it OS specific(doubt it) It seems to be on both
tomcat 4.0 and 3.2. Which points toward the JDK.
Of course, you could always download the blackdown JDK (never thought I'd say
that!) and see if it works. As all JDKs must follow the same spec then it
should work fine and provide the functionality your need.
Keep me posted if you figure it out 8o)
Adam.
----
Adam Fowler
Help Desk Live Project
Information Services
University of Wales, Aberystwyth
Web guy+author on the TomcatBook Project
http://tomcatbook.sourceforge.net
e-mail: [EMAIL PROTECTED]
----
On Thursday 12 July 2001 20:12, you wrote:
> I sent out a message before in regards to my copy of
> Tomcat 4.0b5 and Sun Java 1.3.1 on a Sun Solaris box
> running Solaris 8, where Tomcat will just stop after a
> while. The only response I received was that it's
> possible the VM was buggy. Since 1.3.1 is the only
> version of Java 1.3 that Sun has available, and I need
> the support it provides, I can't do much about that if
> it's true. Is there any advantages to compiling
> Tomcat on my Sun box from scratch, rather than to just
> use the precompiled binaries? Thanks.
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail
> http://personal.mail.yahoo.com/
--
