session persistence with multiple webapps

I just discovered another feature of the the JDBCStore. If your webapps save their own classes in the Session (as webapps are wont to do), then when JDBCStore runs its checks to clean the database, it will try to pull in ALL sessions including those from other webapps. Becasue the classes fro

cvs commit: jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/valve RemoteAddrValveForm.java RemoteHostValveForm.java ValveUtil.java

amyroh 2003/02/10 19:34:43 Modified:webapps/admin build.xml webapps/admin/WEB-INF/classes/org/apache/webapp/admin ApplicationResources_en.properties ApplicationResources_es.properties webapps/admin/WEB-INF/cla

DO NOT REPLY [Bug 16951] New: - RunAsAService fails if I log in and then logout the service stops

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/valve RemoteAddrValveForm.java RemoteHostValveForm.java ValveUtil.java

amyroh 2003/02/10 18:27:15 Modified:webapps/admin build.xml webapps/admin/WEB-INF/classes/org/apache/webapp/admin ApplicationResources_en.properties ApplicationResources_es.properties webapps/admin/WEB-INF/cla

Re: Shutdown.sh does not work when long lasting operations, suchas SQL Queries, are still active!

My plan was to add to Server attribute of shutdownWait(or something else if someone else has a better suggestion). If greater than zero, then System.exit() would be called otherwise, do nothing. That way - we are backwards compatible. Die in 30 seconds Don't Die or or -Tim Craig R.

DO NOT REPLY [Bug 16950] New: - input validation not working

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Shutdown.sh does not work when long lasting operations, such asSQL Queries, are still active!

On Mon, 10 Feb 2003, Tim Funk wrote: > > Why is a kill done instead of a System.exit()? System.exit() is absolutely the wrong answer if Tomcat is embedded into a larger server-side application, rather than run separately in the usual way. At best, you would need to make this configurable someh

cvs commit: jakarta-servletapi-5/jsr152/examples/jsp2/simpletag BookBean.java.txt FindBookSimpleTag.java.txt Functions.java.txt HelloWorldSimpleTag.java.txt RepeatSimpleTag.java.txt

kinman 2003/02/10 15:50:28 Modified:jsr152 build.xml Removed: jsr152/examples/jsp2/el Functions.java.txt jsr152/examples/jsp2/jspattribute FooBean.java.txt ShuffleSimpleTag.java.txt TileSimpleTag.java.txt jsr152/examples/jsp2

Re: Shutdown.sh does not work when long lasting operations, suchas SQL Queries, are still active!

Why is a kill done instead of a System.exit()? Could instead a background daemon thread be launched, then be made to sleep for 30(?) second. If the thread wakes up then the tomcat has not exited properly and System.exit() can be called? Since this class would live in /common or /server - it sho

Re: Shutdown.sh does not work when long lasting operations, such as SQL Queries, are still active!

On Mon, Feb 10, 2003 at 12:04:08PM -0800, Costin Manolache wrote: > I can backport the "-force" option from 3.3 - basically save the PID and > then use kill if tomcat doesn't shut down gracefully. Yes, please!! Matt - To unsubs

DO NOT REPLY [Bug 16449] - Race condition when compiling jsp pages

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 16449] - Race condition when compiling jsp pages

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 14008] - Error in taglib iterator (with NESTED variable info)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Shutdown.sh does not work when long lasting operations, such as SQL Queries, are still active!

Craig R. McClanahan wrote: > It is OK for web applications to start threads -- as long as the web > application cleans up after itself when the application is shut down (the > easiest way to detect that is to create a ServletContextListener and wait > for the contextDestroyed() method of your list

RE: Shutdown.sh does not work when long lasting operations, such as SQL Queries, are still active!

In our case I think all threads started by our web application are cleaned up properly...the delay we're experiencing seems to be within 40 second which is acceptable otherwise...but the thing is that our users are used to the way TC401 shuts down (within 1 sec), they simply can not accept that 40

DO NOT REPLY [Bug 16319] - RequestDispatcher.include in a customTag causes IllegalStateException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 16449] - Race condition when compiling jsp pages

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 16319] - RequestDispatcher.include in a customTag causes IllegalStateException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

[4.1.20] Tagging today

Hi, I plan to tag 4.1.20 later today. Thanks to Glenn and Jan for getting some good fixes in. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt

remm2003/02/10 11:47:40 Modified:.RELEASE-NOTES-4.1.txt Log: - Status update. Revision ChangesPath 1.54 +66 -2 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt Index: RELEASE-NOTES-4.1.txt ===

cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config coyote.xml

remm2003/02/10 11:36:58 Modified:webapps/tomcat-docs/config coyote.xml Log: - Port patch. Revision ChangesPath 1.6 +6 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/coyote.xml Index: coyote.xml ==

cvs commit: jakarta-tomcat-catalina/webapps/docs/config coyote.xml

remm2003/02/10 11:36:44 Modified:webapps/docs/config coyote.xml Log: - Document the new connectionLinger attribute. Revision ChangesPath 1.5 +6 -0 jakarta-tomcat-catalina/webapps/docs/config/coyote.xml Index: coyote.xml ==

cvs commit: jakarta-tomcat-5 build.xml

jfarcand2003/02/10 11:17:52 Modified:.build.xml Log: Oups..the target already exists(at the end of the target) Revision ChangesPath 1.78 +0 -6 jakarta-tomcat-5/build.xml Index: build.xml

RE: Shutdown.sh does not work when long lasting operations, such as SQL Queries, are still active!

On Mon, 10 Feb 2003, Jindong Li wrote: > Date: Mon, 10 Feb 2003 13:53:52 -0500 > From: Jindong Li <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: 'Tomcat Developers List' <[EMAIL PROTECTED]> > Subject: RE: Shutdown.sh does not work when long lasting operations, >

cvs commit: jakarta-tomcat-5 build.xml

jfarcand2003/02/10 10:55:27 Modified:.build.xml Log: (null) Revision ChangesPath 1.77 +6 -0 jakarta-tomcat-5/build.xml Index: build.xml === RCS file: /home/cvs/jakarta-tomcat-5/buil

RE: Shutdown.sh does not work when long lasting operations, such as SQL Queries, are still active!

I think that's what we're experiencing here with Tomcat4.0.5...we have been using TC401 and the shutdown is instant...but I think they have changed the way TC is shutting down now...TC will gracefully shutdown i.e. waiting for all threads finish and then exit... If you want...you can try TC401, se

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources messages.properties

luehe 2003/02/10 10:21:32 Modified:jasper2/src/share/org/apache/jasper/resources messages.properties Log: Added error codes Revision ChangesPath 1.91 +4 -2 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.pr

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources messages.properties

luehe 2003/02/10 10:18:52 Modified:jasper2/src/share/org/apache/jasper/resources Tag: tomcat_4_branch messages.properties Log: Added error message for jsp.error.buffer.invalid Revision ChangesPath No revision No

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Compiler.java

luehe 2003/02/10 10:18:05 Modified:jasper2/src/share/org/apache/jasper/compiler Tag: tomcat_4_branch Compiler.java Log: Backport to TC 4.1.x: Fixed a NPE caused by nulling errorDispatcher: it is needed for Parser Revision ChangesPath No

DO NOT REPLY [Bug 16733] - Validator have no errDispatcher Instance

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Validator.java

luehe 2003/02/10 09:07:08 Modified:jasper2/src/share/org/apache/jasper/compiler Validator.java Log: Fixed 16200 ("isThreadSafe does not work !!") Revision ChangesPath 1.74 +4 -4 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Validator.java

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java Validator.java

luehe 2003/02/10 09:06:15 Modified:jasper2/src/share/org/apache/jasper/compiler Tag: tomcat_4_branch Generator.java Validator.java Log: Fixed 16200 ("isThreadSafe does not work !!") Revision ChangesPath No revision No

DO NOT REPLY [Bug 16200] - isThreadSafe does not work !!

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet JspServletWrapper.java

glenn 2003/02/10 08:39:00 Modified:jasper2/src/share/org/apache/jasper JspCompilationContext.java jasper2/src/share/org/apache/jasper/servlet JspServletWrapper.java Log: Port bug fix for 16449, thread locking from Tomca

DO NOT REPLY [Bug 16449] - Race condition when compiling jsp pages

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 16449] - Race condition when compiling jsp pages

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet JspServletWrapper.java

glenn 2003/02/10 08:29:52 Modified:jasper2/src/share/org/apache/jasper Tag: tomcat_4_branch JspCompilationContext.java jasper2/src/share/org/apache/jasper/servlet Tag: tomcat_4_branch JspServletWrapper.java Log: Fix bug

cvs commit: jakarta-tomcat-5 build.xml

remm2003/02/10 08:18:42 Modified:.build.xml Log: - A lot of junk was ending up in the tgz distribution. Revision ChangesPath 1.76 +15 -0 jakarta-tomcat-5/build.xml Index: build.xml ===

cvs commit: jakarta-tomcat-4.0 build.properties.sample

remm2003/02/10 08:15:05 Modified:.build.properties.sample Log: - It seems to me we can attempt to upgrade to Xerces 2.3 now. Revision ChangesPath 1.56 +3 -3 jakarta-tomcat-4.0/build.properties.sample Index: build.properties.sample

Shutdown.sh does not work when long lasting operations, such as SQL Queries, are still active!

I already tried it on the tomcat-user list but my question problem/question still remains. The problem is as described below (and already posted in the tomcat-user list), that tomcat refuses to stop when long lasting operations are still running. My primary concern is whether it is ok to start som

DO NOT REPLY [Bug 16874] - Same session for two different clients as a result of a lack in synchronization during recycling sessions

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-site/xdocs resources.xml

remm2003/02/10 06:31:46 Modified:docs resources.html xdocsresources.xml Log: - Resources page updates (with release dates, and indicate the book authors which are also committers). Revision ChangesPath 1.11 +20 -18jakarta-tomcat-sit

DO NOT REPLY [Bug 11656] - UTF-8 encoding not supported correctly in included text file or JSP Document

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 8982] - contentType in included file does not affect the parent

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper JspC.java

remm2003/02/10 03:03:07 Modified:jasper2/src/share/org/apache/jasper Tag: tomcat_4_branch JspC.java Log: - Port all the JSPC fixes from Tomcat 5. Revision ChangesPath No revision No revision 1

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper JspC.java

remm2003/02/10 02:31:50 Modified:jasper2/src/share/org/apache/jasper JspC.java Log: - Fix NPE. - Submitted (partially) by Yoshiyuki Karezaki Revision ChangesPath 1.29 +12 -12 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java Index: J

[GUMP] Build Failure - jakarta-tomcat-jk-native

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] /home/rubys [mkdir] C

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session StandardSession.java

remm2003/02/10 01:59:31 Modified:catalina/src/share/org/apache/catalina/session StandardSession.java Log: - Disable session recycling for now. Revision ChangesPath 1.34 +9 -4 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/

cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session StandardSession.java

remm2003/02/10 01:59:01 Modified:catalina/src/share/org/apache/catalina/session StandardSession.java Log: - Experiment: add some syncing in Session.expire. Revision ChangesPath 1.12 +58 -49 jakarta-tomcat-catalina/catalina/src/share/or

cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4 Constants.java CoyoteConnector.java

remm2003/02/10 01:57:37 Modified:coyote/src/java/org/apache/coyote/tomcat4 Constants.java CoyoteConnector.java Log: - Also port the linger patch to that branch. Revision ChangesPath 1.5 +1 -0 jakarta-tomcat-connectors/coyote/src/jav

Re: immediate Session backup

Tom Anderson wrote: On Saturday, February 8, 2003, at 10:59 PM, Tom Anderson wrote: I would like the PersistentManagerBase to immediately backup a session if the maxIdleBackup parameter is zero. The reason I want this behavior is that, in a load-balanced architecture, the next request might