This isnt really related to Tomcat, but I really don't care:
You could make the connection static in the class DatabaseManager, so that
your application only uses one connection against DB. This could (?) cause
problems with Threading and several users accessing at once (I guess...).
Really not
Possible reasons (not really sure here):
You open a filestream, but you do not close it after use
You start a Thread that never finishes (no stop when tomcat runs destroy()
on your webapp)
You start a ServerSocket listener that doesn't timeout or stop gracefully.
Some other reason I do not see.
and/or Opera are much better. So, are
there any ways to tell IE that it shouldn't cache my servlet/jsp-pages?
Regards,
Øyvind Johansen
ElectricTimeCar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
-
From: Øyvind Johansen [mailto:[EMAIL PROTECTED]
Sent: 22 June 2005 11:11
To: 'Tomcat Users List'
Subject: Tomcat and Internet Explorers caching
Hello!
Our web-application uses a combination of JSP-pages and a controller
servlet. When viewing these pages with Internet Explorer
The /Simple_JSP part of the URL should be left out. Always start typing from
the web-app folder. (because, who knows when you want to rename the webapp?)
If you remove the /Simple_JSP part of the URLs in the web.xml, I think it
will work, additionally, you should try not setting restricted access
The /Simple_JSP part of the URL should be left out. Always start typing from
the web-app folder. (because, who knows when you want to rename the webapp?)
If you remove the /Simple_JSP part of the URLs in the web.xml, I think it
will work, additionally, you should try not setting restricted access
