Re: Bringing up tomcat, reliably.

2001-11-11 Thread Tom Drake 

 When I wrote a servlet for TC3.2.3, before Connection conn=bla..., I had
 Class.forName(org.postgresql.driver);
 As far as the location of postgresql.jar, I had it in JDK_HOME/lib and in
 TOMCAT_HOME/lib at least (maybe in WEB-INF/lib as well - I can't remember)

Thanks. I have postgresql.jar in a proper location, it seams. Looks like it is either 
not getting loaded or not registered as a JDBC driver.

QUESTION 1: How can I check if a particular jar/class has been accepted by the 
classloader?
QUESTION 2: Again, what is the proper way of specifying a system-wide JDBC driver in 
Tomcat 4.0?

Nix.



smime.p7s
Description: application/pkcs7-signature

RE: Bringing up tomcat, reliably.

2001-11-11 Thread Brett Porter 

Thank you for your reply.  I have tried HelloWorldExample and it is ok.
But I wonder how the path is set.

When I request http://apachehost/examples/servlets or
http://apahcehost/examples/servlets/index.html, I expect it will return
file d:/tomcat/webapps/examples/servlets/index.html in the tomcat server,
because I have the following line in the config file:
Alias /examples d:/tomcat/webapps/examples

But the error log return :
File does not exist: d:/tomcat/webapps/examples/servlets/index.html


Ada.

Larry Isaacs wrote:

 I don't know if it is a typo, but I don't believe there is
 a resource or directory corresponding to
 http://apachehost/examples/servlets, so 404 is the correct response.
 Try:

 http://apachehost/examples/servlet/HelloWorldExample

 Larry

  -Original Message-
  From: Ada [mailto:[EMAIL PROTECTED]]
  Sent: Friday, November 09, 2001 2:35 AM
  To: [EMAIL PROTECTED]
  Subject: tomcat and apache on separate machine
 
 
  Hi all,
 
  I need help to setup tomcat 3.2.2. and apache1.3.20 on separate
  machine!!
 
  I have done the following steps to move the apache to a new machine.
  1. move file mod_jk.conf-customized to new machine.
  2. move file workers.properties to new machine.
  3. modify httpd.conf in the new machine to point to file
  mod_jk.conf-customized.
  4. modify mod_jk.conf-customized to point the file worker.properties.
  5. modify workers.properties, change the value of
  worker.remotetomcat.host to the ip of tomcat machine.
  6. I suppose there is no changes required for server.xml in tomcat
  machine.
 
  When I tried to access URL http://apachehost/examples/servlets, I got
  error message 404.  It seems that it was trying to access the
  directory
  in the apache machine.
 
  Anything  I am missing?
 
 
  mod_jk.conf-customized
  =
  LoadModule jk_module modules/mod_jk.dll
 
  JkWorkersFile d:/apache/conf/workers.properties
  JkLogFile d:/apache/logs/mod_jk.log
  JkLogLevel error
  JkMount /*.jsp ajp12
  JkMount /servlet/* ajp12
 
  #
  # Auto configuration for the /examples context starts.
  #
 
  #
  # The following line makes apache aware of the location of
  the /examples
 
  context
  #
  Alias /examples d:/tomcat/webapps/examples
  Directory d:/tomcat/webapps/examples
  Options Indexes FollowSymLinks
  /Directory
 
  #
  # The following line mounts all JSP files and the /servlet/ uri to
  tomcat
  #
  JkMount /examples/servlet/* ajp13
  JkMount /examples/*.jsp ajp13
 
  workers.properties
  =
  worker.list=ajp12, ajp13
  worker.ajp12.port=8007
  worker.ajp12.host=xx.xx.xxx.xx   - ip of tomcat machine
  worker.ajp12.type=ajp12
  worker.ajp12.lbfactor=1
 
  worker.ajp13.port=8009
  worker.ajp13.host=xx.xx.xxx.xx  - ip of tomcat machine
  worker.ajp13.type=ajp13
  worker.ajp13.lbfactor=1
 
  Ada.
 
 
 
  --
  To unsubscribe:   mailto:[EMAIL PROTECTED]
  For additional commands: mailto:[EMAIL PROTECTED]
  Troubles with the list: mailto:[EMAIL PROTECTED]
 

 --
 To unsubscribe:   mailto:[EMAIL PROTECTED]
 For additional commands: mailto:[EMAIL PROTECTED]
 Troubles with the list: mailto:[EMAIL PROTECTED]


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

Re: Bringing up tomcat, reliably.

2001-11-11 Thread Nikola Milutinovic 

 Bob:
 
 I can't really comment on Linux, but most Unixes will encumber bound
 ports for a while (read a minute or two) under certain circumstances.
 This could be triggered if Tomcat had open client connections at
 the time of shutdown.

Those sessions should list under netstat as CLOSE_WAIT or anything else but 
ESTABLISHED. Anyway, that never stopped Apache or any other server software from 
coming up.

Are you sure Tomcat is down? Try lsof and see if it mentions either port 8080 or 
Tomcat (java).

Nix.