1. You can try giving a password to the database and setting the same in the
server.xml. See if this works.
Thanks
Tejas
-Original Message-
From: Roy Kiesler [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 03, 2006 10:41 PM
To: users@tomcat.apache.org
Subject: Tomcat 4:
Hello
You can shutdown the tomcat. Delete all the contents under work folder.
Restart the tomcat. Now check if this thing works.
Thanks
Tejas
devteam_matsys [EMAIL PROTECTED]
08/03/2006 10:42 AM
Please respond to
Tomcat Users List users@tomcat.apache.org
To
users@tomcat.apache.org
cc
Hi
I had once worked on an application with approximately 40 tags. I had an Ant
task that compiled these tags and build a jar file. Then the ant task would
also deploy it on tomcat and restart the webapp. The webapp restart time was
very low and also client http request servicing was very quick.
Hi
The session timeout will occur when the user does not perform any activity
for a time longer than session timeout value. Since your app uses URL
rewriting method of session maintenance, any request from the browser after
session timeout, will still be sending the old jsessionid.
To solve the
Hi
I would have thought that multiple requests for the same user should not
have any impact on the tomcat as long as the server logic does not try to
modify the same session data simultaneously. Probably using the synchronized
keyword here may be required.
The request data modifications should
Hi
Not sure if this is helpful to you. I had found this URL useful. The URL
shows how to setup a JNDI DataSource in Tomcat.
http://tomcat.apache.org/tomcat-4.1-doc/jndi-datasource-examples-howto.html
Also, check the Java Servlet specification for more information.
Regards
Tejas
-Original
