DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17762>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17762 runtime link error loading jkjni.so ------- Additional Comments From [EMAIL PROTECTED] 2003-06-19 21:34 ------- After exploring the dependencies a bit, I came up with the following: To build apr and aprutil with the proper dependencies, LDFLAGS was set to the following: export LDFLAGS="-lgdbm -lldap -lexpat -ldb" Apache 2.0.46 was then built to create apr and aprutil. ldd on the two libraries is shown below. ldd /home/apache/lib/libapr-0.so.0.9.4 libdb-4.0.so => /lib/libdb-4.0.so (0x40036000) libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x400de000) libldap.so.2 => /usr/lib/libldap.so.2 (0x400e5000) libexpat.so.0 => /usr/lib/libexpat.so.0 (0x40111000) libc.so.6 => /lib/tls/libc.so.6 (0x42000000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40131000) libsasl.so.7 => /usr/lib/libsasl.so.7 (0x4013f000) libssl.so.4 => /lib/libssl.so.4 (0x4014a000) libcrypto.so.4 => /lib/libcrypto.so.4 (0x4017f000) liblber.so.2 => /usr/lib/liblber.so.2 (0x40271000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) libdl.so.2 => /lib/libdl.so.2 (0x4027c000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x40280000) libpam.so.0 => /lib/libpam.so.0 (0x402ad000) libresolv.so.2 => /lib/libresolv.so.2 (0x402b5000) libgssapi_krb5.so.2 => /usr/kerberos/lib/libgssapi_krb5.so.2(0x402c7000) libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0x402db000) libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3 (0x40339000) libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3 (0x40349000) libz.so.1 => /usr/lib/libz.so.1 (0x4034b000) ldd /home/apache/lib/libaprutil-0.so.0.9.4 libdb-4.0.so => /lib/libdb-4.0.so (0x4002d000) libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x400d5000) libldap.so.2 => /usr/lib/libldap.so.2 (0x400dc000) libexpat.so.0 => /usr/lib/libexpat.so.0 (0x40108000) libc.so.6 => /lib/tls/libc.so.6 (0x42000000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40128000) libsasl.so.7 => /usr/lib/libsasl.so.7 (0x40136000) libssl.so.4 => /lib/libssl.so.4 (0x40141000) libcrypto.so.4 => /lib/libcrypto.so.4 (0x40176000) liblber.so.2 => /usr/lib/liblber.so.2 (0x40268000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) libdl.so.2 => /lib/libdl.so.2 (0x40273000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x40277000) libpam.so.0 => /lib/libpam.so.0 (0x402a4000) libresolv.so.2 => /lib/libresolv.so.2 (0x402ac000) libgssapi_krb5.so.2 => /usr/kerberos/lib/libgssapi_krb5.so.2(0x402be000) libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0x402d2000) libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3 (0x40330000) libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3 (0x40340000) libz.so.1 => /usr/lib/libz.so.1 (0x40342000) The Makefile in: jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/server/apache2 was modified so that the JK_LDFLAGS reads as follows: JK_LDFLAGS=-L${APACHE2_LIBDIR} -lcrypt -lapr-0 -laprutil-0 -lpcre -lpcreposix Creation and installation of mod_jk2.so and jkjni.so proceeded as expected. The socket connection works as expected. When an out-of-process UNIX socket was attempted, the following error occured while starting up Tomcat. INFO: Starting Coyote HTTP/1.1 on port 8080 Jun 19, 2003 2:19:05 PM org.apache.jk.server.JkMain start INFO: APR not loaded, disabling jni components: java.io.IOException: initialize Exception during startup processing java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Caused by: java.lang.UnsatisfiedLinkError: getJkEnv at org.apache.jk.apr.AprImpl.getJkEnv(Native Method) at org.apache.jk.common.JniHandler.initNative(JniHandler.java:132) at org.apache.jk.common.ChannelUn.init(ChannelUn.java:114) at org.apache.jk.server.JkMain.start(JkMain.java:351) at org.apache.jk.server.JkCoyoteHandler.start(JkCoyoteHandler.java:169) at org.apache.coyote.tomcat4.CoyoteConnector.start(CoyoteConnector.java:1141) at org.apache.catalina.core.StandardService.start(StandardService.java:506) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2190) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) ... 5 more And Tomcat dies. I guess the next thing to do is find where getJkEnv is and why it's not linked in appropriately. This appears to be more and more like a build configuration issue coupled with Redhat 9 Linux rpm locations. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]