Henri, as a work-around, is it worth me rebuilding apache with the pthread 
support to get around the unresolved symbols errors when trying to load 
mod_jk.so?

Stewart

>Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
>list-help: <mailto:[EMAIL PROTECTED]>
>list-unsubscribe: <mailto:[EMAIL PROTECTED]>
>list-post: <mailto:[EMAIL PROTECTED]>
>Delivered-To: mailing list [EMAIL PROTECTED]
>From: GOMEZ Henri <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: JNI support in mod_jk : Was: mod_jk.so kills apache 1.3.19 on tru 64 
v5.1 
>Date: Thu, 14 Jun 2001 07:59:36 +0200
>MIME-Version: 1.0
>X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
>Content-Transfer-Encoding: 8bit
>X-MIME-Autoconverted: from quoted-printable to 8bit by glory.curtin.edu.au id 
f5E5wTn10111
>
>>Henri, I've attached jni.h for you to look at.
>
>Thanks.
>
>I take a look at it. The jni.h enforce you to have _REENTRANT defined.
>If you take a look in jk_mt.h (sort of thread wrapper), you'll see
>that if _REENTRANT is defined, the wrapper consider you're running
>in a multi-thread env (like Apache 2.0) and make use of some 
>pthread call like (pthread_mutex_init, pthread_mutex_lock,...).
>
>That's why your new build failed since you've built apache with 
>pthread required.
>
>>I've noticed from the tomcat-user mailing list that I'm not 
>>the only one who's 
>>had problems getting mod_jk.so working with apache and tomcat 
>>on Tru64 UNIX. Do 
>>you have any idea why this is so? I've had no problems on my 
>>personal solaris 8 
>>machine.
>
>Solaris like many others OS didn't require the _REENTRANT defined.
>
>What I propose you it to switch to jakarta-tomcat-connector where I should
>add a switch in mod_jk to determine if you want jni support. 
>Also JF Clere as done a great job in adding autoconf support and static
>build.
>
>Another very bad hack could be to add the HPUX11GCC define and remove 
>jk_jni_worker.c from the list of source files to be compiled.
>
>Just take a look at build-hpux.sh
>
>What about having a flag in autoconf stuff to activate jni support ? 
>
>Jean-Fr�d�ric, could you add a switch to configure adding the jni flag or 
>may be better just have it disable when  --with-java-home is not set.
>
>The rules will be :
>
>- you want jni, set the java flags in configure.
>- you don't care about jni, don't set java flags in configure.
>
>Many sites use mod_jk in ajp12/ajp13 mode and didn't make use of jni.
>
>It will help many users/dev to build mod_jk on their platform (HPUX,
>TRUEUnix, OpenBSD).
>

--
Stewart Mclean
UNIX Support Group
Information Management Services
Curtin University of Technology
GPO Box U1987
Perth 6845
Ph: (08) 9266 7495
Email: [EMAIL PROTECTED]

....The manual said install Windows 98 or better.....
.........so I installed Linux!


....and yes, my password is the same as my dog's name. My dog's name is 
4%&12ab!! but I change it every week. Sure does confuse the hell out of my dog!


Reply via email to