Gary Butler/CHARBROIL/WCB is out of the office.
I will be out of the office starting 06/11/2004 and will not return until 06/21/2004. I am out of the office on business. I will respond when I return. Gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29512] - Weird cache and jsp tags behavior.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29512. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29512 Weird cache and jsp tags behavior. --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 10:58 --- Have you tried to configure the web.xml - TOMCAT_HOME/conf/web.xml - JspServlet - enablePooling = false - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29521] New: - No destroy methods called on service shutdown
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29521. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29521 No destroy methods called on service shutdown Summary: No destroy methods called on service shutdown Product: Tomcat 5 Version: 5.0.24 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If the Tomcat server is stopped using shutdown.bat, then the shutdown sequence is completed without any problems and the appropriate destroy methods of the servlets and contextDestroyed methods of the ContextListener are called. If the same server instance is stopped using either: - the Apache Monitor task icon - the Windows Services panel - the command net stop Apache Tomcat Then these destroy methods do not get called and the server is just killed. Using: Java 1.4.2_04 Standard configuration and example applications - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29521] - No destroy methods called on service shutdown
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29521. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29521 No destroy methods called on service shutdown --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 12:22 --- I don't think so: are you absolutely certain that is the case ? Please don't get abused by the fact commons-logging may be stopping logging stuff. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29521] - No destroy methods called on service shutdown
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29521. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29521 No destroy methods called on service shutdown [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 12:27 --- You are probaly trying to kill the Tomcat using Task Manager. Seems to me that the Task Manager gives you a warning that the application is going to be shut down 'abnormarly', and gives you a proper warning: The process will not be given the chance to save its state or data before it is terminated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29521] - No destroy methods called on service shutdown
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29521. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29521 No destroy methods called on service shutdown [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 13:58 --- I am absolutely sure. In the destroy methods, I have added code that generates output, no matter what. This includes - the standard system.out / system.err usage - create a file with a timestamp - updating my configuration storage file (what I need) And no, there is no KILL involved. I ask for a nice and clean shutdown using the Stop Service. But still it behaves as if it had been killed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Valide o seu email
A Panda Software Portual está a proteger-se contra as mensagens de email indesejadas o chamado Spam. Pedimos desculpa pelo incómodo mas o seu email não está ainda validado. Para que os seus emails sejam considerados como válidos, por favor, valide-se nesta página: http://www.startcontrol.com/GoodMail/Validate.asp?I=EMOETESIAKYITIN Só necessita de se validar uma única vez. Todos os emails subsequentes serão considerados válidos. Obrigado. Panda Software Portugal
Re: Valide o seu email
A Panda Software Portual está a proteger-se contra as mensagens de email indesejadas o chamado Spam. Pedimos desculpa pelo incómodo mas o seu email não está ainda validado. Para que os seus emails sejam considerados como válidos, por favor, valide-se nesta página: http://www.startcontrol.com/GoodMail/Validate.asp?I=EMOGCEDTLSTBNHV Só necessita de se validar uma única vez. Todos os emails subsequentes serão considerados válidos. Obrigado. Panda Software Portugal
DO NOT REPLY [Bug 29526] New: - Cannot undeploy and deploy war file with on the same context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29526. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29526 Cannot undeploy and deploy war file with on the same context Summary: Cannot undeploy and deploy war file with on the same context Product: Tomcat 5 Version: 5.0.24 Platform: All OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Webapps:Manager AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 1)Start tomcat 2)Go to Manager. 3)deploy a war file. 4)undeploy it. 5)try to deploy it again and you get message FAIL - War file proxy.war already exists on server. It used to work fine in tomcat 5.0.19. It not fixed in the version 5.0.26-beta. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29526] - Cannot undeploy and deploy war file with on the same context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29526. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29526 Cannot undeploy and deploy war file with on the same context [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 14:44 --- This works for me. Please don't reopen the report. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29526] - Cannot undeploy and deploy war file with on the same context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29526. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29526 Cannot undeploy and deploy war file with on the same context [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 15:03 --- Hmm, actually, I tested again, and it now doesn't work anymore. I did countless changes already to fix this issue, and now I'm really really sick of it and tired of mickey mouse OS. As a result, I'm not going to fix this issue. I recommend either using Linux, investigating this issue more (and submit a patch), or convince another developer to look into it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[5.next] Summary
- Move to concrete classes for request/response, and remove all of the RTTI done in Catalina's pipeline - Use Tomcat 4.0 beta valve pattern - Redo logging using commons-logging, and remove Logger - Fork commons-digester, to remove what we don't need (many fancy features provided by beanutils, and in the process remove dependencies on beanutils and collections) - Attempt to redo a bit the deployer: * remove the CL code which is there to avoid JAR locking (or at least allow disabling this feature for non-Windows OSes) * move processing of context.xml to ContextConfig (at the expense of being able to specify the context class, which will move to an attribute on the Host), as I realize it is important to get context level configurability without adding too much complexity in the embedding application - Use the webapp CL as the main CL (without the locking tricks it is likely faster than the regular CL) - And the ongoing: allow all config/management through JMX (actually, we could consider going to a JMX config format) - Use any means necessary (hehe) so that Filip refactors the clutering module, and extend the regular Catalina objects, for easier maintenance - Remove anything useless (spring cleaning time), such as configuration options, container listeners (to be replaced with JMX notifications where it matters), etc - Possibly require JDK 1.5 (cleaner code, annotations, integrated JMX and JMX remote, etc) Overall, the throughtput of Tomcat should go up about 5-10% with those changes, as most significant optimizations are already done. I don't think any of these items will take too long to implement. I'm away next week, so I'll start the week after. Some of this could eventually be backported to 5.0.x :) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.next] Summary
Hi, Cool stuff ;) I'm away in two weeks, so I'll tag and branch 5.0.27 and TOMCAT_5_0 at the end of next week, so that you can start working on HEAD two weeks when you're back from vaca. Yoav Shapira Millennium Research Informatics -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 12:51 PM To: Tomcat Developers List Subject: [5.next] Summary - Move to concrete classes for request/response, and remove all of the RTTI done in Catalina's pipeline - Use Tomcat 4.0 beta valve pattern - Redo logging using commons-logging, and remove Logger - Fork commons-digester, to remove what we don't need (many fancy features provided by beanutils, and in the process remove dependencies on beanutils and collections) - Attempt to redo a bit the deployer: * remove the CL code which is there to avoid JAR locking (or at least allow disabling this feature for non-Windows OSes) * move processing of context.xml to ContextConfig (at the expense of being able to specify the context class, which will move to an attribute on the Host), as I realize it is important to get context level configurability without adding too much complexity in the embedding application - Use the webapp CL as the main CL (without the locking tricks it is likely faster than the regular CL) - And the ongoing: allow all config/management through JMX (actually, we could consider going to a JMX config format) - Use any means necessary (hehe) so that Filip refactors the clutering module, and extend the regular Catalina objects, for easier maintenance - Remove anything useless (spring cleaning time), such as configuration options, container listeners (to be replaced with JMX notifications where it matters), etc - Possibly require JDK 1.5 (cleaner code, annotations, integrated JMX and JMX remote, etc) Overall, the throughtput of Tomcat should go up about 5-10% with those changes, as most significant optimizations are already done. I don't think any of these items will take too long to implement. I'm away next week, so I'll start the week after. Some of this could eventually be backported to 5.0.x :) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.next] Summary
Shapira, Yoav wrote: Hi, Cool stuff ;) I'm away in two weeks, so I'll tag and branch 5.0.27 and TOMCAT_5_0 at the end of next week, so that you can start working on HEAD two weeks when you're back from vaca. I'm going to have a lot of fun: it's a training in Vienna. I guess you have to go earn money sometimes ;) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Valide o seu email
A Panda Software Portual está a proteger-se contra as mensagens de email indesejadas o chamado Spam. Pedimos desculpa pelo incómodo mas o seu email não está ainda validado. Para que os seus emails sejam considerados como válidos, por favor, valide-se nesta página: http://www.startcontrol.com/GoodMail/Validate.asp?I=EMPIGEKCNMTUMIG Só necessita de se validar uma única vez. Todos os emails subsequentes serão considerados válidos. Obrigado. Panda Software Portugal
DO NOT REPLY [Bug 29512] - Weird cache and jsp tags behavior.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29512. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29512 Weird cache and jsp tags behavior. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 18:04 --- Seems like adding that flag fixed it. Thanks for the suggestion JJ I appreciate the help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28612] - configure script fails locating libapr
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28612. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28612 configure script fails locating libapr [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 18:25 --- Hmm, no action here or on the mailing list. I'm closing this item for now due to lack of interest from both the tomcat developer and the original submitter . Feel free to reopen WHEN you have a patch, not until then, please. Thank.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28909] - ajpGetReply recoverable error 120000
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28909. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28909 ajpGetReply recoverable error 12 --- Additional Comments From [EMAIL PROTECTED] 2004-06-11 23:47 --- Hi George, This is definitely not a Solaris issue only as I'm seeing it on Linux. I'm using httpd 2.0.49, jk2 2.0.4, tomcat 5.0.24. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
