You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Peter H." <co...@hotmail.com> on 2003/04/03 17:08:57 UTC
Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess
Hello,
Does someone use IBM JDK 1.4 with tomcat 4.1.24 and apache 2.0.44
Can't startup JVM exit -1 message...
Compiled jni*.so and
maybe its the problem because the ././classic/jvm*.so is used?
I thought jdk1.4 stops supporting classic jvm...
Greetings and thanks
Peter
_________________________________________________________________
Fotos - MSN Fotos das virtuelle Fotoalbum. Allen Freunden zeigen oder
einfach online entwickeln lassen:
http://photos.msn.de/support/worldwide.aspx
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess
Posted by Michael Crozier <cr...@conducivetech.com>.
And you should upgrade to apache 2.0.45 anyways, since there is apparently a
un-announced security problem that was fixed.
On Thursday 03 April 2003 07:45 am, Richard Dunn wrote:
> On Thursday 03 April 2003 08:08, Peter H. wrote:
> > Hello,
> >
> > Does someone use IBM JDK 1.4 with tomcat 4.1.24 and apache 2.0.44
> > Can't startup JVM exit -1 message...
>
> I tried this setup a couple days ago (on Redhat 8.0) and it worked fine,
> but I am using the mod_jk.so connector. I have not tried the JNI approach.
> I did notice my applications ran much slower than under the Sun 1.4.1 (both
> _01 and _02 versions) so I went back to the Sun jdk (despite reports of
> StringBuffer related memory leaks).
>
> I am now on the Apache 2.0.45 and it is working fine.
>
> > Compiled jni*.so and
> >
> > maybe its the problem because the ././classic/jvm*.so is used?
> > I thought jdk1.4 stops supporting classic jvm...
> >
> >
> > Greetings and thanks
> > Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
--
Michael Crozier
Conducive Technology Corporation
First we were Sight & Sound,
then we were Datalex,
and temporarily Framework Technology.
<http://www.conducivetech.com>
Michael Crozier, crozierm@conducivetech.com
Voice: 503.445.4233
Fax: 503.274.0939
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess
Posted by Richard Dunn <ri...@arkona.com>.
On Thursday 03 April 2003 08:08, Peter H. wrote:
> Hello,
>
> Does someone use IBM JDK 1.4 with tomcat 4.1.24 and apache 2.0.44
> Can't startup JVM exit -1 message...
I tried this setup a couple days ago (on Redhat 8.0) and it worked fine, but I
am using the mod_jk.so connector. I have not tried the JNI approach. I did
notice my applications ran much slower than under the Sun 1.4.1 (both _01 and
_02 versions) so I went back to the Sun jdk (despite reports of StringBuffer
related memory leaks).
I am now on the Apache 2.0.45 and it is working fine.
>
> Compiled jni*.so and
>
> maybe its the problem because the ././classic/jvm*.so is used?
> I thought jdk1.4 stops supporting classic jvm...
>
>
> Greetings and thanks
> Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org