Hi Justin!
Thanks a lot for your answer. But I would like to paste the relevant part of the docs
(Tomcat-A Minimilistic Users Guide) from the 'Getting Started' section.
--- Start ---
Getting Started
Tomcat is a servlet container with a JSP environment. A servlet container is a runtime
shell that manages and invokes servlets on behalf of users.
You can roughly partition servlet containers into:
1. Stand-alone servlet containers
These are an integral part of the web server. This is the case when using a Java-based
web server, for example the servlet container that is part of the JavaWebServer.
Stand-alone is the default mode used by Tomcat.
Most web servers, however, are not Java-based, which leads us to the next two
container types.
2. In-process servlet containers
The servlet container is a combination of a web server plugin and a Java container
implementation. The web server plugin opens a JVM inside the web server's address
space and lets the Java container run in it. If a certain request should execute a
Servlet, the plugin takes control over the request and passes it (using JNI) to the
Java container. An in-process container is suitable for multi-threaded single-process
servers and provides good performance but is limited in scalability.
3. Out-of-process servlet containers
The servlet container is a combination of a web server plugin and a Java container
implementation that runs in a JVM outside the web server. The web server plugin and
the Java container JVM communicate using some IPC mechanism (usually TCP/IP sockets).
If a certain request should execute a Servlet the plugin takes control over the
request and passes it (using the IPCs) to the Java container. The response time of an
out-of-process engine is not as good as in the in-process one but the out-of-process
engine performs better in many measurable ways (scalability, stability, etc.).
***
Tomcat can be used as either a stand-alone container (mainly for development and
debugging) or as an add-on to an existing web server (currently Apache, IIS and
Netscape servers are supported). This means that whenever you are deploying Tomcat you
will have to decide how to use it and, *** if you select options 2 or 3, you will also
need to install a web server adapter ***
***
--- End ---
Please reply if I understand the marked portion (above) wrongly.
Many Thanks
Shailesh
On Sun, 30 Sep 2001 Justin Erenkrantz wrote :
> On Sun, Sep 30, 2001 at 01:46:37PM -0000, Shailesh S.
> Gokhale wrote:
> > 1. I understand that Tomcat can work with any
> (supported) web
> > server in two modes - 'In Proc' and 'Out of Proc'. I
> have
> > successfully configured Tomcat (Out of Proc) to work
> with Apache.
> > The question is how can I make it work 'In Proc' with
> Apache?
>
> I'm not aware how Apache will load the JVM, so I don't
> see how you
> will get it to be "in proc." AFAIK, all of the modules
> for all
> webservers require an externally running copy of
> Tomcat. I could
> be wrong though. I think some of them are smart enough
> to invoke
> Tomcat if it isn't running, but that doesn't mean they
> are running
> in the same process space.
>
> > 2. In relation to the above, there seem to be two
> available
> > adapters for the Apache/Tomcat collaboration in the
> Windows
> > environment. One is ApacheModuleJServ.dll and another
> is
> > mod_jk.dll. [The second one replaces a more complex
> adapter
> > (mod_jserv.dll) available earlier and no longer used]
> . My
> > question is what is the difference between the two -
> that is
> > ApacheModuleJServ.dll and mod_jk.dll?
>
> I think ApacheModuleJServ.dll is just a renamed version
> of
> mod_jserv.dll. You should always be using mod_jk -
> mod_jserv
> isn't supported anymore. -- justin
>
