Hi Guys,
Here is what is happening now with very precise info. I think
I was dealing at a very high level so far. . I am running apache 1.3.19
+ tomcat 4.1.18 and modjk 1.2.1
I have given the URL down from where I got the entire .so module,no
building was done just a copy from Jakarta web site to the apache module
directory.Now this is the picture on the linux server. http://192.168.132.34 is a test page from apache. http://192.168.132.34/bugzilla is a perl-CGI application sitting on port 80. http://192.168.132.34:8080 tomcat's page http://192.168.132.34:8080/examples/jsp/index.html shows me JSP samples. They execute very well http://192.168.132.34:8080/examples/servlets/index.html shows me servelets they execute very well. PAGE NOT FOUND ERRORS for http://192.168.132.34/examples/jsp/index.html http://192.168.132.34/examples/servlets/index.htm; Pl. Look for-----> <-------- comments. I am attaching all the configs file as mentioned by Jan/John. The mod_jk.conf file is always empty after I deleted the contents,since I assumed that it would be autogenrated. But it never did. I edited the contents of server.xml and insered workers.properties from John's website, Just retyping the URL again.. http://www.johnturner.com/howto/apache2-tomcat4110-jk-howto.html Thanks Again..... Hope to hear a LOT!! ~Vivek -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, January 06, 2003 9:44 PM To: Tomcat Users List Subject: Re: RE: TOMCAT Not listening on 80 Hi there, Hi vivek, John Turner's suggestion is right on. Try setting it up on a development box first. This will save you and your colleagues a lot of headaches later on. Besides it is good practice. But here are some pointers. --------> I have shifted the Bugzilla MySQL DB on a different box and ghosted the server too so I damn well have a contingency plan. Haven't I. Let's not worry about it anymore.... If anything goes crazy I will ghost it again. <---------- 1. Log in as root or su to it su - ---------> one of the reasons why I write to user groups :-) <---------- 2. Search for perl which perl or whereis perl This should return /usr/bin/perl or /usr/local/bin/perl ------------------> /usr/bin/perl <------------------ 3. Check the version /path/to/perl -V Note this version ----------> 5.6.0 <---------- 4. Search for apachectl cd / ; find . -local -name 'apachectl' -print This might take a while but should list where apachectl is located -----------------> I had apache 1.3.27 from redhat and unluckily rpm does not install bin directory anywhere. SO I use servie httpd restart,stop,start and etc to reread httpd.conf. But wait I did find this file in one of the oracle 9i home ./home/oracle/product/9.0.1/Apache/Apache/bin/apachectl on the same machine, yeah the big box runs almost everything. oracle 9i uses this for it's web applications on this server. So I ran this file with configtest,it said Syntax OK. I did a more on it as well and it uses 'bash' as the interpreter. (( I see where the perl thing came from :-) <-------------------- 4a. Search for workers.properties cd / ; find . -local -name 'workers.properties' -print Note this location as this is what you'll put in JkWorkersFile later on ---------> /usr/local/jakarta-tomcat-4.1.18/conf/jk/workers.properties I typed everything from John Turner's site accordingly, changed the path of module as far as I know it well. I had to create this directory jk after after I learned I require it BTW: -local gave invalid predicate on my linux RH 7.1 <--------- 5. Run apachectl configtest /path/to/apachectl configtest It should return 'Syntax OK' if everything is okay. If it returns 'not found' check to make sure that the first line of apachectl is your perl binary --------> IT did OK <------- more apachectl #!/path/to/perl <-- should match step 2 ----> no that's sh in oracle's apache(not on the port 80) <---- 6. Check to make sure that you have the Tomcat connectors installed and search for mod_jk.so (JK1 I think) this should be in $APACHE_HOME/libexec ---------------> I did not make this module but downloaded it from Jakarta.apache.org. It was readymade as I did not find any src or binary to build it. Here is the link from which I got it. I simply copied it to the /etc/httpd/modules where other apache modules are. http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1 .2.1/bin/linux/i386/ I downloaded mod_jk-1.3-eapi.so as per the instruction on this page. <-------------------- 7. There should be a couple of lines in your httpd conf along the following LoadModule libexec/mod_jk.so ... [snip] ... AddModule mod_jk.so ----> I also did add these line in httpd.conf, I added the Addmodule line after reading point 7, but it was mod_jk.c not .so <------------- Read more on these directives on the apache website httpd.apache.org 8. Check apache's config and Restart apache /path/to/apachectl configtest /path/to/apachectl graceful -------> I did this with service httpd restart not with this script. <--------------- 9. If this doesn't return an error, proceed with John's suggestions below. As a side note, to configure tomcat to respond to 80 with apache you have to set up JKMount points and "redirect" jsp requests to tomcat (that's what the mod_jk.so is for) Something like this in httpd.conf ---------------> Hooon!!!! So this is where the loopholes might be I did add these line somewhere in httpd.conf with the exact path of workers.properties without these '' ofcourse!! And I checked out the tomcat1 I think the user is 'ajp13' there . I have the file attched here for reference. Does it need to be a unix user or it is just a reference in context of TOMCAT.? <-------------------- JKWorkersFile '/path/to/workers.properties' JKLogLevel debug JKMount /examples/*.jsp tomcat1 JKMount /examples/servlet/*.jsp tomcat1 Make sure that the "tomcat1" worker exists in workers.properties where you'll have to declare the worker and set some properties I'm basing this off of tomcat 3.x it might have changed for 4.x Try running a search off google also for "tomcat mod_jk tutorial" or just visit jakarta.apache.org ----------> I am planning it this weekend <----------------- Hope that helps. GREAT!!!!!!!!!!!!!!!!!! Jan-Michael ----- Original Message ----- From: "Turner, John" <[EMAIL PROTECTED]> Date: Monday, January 6, 2003 5:33 am Subject: RE: TOMCAT Not listening on 80 > > Did you include a LoadModule line in Apache's config to load > mod_jk? You > cannot use JK commands in httpd.conf unless you load a module that > understands them. > > Perhaps you might want to take a step back, tell us more > specifically what > you want to do, and perhaps consider setting up a test environment > that is > not on a production server so that you can understand how to integrate > Tomcat with Apache without interfering with your colleague's use > of your > bugzilla installation. > > John > > > -----Original Message----- > > From: Vivek Singh [mailto:[EMAIL PROTECTED]] > > Sent: Monday, January 06, 2003 6:43 AM > > To: 'Tomcat Users List' > > Subject: RE: TOMCAT Not listening on 80 > > > > > > John, > > I don't remember doing any of these JkMount > > directives, I > > did not find any reference to this in your website, so there you go > > :-).... > > > > And I had created a mod_jk.conf file in the path you had told and > > included it at the end of httpd.conf, It had some autogenerated > > stuff in it put in my tomcat when I checked it later on.. > > > > After that when I tried restarting apache it gave me this > > error too > > and did not come up. > > > > Invalid command 'JkWorkersFile', perhaps mis-spelled or defined > by a > > module not > > included in the server configuration > > > > Then I echoed blanks in the file and Apache restared pretty > well and > > tomcat did not listen on 80. > > > > So let me give a try adding all this... > > > > ~vivek > > > > > > > > -----Original Message----- > > From: Turner, John [mailto:[EMAIL PROTECTED]] > > Sent: Monday, January 06, 2003 4:48 PM > > To: ''Tomcat Users List' ' > > Subject: RE: TOMCAT Not listening on 80 > > > > > > If you're saying that Apache's httpd.conf has no JkMount > > directives for > > JK, > > then yes, your setup will never work. > > > > If you've setup auto-generation according to my HOWTO, you can check > > your Apache config prior to a restart as specified in my HOWTO, > > with: > > > > /path/t> > > provided you have an Include statement that includes > mod_jk.conf. > > > > If you do have an Include statement, then you can simply > > restart Apache > > nicely with: > > > > /path/t> > > This will cause Apache to refuse new connection requests, > > wait until all > > current connection requests are closed, and then reread > > httpd.conf. It > > all > > happens in a second or two, it is highly doubtful that anyone > > would even > > notice. > > > > John > > > > -----Original Message----- > > From: Vivek Singh > > To: 'Tomcat Users List' > > Sent: 1/6/03 6:04 AM > > Subject: RE: TOMCAT Not listening on 80 > > > > Won't stop it!! > > My team members will kill me if I stop it. I believe one of > > the reasons > > why Tomcat cannot communicate with Apache is that I have no > > virtual host > > thing going. I might be wrong > > > > What do you think? > > > > ~Vivek > > > > -----Original Message----- > > From: Donie Kelly [mailto:[EMAIL PROTECTED]] > > Sent: Monday, January 06, 2003 4:19 PM > > To: 'Tomcat Users List' > > Subject: RE: TOMCAT Not listening on 80 > > > > When you say you can't stop it do you mean "won't stop it?" or > you are > > unable to stop it? > > > > Donie > > > > > > -----Original Message----- > > From: Vivek Singh [mailto:[EMAIL PROTECTED]] > > Sent: 06 January 2003 10:52 > > To: 'Tomcat Users List' > > Subject: TOMCAT Not listening on 80 > > > > Hi, > > > > I did exactly as in the John Turner's website, Apache > > 1.3.27 with mod_jk and tomcat 4.1.18. To sum up here is what is > > happening > > > > 1. I already have a Bugzilla running on my server at port80. Can't > > stop it > > 2. At port 8080 I can see Tomcat listening. I need it on 80 ( > Apache> is running here) > > > > > > Can anyone help me? > > > > > > Thanks a lot in Advance and thanks John mail for Host Container > > clarifications > > > > > > ~Vivek > > > > > > > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > <<Wipro_Disclaimer.txt>> <<ATT128036.txt>> > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: <mailto:tomcat-user- > [EMAIL PROTECTED]>For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
httpd.conf
Description: Binary data
workers.properties
Description: Binary data
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
modJk="/usr/lib/apache/mod_jk.so"/>
<!-- Comment these entries out to disable JMX MBeans support -->
<!-- You may also configure custom components (e.g. Valves/Realms) by
including your own mbean-descriptor file(s), and setting the
"descriptors" attribute to point to a ';' seperated list of paths
(in the ClassLoader sense) of files to add to the default list.
e.g. descriptors="/com/myfirm/mypackage/mbean-descriptor.xml"
-->
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Tomcat-Standalone">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 4.0 documentation bundle for more detailed
instructions):
* Download and install JSSE 1.0.2 or later, and put the JAR files
into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="100" debug="0" connectionTimeout="20000"
useURIValidationHack="false" disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to -1 -->
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8443" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" scheme="https" secure="true"
useURIValidationHack="false" disableUploadTimeout="true">
<Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
clientAuth="false" protocol="TLS" />
</Connector>
-->
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="0"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
<!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8082" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" connectionTimeout="20000"
proxyPort="80" useURIValidationHack="false"
disableUploadTimeout="true" />
-->
<!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083 -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8083" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084 -->
<!--
<Connector className="org.apache.catalina.connector.http10.HttpConnector"
port="8084" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- You should set jvmRoute to support load-balancing via JK/JK2 ie :
<Engine name="Standalone" defaultHost="localhost" debug="0" jmvRoute="jvm1">
-->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Standalone" defaultHost="localhost" debug="0">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.3
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>
<!-- Because this Realm is here, an instance will be shared globally -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!--
<Realm className="org.apache.catalina.realm.MemoryRealm" />
-->
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority"
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!-- Define the default virtual host -->
<Host name="192.168.132.34" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<Listener className="org.apache.ajp.tomcat4.config.ApacheConfig" append="true" forwardAll="false" modJk="/usr/lib/apache/mod_jk.so"
workersConfig="/usr/local/tomcat/conf/jk/workers.properties" />
</Host>
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across *all* web applications contained
in this virtual host. -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn"
debug="0"/>
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
<!-- Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in the "logs"
directory relative to $CATALINA_HOME. If you wish, you can specify
a different directory with the "directory" attribute. Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
directory.-->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
timestamp="true"/>
<!-- Define properties for each web application. This is only needed
if you want to set non-default properties, or have web application
document roots in places other than the virtual host's appBase
directory. -->
<!-- Tomcat Root Context -->
<!--
<Context path="" docBase="ROOT" debug="0"/>
-->
<!-- Tomcat Examples Context -->
<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_examples_log." suffix=".txt"
timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>
<!-- If you wanted the examples app to be able to edit the
user database, you would uncomment the following entry.
Of course, you would want to enable security on the
application as well, so this is not done by default!
The database object could be accessed like this:
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
UserDatabase database =
(UserDatabase) envCtx.lookup("userDatabase");
-->
<!--
<ResourceLink name="userDatabase" global="UserDatabase"
type="org.apache.catalina.UserDatabase"/>
-->
<!-- PersistentManager: Uncomment the section below to test Persistent
Sessions.
saveOnRestart: If true, all active sessions will be saved
to the Store when Catalina is shutdown, regardless of
other settings. All Sessions found in the Store will be
loaded on startup. Sessions past their expiration are
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out. minIdleSwap
limits this. -1 or 0 means unlimited sessions are allowed.
If it is not possible to swap sessions new sessions will
be rejected.
This avoids thrashing when the site is highly active.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
activity.
0 means sessions will almost always be swapped out after
use - this will be noticeably slow for your users.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked periodically.
-1 means sessions won't be swapped out for this reason,
although they may be swapped out for maxActiveSessions.
If set to >= 0, guarantees that all sessions found in the
Store will be loaded on startup.
maxIdleBackup: Sessions will be backed up (saved to the Store,
but left in active memory) if idle for this long (in seconds),
and all sessions found in the Store will be loaded on startup.
If set to -1 sessions will not be backed up, 0 means they
should be backed up shortly after being used.
To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
and minIdleBackup all to -1, saveOnRestart to false, then restart
Catalina.
-->
<!--
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
-->
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/EmployeeAppDb">
<parameter><name>username</name><value>sa</value></parameter>
<parameter><name>password</name><value></value></parameter>
<parameter><name>driverClassName</name>
<value>org.hsql.jdbcDriver</value></parameter>
<parameter><name>url</name>
<value>jdbc:HypersonicSQL:database</value></parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
<ResourceLink name="linkToGlobalResource"
global="simpleValue"
type="java.lang.Integer"/>
</Context>
</Host>
</Engine>
</Service>
<!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
as its servlet container. Please read the README.txt file coming with
the WebApp Module distribution on how to build it.
(Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
To configure the Apache side, you must ensure that you have the
"ServerName" and "Port" directives defined in "httpd.conf". Then,
lines like these to the bottom of your "httpd.conf" file:
LoadModule webapp_module libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
The next time you restart Apache (after restarting Tomcat, if needed)
the connection will be established, and all applications you make
visible via "WebAppDeploy" directives can be accessed through Apache.
-->
<!-- Define an Apache-Connector Service -->
<!--
<Service name="Tomcat-Apache">
<Connector className="org.apache.catalina.connector.warp.WarpConnector"
port="8008" minProcessors="5" maxProcessors="75"
enableLookups="true" appBase="webapps"
acceptCount="10" debug="0"/>
<Engine className="org.apache.catalina.connector.warp.WarpEngine"
name="Apache" debug="0">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="apache_log." suffix=".txt"
timestamp="true"/>
<Realm className="org.apache.catalina.realm.MemoryRealm" />
</Engine>
</Service>
-->
</Server>
**************************Disclaimer************************************************ Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ***************************************************************************************
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
