You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Costin Manolache <co...@eng.sun.com> on 2000/03/29 18:31:48 UTC
Re: cvs commit: jakarta-tomcat/src/etc jni_workers.properties
jni_server.xml
Gal,
Wouldn't be simpler if you put the jni connector inside server.xml ( as a comment )
and jni_worker.properties inside worker.properties ?
An even better solution is to add a "disabled" property to connectors, and mark the jni as disabled ( in
default config). We can add an admin page later.
( as soon as we're done with this release, I want to generate worker.properties and urimaps automatically )
Just an idea...
Costin
shachor@locus.apache.org wrote:
> shachor 00/03/29 01:20:37
>
> Modified: src/etc jni_workers.properties jni_server.xml
> Log:
> Minor updates to the jni howto
>
> Revision Changes Path
> 1.2 +10 -5 jakarta-tomcat/src/etc/jni_workers.properties
>
> Index: jni_workers.properties
> ===================================================================
> RCS file: /home/cvs/jakarta-tomcat/src/etc/jni_workers.properties,v
> retrieving revision 1.1
> retrieving revision 1.2
> diff -u -r1.1 -r1.2
> --- jni_workers.properties 2000/03/25 03:35:24 1.1
> +++ jni_workers.properties 2000/03/29 09:20:36 1.2
> @@ -16,11 +16,11 @@
> #
> # Additional class path components.
> #
> -worker.jni.class_path=d:\tomcat\tomcat\classes
> -worker.jni.class_path=d:\tomcat\tomcat\lib\xml.jar
> -worker.jni.class_path=d:\tomcat\tomcat\lib\jasper.jar
> -worker.jni.class_path=d:\tomcat\tomcat\lib\servlet.jar
> -worker.jni.class_path=d:\tomcat\tomcat\lib\webserver.jar
> +worker.jni.class_path=d:\tomcat\classes
> +worker.jni.class_path=d:\tomcat\lib\xml.jar
> +worker.jni.class_path=d:\tomcat\lib\jasper.jar
> +worker.jni.class_path=d:\tomcat\lib\servlet.jar
> +worker.jni.class_path=d:\tomcat\lib\webserver.jar
> worker.jni.class_path=d:\sdk\jdk1.2.2\lib\tools.jar
> # worker.jni.class_path=d:\SQLLIB\java\db2java.zip
>
> @@ -47,6 +47,11 @@
> #
> worker.jni.stdout=d:\tomcat\jvm.stdout
> worker.jni.stderr=d:\tomcat\jvm.stderr
> +
> +#
> +# Setting the tomcat.home Java property
> +#
> +worker.jni.sysprops=tomcat.home=D:\tomcat\
>
> #
> # Java system properties
>
>
>
> 1.2 +59 -10 jakarta-tomcat/src/etc/jni_server.xml
>
> Index: jni_server.xml
> ===================================================================
> RCS file: /home/cvs/jakarta-tomcat/src/etc/jni_server.xml,v
> retrieving revision 1.1
> retrieving revision 1.2
> diff -u -r1.1 -r1.2
> --- jni_server.xml 2000/03/25 03:35:24 1.1
> +++ jni_server.xml 2000/03/29 09:20:36 1.2
> @@ -1,22 +1,71 @@
> <?xml version="1.0" encoding="ISO-8859-1"?>
>
> <Server>
> - <ContextManager port="8080" hostName="" inet="">
> + <!-- Debug low-level events in XmlMapper startup -->
> + <xmlmapper:debug level="2" />
>
> + <!-- This is quite flexible; we can either have a log file per
> + module in Tomcat (example: ContextManager) or we can have
> + one for Servlets and one for Jasper, or we can just have
> + one tomcat.log for both Servlet and Jasper.
> +
> + If you omit "path" there, then stderr should be used.
> +
> + verbosityLevel values can be:
> + FATAL
> + ERROR
> + WARNING
> + INFORMATION
> + DEBUG
> + -->
> +
> + <Logger name="tc_log"
> + path="logs/tomcat.log"
> + customOutput="yes" />
> +
> + <Logger name="servlet_log"
> + path="logs/servlet.log"
> + customOutput="yes" />
> +
> + <Logger name="JASPER_LOG"
> + path="logs/jasper.log"
> + verbosityLevel = "INFORMATION" />
> +
> + <!-- Set the "home" attribute to point to where your in-process tomcat
> + configuration is located. ContextManager home is the base directory
> + for contexts, webapps/ and work/
> + -->
> + <ContextManager debug="2" workDir="work" home="D:\tomcat">
> + <!-- ContextInterceptor className="org.apache.tomcat.context.LogEvents" / -->
> + <ContextInterceptor className="org.apache.tomcat.context.AutoSetup" />
> + <ContextInterceptor className="org.apache.tomcat.context.DefaultCMSetter" />
> + <ContextInterceptor className="org.apache.tomcat.context.WorkDirInterceptor" />
> + <ContextInterceptor className="org.apache.tomcat.context.WebXmlReader" />
> + <ContextInterceptor className="org.apache.tomcat.context.LoadOnStartupInterceptor" />
> + <!-- Request processing -->
> + <RequestInterceptor className="org.apache.tomcat.request.SimpleMapper" debug="0" />
> + <RequestInterceptor className="org.apache.tomcat.request.SessionInterceptor" />
> + <RequestInterceptor className="org.apache.tomcat.request.SecurityCheck" />
> + <RequestInterceptor className="org.apache.tomcat.request.FixHeaders" />
> +
> <!--
> - JNI connector, make sure that you update the native_lib
> + JNI connector, make sure that you update the native_lib
> Parameter to point to your jni_connect.dll
> - -->
> + -->
> <Connector className="org.apache.tomcat.service.JNIEndpointConnector">
> - <Parameter name="native_lib" value="D:\tomcat\bin\jni_connect\nt4\i386\jni_connect.dll"/>
> + <Parameter name="native_lib" value="D:\tomcat\bin\i386\jni_connect.dll"/>
> </Connector>
>
> - <!--
> - Setting the contexts explicitly
> - -->
> - <Context path="/" docBase="D:\tomcat\webapps\ROOT" />
> - <Context path="/examples" docBase="D:\tomcat\webapps\examples" />
> - <Context path="/test" docBase="D:\tomcat\webapps\test" />
> + <!-- example - how to override AutoSetup actions -->
> + <Context path="/examples" docBase="webapps/examples" debug="0" reloadable="true" >
> + </Context>
> + <!-- example - how to override AutoSetup actions -->
> + <Context path="" docBase="webapps/ROOT" debug="0" reloadable="true" >
> + </Context>
>
> + <Context path="/test" docBase="webapps/test" debug="0" reloadable="true" >
> + </Context>
> +
> </ContextManager>
> </Server>
> +
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-tomcat/src/etc jni_workers.properties
jni_server.xml
Posted by Gal Shachor <sh...@il.ibm.com>.
>
> Wouldn't be simpler if you put the jni connector inside server.xml ( as a comment )
> and jni_worker.properties inside worker.properties ?
>
Only that from private corresponding with users I found out that it
confused them.
Common problems were:
1. So why do you use ajp12 also for in-process? (when ajp12 is defined,
but not used).
2. Users that forgot removing the HTTP connector.
...
so (at least for now) I'd rather have something simple.
>
> An even better solution is to add a "disabled" property to connectors, and mark the jni as disabled ( in
> default config). We can add an admin page later.
> ( as soon as we're done with this release, I want to generate worker.properties and urimaps automatically )
>
> Just an idea...
>
And a good idea, we should do that. Hopefully by Apache-2.0 we will have
an *almost*
unified configuration for Apache, IIS and Netscape and then generating
these files
will benefit all users.
Also, somebody told me once that a gram of automation is better then
tons of docs...
Gal Shachor