Adam, thanks for the response, I will try your suggestions. Thanks again,
Randall -----Original Message----- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 3:50 PM To: Tomcat Users List Subject: Re: Tomcat 4.1.29 CoyoteAdapter Exception I had an issue with tomcat 4.1.x (don't remember which - but it was Feb. last year) and sun java 1.4 Tomcat would just hang at random times and require a restart. I downgraded to java 1.3 to solve it. Try another Java - perhaps from IBM. Or check bugzilla. Adam On 02/25/2004 07:39 PM Randall Svancara wrote: > After further investigation, I am just going to chalk this one up as a stability > issue with windows XP. The same version of tomcat running with same configuration on > linux can sustain well over 10000+++ hits using jmeter while the same configuration > on windows barely handles 2000 hits before tomcat fails. > > Anyone know of a stable version of tomcat that works with windows. Do I need to > downgrade to 4.0.x or upgrade to 5.0.x versions of tomcat for better stability on > windows....or do I need to convince my boss what I have know all along, linux is > superior to windows. > > Thanks..... > > Randall > > -----Original Message----- > From: Randall Svancara [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 25, 2004 8:05 AM > To: Tomcat Users List > Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception > > > Ok, now I am thinking this error might be caused by Database Connection pooling. I > increased Mysql's max connection limit from the default to 500. I hope this enough > to satify my hungry application. Also I adjusted the apps xml configuration option > "maxActive to a value of 400 which is 100 less than the max. We will see if this > works. > > -----Original Message----- > From: Randall Svancara [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 25, 2004 7:47 AM > To: Tomcat Users List > Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception > > > Thanks, > > I have had a difficult time reproducing this error on a predictable basis. All I > can say is that it happens once per day, and I have temporarily wrote a perl script > that checks the service to see if it is working properly, and if not, it shuts down > tomcat and restarts it...A bandaid fix at best. > > I will give you a little more background on the webapp I have deployed. It is just > a basic webapp with several jsp pages and a couple of servlets. I am using Database > Connection Pooling with Mysql Connector J. The problem does not appear to happen on > any one particular jsp or servlet, but I will keep digging further to see if it is > or not. If I can create a reproducable test case, I will post it here. > > I will keep on researching the problem to see if I can pin point the exact error. > Thanks for the advice on using news groups. It is my first experience with them. > > Thanks, > > Randall > > -----Original Message----- > From: Adam Hardy [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 25, 2004 2:47 AM > To: Tomcat Users List > Subject: Re: Tomcat 4.1.29 CoyoteAdapter Exception > > > Randall, > I've often had issues that cause major problems, and my experience is > that user groups and mailing lists are normally unable to help without > there being an easily reproducible error. > > For instance, are you able to nail it down to a particular page or > servlet? Does it happen regularly or at random? Can you make a test case? > > Sorry I can't be any help, but good luck finding it. > > Adam > > On 02/25/2004 12:03 AM Randall Svancara wrote: > >>What would cause the coyote connector to return a null pointer >>exception. Every time this happens, mod_jk is unable to communicate >>with tomcat and as a result our web service is unusable. Is this a >>tomcat bug, or a problem with running tomcat on Windows XP..... >> >>Anyway, I have looked through this user group and found some other >>people with this problem on Solaris, but no real answers. >> >>Thanks. >> >> >> >> >>I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on >>Windows XP. Occasionally, I will receive the following error: >> >>2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is >>A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 >>CoyoteAdapter An exception or error occurred in the container during >>the request processing java.lang.NullPointerException at >>org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) >> at >>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) >> at >>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) >> at >>org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >> at >>org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193) >> at >>org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) >> at >>org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) >>at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673) >>at >>org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615) >> at >>org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786) >>at >>org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666) >> at java.lang.Thread.run(Thread.java:534) >> >> >> >> >> >> >>-----Original Message----- From: Randall Svancara Sent: Tuesday, >>February 24, 2004 11:34 AM To: Tomcat Users List Subject: RE: Tomcat >>4.1.29 CoyoteAdapter Exception >> >> >>Here is my server.xml in full for anyone interested. It is at the >>end of this email. >> >> >> >>-----Original Message----- From: Randall Svancara Sent: Tuesday, >>February 24, 2004 11:14 AM To: Tomcat Users List Subject: RE: Tomcat >>4.1.29 CoyoteAdapter Exception >> >> >>Hmm...I am unable to find anything in google regarding this error. >> >>-----Original Message----- From: Randall Svancara Sent: Tuesday, >>February 24, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: >>Tomcat 4.1.29 CoyoteAdapter Exception >> >> >>Hi, >> >>I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on >>Windows XP. Occasionally, I will receive the following error: >> >>2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is >>A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 >>CoyoteAdapter An exception or error occurred in the container during >>the request processing java.lang.NullPointerException at >>org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) >> at >>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) >> at >>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) >> at >>org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >> at >>org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193) >> at >>org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) >> at >>org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) >>at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673) >>at >>org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615) >> at >>org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786) >>at >>org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666) >> at java.lang.Thread.run(Thread.java:534) >> >>At which point the web service becomes UNAVAILABLE on port 80 through >>apache which forwards the requests via mod_jk to the tomcat 4.1.29 >>servlet engine. I am including some snippets from my server.xml >>below for the coyote connector. >> >><Connector className="org.apache.coyote.tomcat4.CoyoteConnector" >>port="8019" minProcessors="100" maxProcessors="600" >>enableLookups="false" redirectPort="8443" acceptCount="10" debug="10" >>connectionTimeout="60000" useURIValidationHack="false" >>protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/> >> >> >>I have also configured apache with 600 max threads, see snippet >>below. >> >># WinNT MPM # ThreadsPerChild: constant number of worker threads in >>the server process # MaxRequestsPerChild: maximum number of requests >>a server process serves <IfModule mpm_winnt.c> ThreadsPerChild 600 >>MaxRequestsPerChild 0 </IfModule> >> >>If someone has any idea what I have misconfigured or if you need more >>information, let me know. I am desperate at this point to find the >>root of this problem that has been plaguing our website since its >>release January. >> >>Thank you, >> >>Randall Svancara >> >>--------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >>--------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >><!-- 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"> >> >> >><!-- Uncomment these entries to enable JMX MBeans support --> >><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 8081 --> >><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="80" maxProcessors="400" >>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 --> <!-- >>Changed by Randall Svancara January 16, 2004 --> <!-- Changed by >>Randall Svancara January 22, 2004, added more min and max processes >>--> >> >> >><Connector className="org.apache.coyote.tomcat4.CoyoteConnector" >>port="8019" minProcessors="100" maxProcessors="600" >>enableLookups="false" redirectPort="8443" acceptCount="10" debug="99" >>connectionTimeout="60000" 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="8019" minProcessors="200" maxProcessors="600" acceptCount="10" >>connectionTimeout="60000" debug="10"/>--> >> >> >><!-- 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" >>disableUploadTimeout="true" acceptCount="100" debug="0" >>connectionTimeout="20000" proxyPort="80" useURIValidationHack="false" >>/> --> >> >><!-- 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). --> >> >><!-- Define the top level container in our container hierarchy --> >><Engine name="Standalone" defaultHost="localhost" debug="0" >>jvmRoute="worker1"> >> >><!-- 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="localhost" >>debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true"> >> >><!-- 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 means unlimited sessions are >>allowed. 0 means sessions will almost always be swapped out after use >>- this will be noticeably slow for your users. minIdleSwap: Sessions >>must be idle for at least this long (in seconds) before they will be >>swapped out due to maxActiveSessions. This avoids thrashing when the >>site is highly active. -1 or 0 means there is no minimum - sessions >>can be swapped out at any time. 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>user</name><value>sa</value></parameter> >><parameter><name>password</name><value></value></parameter> >><parameter><name>driverClassName</name> >><value>org.hsql.jdbcDriver</value></parameter> >><parameter><name>driverName</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> > > > -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
