I am still unable to make servlet reloading work on AIX4.3
with tomcat 4 and apache 1.3.19
I have included some of my webapps directory structure and
my server.xml which is the install version with my editing at the bottom
The context is ct and the service is tomcat-apache
In desperation and frustration trying really hard to use tomcat 4
Paul
> ./ct
> ./ct/ErrorPage.jsp
> ./ct/CSS_select.jsp
> ./ct/Navbar.jsp
> ./ct/getenvs.jsp
> ./ct/LogonTest.jsp
> ./ct/DisplayLogon.jsp
> ./ct/Logon.jsp
> ./ct/Receive.jsp
> ./ct/Send.jsp
> ./ct/WHControl.jsp
> ./ct/receive.jar
> ./ct/Nev-bar.jsp
> ./ct/send.jar
> ./ct/LoadLogon.jsp
> ./ct/CTListSC.jsp
> ./ct/CTViewJob.jsp
> ./ct/WHListStock.jsp
> ./ct/WHListStockSum.jsp
> ./ct/wml_ErrorPage.jsp
> ./ct/wml_joblist.jsp
> ./ct/wml_logon.jsp
> ./ct/wml_viewjob.jsp
> ./ct/WEB-INF
> ./ct/WEB-INF/web.xml
> ./ct/WEB-INF/classes
> ./ct/WEB-INF/classes/playjsp
> ./ct/WEB-INF/classes/playjsp/Logon.class
> ./ct/WEB-INF/classes/playjsp/Logon$1.class
> ./ct/WEB-INF/classes/playjsp/Job$1.class
> ./ct/WEB-INF/classes/playjsp/Job.class
> ./ct/WEB-INF/classes/playjsp/ListStatusChanges$1.class
> ./ct/WEB-INF/classes/playjsp/ListStatusChanges.class
> ./ct/WEB-INF/classes/playjsp/ListWHStockSummary.class
> ./ct/WEB-INF/classes/playjsp/ListWHStockSummary$1.class
> ./ct/WEB-INF/classes/playjsp/ListWHStock.class
> ./ct/WEB-INF/classes/playjsp/ListWHStock$1.class
> ./ct/WEB-INF/classes/playjsp/CTControl.class
> ./b2b
> ./b2b/WEB-INF
> ./b2b/WEB-INF/classes
> ./b2b/WEB-INF/classes/playjsp
> ./b2b/WEB-INF/classes/playjsp/BBControl.class
> ./b2b/WEB-INF/classes/playjsp/ListB2B.class
> ./b2b/WEB-INF/classes/playjsp/ListB2B$1.class
> ./b2b/WEB-INF/classes/playjsp/Parameters.class
> ./b2b/WEB-INF/classes/playjsp/Parameters$1.class
> ./b2b/WEB-INF/classes/playjsp/Parameters$2.class
> ./b2b/WEB-INF/classes/playjsp/ListB2B$2.class
> ./b2b/WEB-INF/classes/playjsp/ListB2B$3.class
> ./b2b/WEB-INF/web.xml
> ./b2b/BBListTransactions.jsp
> ./b2b/panpars.xml
> ./b2b/hostpars.xml
> ./b2b/BBTest.jsp
> ./b2b/apachepars.xml
> ./b2b/testpars.xml
> ./b2b/BBListSummaryTrans.jsp
>
> My server.xml
>
> <!-- Alternate Example-less 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">
>
>
> <!-- 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:
> * Download and install JSSE 1.0.2 or later, and put the JAR files
> into "$JAVA_HOME/jre/lib/ext".
> * Edit "$JAVA_HOME/jre/lib/security/java.security" and add
> security.provider.2=com.sun.net.ssl.internal.ssl.Provider
> * Execute: keytool -genkey -alias tomcat -keyalg RSA
> with a password value of "changeit".
>
> 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 HTTP/1.1 Connector on port 8080 -->
> <Connector
className="org.apache.catalina.connector.http.HttpConnector"
> port="8080" minProcessors="5" maxProcessors="75"
> enableLookups="true" redirectPort="8443"
> acceptCount="10" debug="0" connectionTimeout="60000"/>
> <!-- Note : To disable connection timeouts, set connectionTimeout
value
> to -1 -->
>
> <!-- Define an SSL HTTP/1.1 Connector on port 8443 -->
> <!--
> <Connector
className="org.apache.catalina.connector.http.HttpConnector"
> port="8443" minProcessors="5" maxProcessors="75"
> enableLookups="true"
> acceptCount="10" debug="0" scheme="https" secure="true">
> <Factory className="org.apache.catalina.net.SSLServerSocketFactory"
> clientAuth="false" protocol="TLS"/>
> </Connector>
> -->
>
> <!-- Define a Proxied HTTP/1.1 Connector on port 8081 -->
> <!-- See proxy documentation for more information about using
this. -->
> <!--
> <Connector
className="org.apache.catalina.connector.http.HttpConnector"
> port="8081" minProcessors="5" maxProcessors="75"
> enableLookups="true"
> acceptCount="10" debug="0" connectionTimeout="60000"
> proxyPort="80"/>
> -->
>
> <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8082 -->
> <!--
> <Connector
> className="org.apache.catalina.connector.http10.HttpConnector"
> port="8082" 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">
>
> <!-- 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 -->
>
> <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?user=test;password=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?user=scott;password=tige
> r"
> 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">
>
> <!-- 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"/>
>
> <!-- 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"/>
> -->
>
> </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="8009" minProcessors="5" maxProcessors="75"
> enableLookups="true"
> acceptCount="10" debug="0"/>
>
> <!-- Replace "localhost" with what your Apache "ServerName" is set
> to -->
> <Engine className="org.apache.catalina.connector.warp.WarpEngine"
> name="Apache" defaultHost="pan.web.roadrunner.uk.com" debug="0"
> appBase="webapps">
>
> <!-- Global logger unless overridden at lower levels -->
> <Logger className="org.apache.catalina.logger.FileLogger"
> prefix="apache_log." suffix=".txt"
> timestamp="true"/>
>
> <!-- Because this Realm is here, an instance will be shared
> globally -->
> <Realm className="org.apache.catalina.realm.MemoryRealm" />
>
> <Host name="pan.web.roadrunner.uk.com" debug="0" appBase="webapps">
> <Context path="" docBase="ROOT" debug="0"/>
> <Context path="/ct" docBase="ct" debug="4" reloadable="true">
> <Loader checkInterval="5"/>
> </Context>
> </Host>
>
> </Engine>
>
> </Service>
>
> </Server>
>
>
>
>
> ----- Original Message -----
> From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, September 12, 2001 7:01 PM
> Subject: Re: tomcat 4 beta 7 - reloading doesn't work
>
>
> >
> >
> > On Wed, 12 Sep 2001, sankar kondur wrote:
> >
> > > Date: Wed, 12 Sep 2001 10:29:45 -0700 (PDT)
> > > From: sankar kondur <[EMAIL PROTECTED]>
> > > Reply-To: [EMAIL PROTECTED]
> > > To: [EMAIL PROTECTED]
> > > Subject: tomcat 4 beta 7 - reloading doesn't work
> > >
> > > Hi,
> > >
> > > i am using tomcat 4 beta 7. reloading doesn't seem to
> > > work at all.
> > >
> > > i did the following
> > >
> > > 1. used reloadable="true"
> > > 2. put the classes in WEB-INF/classes
> > > 3. i also tried putting the classes in a jar in
> > > WEB-INF/lib instead of WEB-INF/classes
> > >
> > > it doesn't seem to work.
> > > anyone experienced this problem.
> > >
> >
> > It works for me, and for many others.
> >
> > Could you please prepare a small webapp WAR file that illustrates your
> > problem, and create a bug report (with this WAR as an attachment)?
We'll
> > need a copy of your server.xml file as well.
> >
> > http://nagoya.apache.org/bugzilla/
> >
> > Without a detailed test case, there is little we can do.
> >
> > > thanks,
> > > SK
> > >
> >
> > Craig
> >
> >
>
