mturk 2002/08/16 01:20:28
Modified: jk/conf jk2.properties
Log:
To be able to use the jni inside the jk2.properties you will need at least
one channelJni directive. It can be anything (even channelJni.foo=bar).
This can be either bug (cause the directives are not checked), or feature
meaning that you need at least one directive to enable the channel itself.
Also IMO we should promote the 'inprocess' as a favorite option for using JNI,
and making LoadLibray from Java as depriciated.
Revision Changes Path
1.10 +8 -0 jakarta-tomcat-connectors/jk/conf/jk2.properties
Index: jk2.properties
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/conf/jk2.properties,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- jk2.properties 9 Aug 2002 17:36:17 -0000 1.9
+++ jk2.properties 16 Aug 2002 08:20:28 -0000 1.10
@@ -12,4 +12,12 @@
# Just to check if the the config is working
# shm.file=${jkHome}/work/jk2.shm
+# In order to enable jni use any channelJni directive
+# channelJni.disabled = 0
+# And one of the following directives:
+
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
+
+# If set to inprocess the mod_jk2 will Register natives itself
+# This will enable the starting of the Tomcat from mod_jk2
+# apr.jniModeSo=inprocess
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
