Replacing WebappClassLoader
Hi! I tried to configure tomcat 4.0.2 to use my own class loader implementation for web-app class loading. The documentation implies that this can be done by secifying a loaderClass attribute in my Context/Loader element in server.xml. This does not work. Stepping through the code of org.apache.catalina.loader.WebappLoader (which i still want to use) I found out that the loaderClass Property does get set, but it seems to be ignored since org.apache.catalina.loader.WebappClassLoader gets instantiated explicitly (line 615-, cvs revision 1.12.2.5). Is this intended? Perhaps I missed something in the code. Best regards, Volker. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Using InstallAnywhere for Tomcat installer
on 4/23/02 2:33 PM, Remy Maucherat [EMAIL PROTECTED] wrote: To get around this, Zero G has offered to donate a license of InstallAnywhere to Tomcat, as well as installer code. I have a strong -1 on this unless the licese is granted to ALL Jakarta projects. It isn't fair to judge one project under Jakarta more worthy of this license over other projects. Where did that rule that everything must be Jakarta-wide come from ? It's up to each project to ask IMO. Also, I don't see many Jakarta projects which could benefit from having an installer. James maybe. JMeter seems a better candidate for WebStart. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RUNNING.txt
remm02/04/24 01:06:14 Modified:.RUNNING.txt Log: - Document that the configuration needs to be modified to be able to run the admin and manager webapp with CATALINA_BASE. - Fixes bug 5166. Revision ChangesPath 1.5 +13 -1 jakarta-tomcat-4.0/RUNNING.txt Index: RUNNING.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RUNNING.txt,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- RUNNING.txt 26 Dec 2001 01:21:24 - 1.4 +++ RUNNING.txt 24 Apr 2002 08:06:14 - 1.5 @@ -1,4 +1,4 @@ -$Id: RUNNING.txt,v 1.4 2001/12/26 01:21:24 glenn Exp $ +$Id: RUNNING.txt,v 1.5 2002/04/24 08:06:14 remm Exp $ Running The Tomcat 4.0 Servlet/JSP Container @@ -126,6 +126,18 @@ If you do not set CATALINA_BASE to an explicit value, it will be initialized to the same value as is set for CATALINA_HOME (which means that the same directory is used for all relative path resolutions). + +The administration and manager web applications, which are defined in the +$CATALINA_BASE/webapps/admin.xml and $CATALINA_BASE/webapps/manager.xml will +not run in that configuration, unless either: +- The path specified in the docBase attribute of the Context element is made + absolute, and replaced respectively by $CATALINA_HOME/server/webapps/admin + and $CATALINA_HOME/server/webapps/manager +- Copying and linking both web applications in $CATALINA_BASE, and modify + accordingly the path specified in the docBase attribute of the Context + element +- Disabling both web applications by removing $CATALINA_BASE/webapps/admin.xml + and $CATALINA_BASE/webapps/manager.xml (5) Troubleshooting: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5166] - CATALINA_BASE config issues for RUNNING.txt
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5166. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5166 CATALINA_BASE config issues for RUNNING.txt [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 08:06 --- Fixed, thanks. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Using InstallAnywhere for Tomcat installer
Good/free advertising for zerog if installanywhere is used! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core ApplicationContext.java
remm02/04/24 01:39:53 Modified:catalina/src/share/org/apache/catalina/core ApplicationContext.java Log: - Fixes bug 6662. - The problem was that, given two context /foo and /foobar, doing ServletContext.getContext(/foobar) in context /foo would have returned context /foo instead of context /foobar because of the startsWith test. Now, the test is an equals. - This needs some testing, but the change looks safe. Revision ChangesPath 1.36 +5 -6 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/ApplicationContext.java Index: ApplicationContext.java === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/ApplicationContext.java,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- ApplicationContext.java 27 Feb 2002 19:16:16 - 1.35 +++ ApplicationContext.java 24 Apr 2002 08:39:53 - 1.36 @@ -1,7 +1,7 @@ /* - * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/ApplicationContext.java,v 1.35 2002/02/27 19:16:16 remm Exp $ - * $Revision: 1.35 $ - * $Date: 2002/02/27 19:16:16 $ + * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/ApplicationContext.java,v 1.36 2002/04/24 08:39:53 remm Exp $ + * $Revision: 1.36 $ + * $Date: 2002/04/24 08:39:53 $ * * * @@ -114,7 +114,7 @@ * * @author Craig R. McClanahan * @author Remy Maucherat - * @version $Revision: 1.35 $ $Date: 2002/02/27 19:16:16 $ + * @version $Revision: 1.36 $ $Date: 2002/04/24 08:39:53 $ */ public class ApplicationContext @@ -422,8 +422,7 @@ // Return the current context if requested String contextPath = context.getPath(); -if ((contextPath.length() 0) -(uri.startsWith(contextPath))) { +if ((contextPath.length() 0) (uri.equals(contextPath))) { return (this); } -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6662] - servlet context fails if webapp name smaller version of another webapp
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6662. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6662 servlet context fails if webapp name smaller version of another webapp [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 08:40 --- Fixed in the 04/25 nightly build. This change will be ported to the 4.0.x branch. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Jk2: scoreboard format and semantics.
To keep things simple and use existing code, I think we should use the current marshalling/demarshalling code ( ajp13 ) to store/get informations from each slot. Why not just use native read/write on int/strings ? If we treat shm as a byte[] and use java code to process it - we can run into byte order problems, aligment, etc. It's quite tricky to predict how a struct will be layed out. Ok, I understand why, you're thinking in-process tomcats whereas I was thinking out-process tomcats (and even on differents machines) +1 so for ajp marshalling use -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
var retrieval from checkbox (with single name)
Hi, I wish to retrieve / store values of multiple checkboxes checked in the previous page. The problem here is I dont know how many boxes (a dynamic amount of them is output), and the checkboxes must have the same name. I wish to do something similar to Hotmail where I check an amount of checkboxes, then manipulate the values in the next page. The reason they all must be name the same - chkboxarray - is to allow a Hotmail style 'check-all', 'uncheck all' facility (below). The reason for this being that the check boxes checked contain email recipient ID's (JSP) where I am concatonating email address as a String value to add to a BCC field. I have tried retrieving and storing in an array but all I get is the value for the first checkbox. Any ideas how I can achieve what I'm trying to do while retrieveing the values with a single checkbox name, or maybe there's someone with a better solution out there?! Perhaps I need to assign the checkboxes different names, and edit the JS? (I dont know how to do this)! Thanks for all input Paul. script language= JavaScript function modify_boxes(to_be_checked,total_boxes){ for ( i=0 ; i total_boxes ; i++ ) { if (to_be_checked) { document.forms[0].chkboxarray[i].checked=true; } else { document.forms[0].chkboxarray[i].checked=false; } } } /script -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: AJP connector silent when RealPlayer is client.
After investigation of virtually every other possibility, it seems that mod_jk (AJP 1.3) fails to respond to queries that originate from RealPlayer (v8 and RealOne on win32 tested). The platform is RedHat Linux, running Apache 1.3 with mod_jk to Tomcat 4.0.1 (mod_jk from 4.0.3). Any other request to Apache from any other client works perfectly. When RealPlayer requests a URL in a directory handled by AJP, it accepts the connection and the request, but returns no data and holds the connection open. Could you try with a more recent release of TC 4.0 (4.0.3 for example) What happen if you replace TC 4.0.1 with a TC 3.3.1 (for test purposes :) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using InstallAnywhere for Tomcat installer
Don't want to do the OSS passionaria but we should try to use only OSS tools on Apache. NSIS is OSS so keep. For Free Java installer we have : IZPack : http://www.izforge.com/izpack/ VAInstall : http://vainstall.sourceforge.net/ FreeInstaller : http://www.xenonsoft.demon.co.uk/products/freeinstaller/index.html -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Continue, select one of the above, and then
Care - The original text contains a virus Sender of the infected attachment: issa Subject of the message: Continue, select one of the above, and then One or more attachments were quarantined. Attachment Vvyc.exe was Quarantined for the following reasons: Virus W32.Klez.H@mm was found. Kind Regards, Mark Gash Consultant TriSystems Ltd. 020 7264 0440 [EMAIL PROTECTED] -Original Message- From: issa [mailto:[EMAIL PROTECTED]] Sent: 24 April 2002 10:35 To: [EMAIL PROTECTED] Subject: Continue, select one of the above, and then File: Quarantined Attachment.txtFile: MEULAWAR.HTM --- The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. TriSystems Ltd. cannot accept liability for statements made which are clearly the senders own. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8263] - url-pattern easy to circumvent
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8263. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8263 url-pattern easy to circumvent [EMAIL PROTECTED] changed: What|Removed |Added Priority|Other |High Summary|url-pattern easyly to |url-pattern easy to |circumvent |circumvent Version|3.2.1 Final |3.2.3 Final -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7575] - Throwing UnavailableException in JSP's init disables JSP servlet
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7575. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7575 Throwing UnavailableException in JSP's init disables JSP servlet [EMAIL PROTECTED] changed: What|Removed |Added Component|Catalina|Jasper 2 --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 11:10 --- Catalina does not create temporary servlets to do this, so it's up to Jasper to handle the JSP page availability status. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Using InstallAnywhere for Tomcat installer
Don't want to do the OSS passionaria but we should try to use only OSS tools on Apache. NSIS is OSS so keep. Sure, no problem. The licensing terms seems ok to me, so I wanted to see if the community was ok about it (apparently not). So even if this installer is provided in addition to other OSS based installers, it's not ok ? Since when is this project refusing contributions from companies, BTW ? There's no explicit endorsement required, and no blinking ZeroG ad we'll have to put anywhere. They'll also provide the installer script. Note: Did you notice what the httpd project was using for its installers (http://www.apache.org/dist/httpd/binaries/win32/apache_2.0.35-win32-x86-no_ ssl.msi) ? Doesn't seem OSS to me ... Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using InstallAnywhere for Tomcat installer
NSIS is OSS so keep. Sure, no problem. The licensing terms seems ok to me, so I wanted to see if the community was ok about it (apparently not). So even if this installer is provided in addition to other OSS based installers, it's not ok ? Since when is this project refusing contributions from companies, BTW ? There's no explicit endorsement required, and no blinking ZeroG ad we'll have to put anywhere. They'll also provide the installer script. I don't refuse anything, just expose that I'd rather like an OSS Java installer. Note: Did you notice what the httpd project was using for its installers (http://www.apache.org/dist/httpd/binaries/win32/apache_2.0.35- win32-x86-no_ ssl.msi) ? Doesn't seem OSS to me ... Yes you're right and I was thinking at them will clicking 'send button' for my previous email (I was hopping you didn't find it too quickly ;) ). Yes, Apache HTTP team use M$ stuff for 1.3 and 2.0 but I'm not a commiter there so... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8459] New: - Tomcat Crash or stuck without DISPLAY
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8459. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8459 Tomcat Crash or stuck without DISPLAY Summary: Tomcat Crash or stuck without DISPLAY Product: Tomcat 4 Version: 4.0 Beta 1 Platform: Sun OS/Version: Other Status: NEW Severity: Critical Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Being running from terminal window without DISPLAY environmental variable defned properly, (that is when DISPLAY points to closed display, for example), catalina (version 4.0.1) sometimes gets stuck or even crashes. In both cases there is the following line in catalina's output: X connection to hostanme:0.0 broken (explicit kill or server shutdown). Can anybody explain me, why catalina's processes need DISPLAY variable to be properly defined ? Thanks -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8459] - Tomcat Crash or stuck without DISPLAY
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8459. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8459 Tomcat Crash or stuck without DISPLAY [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 11:37 --- If you run it in an XTerm, maybe. This is a user question, please post it in tomcat-user. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Using InstallAnywhere for Tomcat installer
I don't refuse anything, just expose that I'd rather like an OSS Java installer. (The main advantage is that we wouldn't have to build the script, since they would be contributing one, but I'm repeating myself) Yes you're right and I was thinking at them will clicking 'send button' for my previous email (I was hopping you didn't find it too quickly ;) ). Lol. I'm using it, so I know very well whet they're using ;-) Yes, Apache HTTP team use M$ stuff for 1.3 and 2.0 but I'm not a commiter there so... M$ installer tech, built with InstallShield :) For what they're doing with the installer, they could use NSIS instead IMO. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet JspServlet.java
remm02/04/24 04:58:00 Modified:jasper2/src/share/org/apache/jasper/resources messages.properties jasper2/src/share/org/apache/jasper/servlet JspServlet.java Log: - Fix bug 7575. - Jasper now keeps track of the availability status of each individual JSP page. Revision ChangesPath 1.2 +2 -1 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties Index: messages.properties === RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- messages.properties 28 Mar 2002 18:46:19 - 1.1 +++ messages.properties 24 Apr 2002 11:58:00 - 1.2 @@ -1,4 +1,4 @@ -# $Id: messages.properties,v 1.1 2002/03/28 18:46:19 kinman Exp $ +# $Id: messages.properties,v 1.2 2002/04/24 11:58:00 remm Exp $ # # Default localized string information # Localized this the Default Locale as is en_US @@ -22,6 +22,7 @@ jsp.error.not.impl.plugin=Internal error: plugin not implemented jsp.error.not.impl.forward=Internal error: forward not implemented jsp.error.not.impl.include=Internal error: include not implemented +jsp.error.unavailable=JSP has been marked unavailable jsp.error.usebean.missing.attribute=useBean: id attribute missing or misspelled jsp.error.usebean.missing.type=useBean ({0}): Either class or type attribute must be \ specified: 1.4 +28 -0 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServlet.java Index: JspServlet.java === RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServlet.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- JspServlet.java 24 Apr 2002 02:21:05 - 1.3 +++ JspServlet.java 24 Apr 2002 11:58:00 - 1.4 @@ -60,6 +60,7 @@ import javax.servlet.ServletConfig; import javax.servlet.ServletException; import javax.servlet.SingleThreadModel; +import javax.servlet.UnavailableException; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; @@ -127,6 +128,7 @@ URLClassLoader loader = null; JspCompilationContext ctxt = null; String outDir = null; +long available = 0L; JspServletWrapper(String jspUri, boolean isErrorPage) { this.jspUri = jspUri; @@ -203,6 +205,14 @@ throws ServletException, IOException, FileNotFoundException { try { + +if ((available 0L) (available Long.MAX_VALUE)) { +response.setDateHeader(Retry-After, available); +response.sendError +(HttpServletResponse.SC_SERVICE_UNAVAILABLE, + Constants.getString(jsp.error.unavailable)); +} + loadIfNecessary(request, response); // If a page is to only to be precompiled return. @@ -219,6 +229,24 @@ theServlet.service(request, response); } +} catch (UnavailableException ex) { +String includeRequestUri = (String) +request.getAttribute(javax.servlet.include.request_uri); +if (includeRequestUri != null) { +// This file was included. Throw an exception as +// a response.sendError() will be ignored by the +// servlet engine. +throw ex; +} else { +int unavailableSeconds = ex.getUnavailableSeconds(); +if (unavailableSeconds = 0) +unavailableSeconds = 60;// Arbitrary default +available = System.currentTimeMillis() + +(unavailableSeconds * 1000L); +response.sendError +(HttpServletResponse.SC_SERVICE_UNAVAILABLE, + ex.getMessage()); + } } catch (FileNotFoundException ex) { String includeRequestUri = (String) request.getAttribute(javax.servlet.include.request_uri); -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7575] - Throwing UnavailableException in JSP's init disables JSP servlet
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7575. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7575 Throwing UnavailableException in JSP's init disables JSP servlet [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 11:58 --- This should be fixed in 04/25 nightly. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RELEASE-PLAN-4.1.txt
remm02/04/24 04:59:03 Modified:.RELEASE-PLAN-4.1.txt Log: - Update bug status. Revision ChangesPath 1.4 +1 -6 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt Index: RELEASE-PLAN-4.1.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- RELEASE-PLAN-4.1.txt 23 Apr 2002 18:32:11 - 1.3 +++ RELEASE-PLAN-4.1.txt 24 Apr 2002 11:59:03 - 1.4 @@ -1,4 +1,4 @@ -$Id: RELEASE-PLAN-4.1.txt,v 1.3 2002/04/23 18:32:11 remm Exp $ +$Id: RELEASE-PLAN-4.1.txt,v 1.4 2002/04/24 11:59:03 remm Exp $ Release Plan for Apache Tomcat 4.1 == @@ -61,14 +61,11 @@ Catalina -5166 CATALINA_BASE config issues for RUNNING.txt 5735 HTTP connector running out of processors under heavy load 5829 StandardManager needs to cope with sessions throwing exception in read/write 5895 Not all sessions receives HttpSessionListener.sessionDestroyed(event) using FileStore -6662 servlet context fails if webapp name smaller version of another webapp -7575 Throwing UnavailableException in JSP's init disables JSP servlet 7656 Webapplications deployed using PUT don't survive a tomcat restart 8087 HttpSessionAttributeListener.attributeRemoved() not working with URLRewriting @@ -83,9 +80,7 @@ 5793 variable element in tld with TagExtraInfo class 5903 version attribute in jsp:root 6196 jsp:forward should trigger IllegalStateException when buffer flushed -6907 jsp compiler not synchronized 6908 JavaCompiler interface setOutputDir always called with null parameter -6909 source parameter to compile method called with mangled file path 7007 Invalid names in web.xml generated by JspC for top-level JSP pages 7059 Jasper compiler holds pointers to jars in WEB-INF/lib: cannot delete 7989 jsp:setProperty and jsp:getProperty ignore information from -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
NoClassDefFoundError
Hi, I'm using Apache Tomcat 4.0.3 (OS - Win2000). I've encountered the problem of - java.lang.NoClassDefFoundError: oracle/jdbc/driver/OracleDriver I can successfully compile the java file which is basically for DB utility and the way I'm loading the oracle driver is mentioned below - (Line no. 25) DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver()); But while running the application through the tomcat it's throwing the exception and pointing towards the line 25 of the java file. I've already included the classes12.zip classes111.zip file under the classpath (jdk1.3.1). Any suggestion? - Samit THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED ONLY FOR THE ADDRESSEE and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are notified that any dissemination, distribution or copy of this communication is strictly Prohibited. If you have received this message by error, please notify us immediately, return the original mail to the sender and delete the message from your system. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8024] - Can't include entities in web.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8024. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8024 Can't include entities in web.xml --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 12:18 --- You are right, however I was talking about enhancing the Digester.parse(File) method. I have now submitted this as a separate Bug 8461 reported against the Commons/Digester/Nightly Build, together with a patch. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat build.xml
keith 02/04/24 05:26:23 Modified:.build.xml Log: Fix build with the http11 connector Revision ChangesPath 1.177 +1 -1 jakarta-tomcat/build.xml Index: build.xml === RCS file: /home/cvs/jakarta-tomcat/build.xml,v retrieving revision 1.176 retrieving revision 1.177 diff -u -r1.176 -r1.177 --- build.xml 18 Apr 2002 13:57:59 - 1.176 +++ build.xml 24 Apr 2002 12:26:23 - 1.177 @@ -263,7 +263,7 @@ property name=tomcat33.home value=${basedir}/build/tomcat/ /ant -ant dir=${jakarta-tomcat-connectors}/http11 / +ant dir=${jakarta-tomcat-connectors}/http11 inheritAll=false / ant dir=${jakarta-tomcat-connectors}/jk target=build-jk property name=tomcat33.home value=${basedir}/build/tomcat/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8465] New: - classpath.sh overwrites existing java_opts settings
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8465. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8465 classpath.sh overwrites existing java_opts settings Summary: classpath.sh overwrites existing java_opts settings Product: Tomcat 4 Version: 4.0.3 Final Platform: Other OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The documentation for catalina.sh claims that java options for tomcat execution can be defined using the JAVA_OPTS environment variable. However any existing values are overwritten by classpath.sh:30. It would also be useful to document the use of the setenv.sh shell script for defining environment variables -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat 4.x cluster
A must read from Filip ;) http://www.theserverside.com/resources/article.jsp?l=Tomcat - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: NoClassDefFoundError
I've already included the classes12.zip classes111.zip file under the classpath (jdk1.3.1). Any suggestion? 2 suggestions: 1) Use tomcat-user for this kind of messages.. Thanks.. 2) None of Tomcat versions ( 3.x or 4.x ) reads zip files from the jar repositories ( web-inf/lib nor any of the server repositiories ) ( as the Servlet Spec says ), so rename your *.zip files to *.jar Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Possible bugs in jasper Parser/EventListener interaction
Affected versions: Tomcat 4 version up to 4.0.3 Possible bugs: 1) handleComment is never called on the EventListener handleComment should be called as far as i understand because the parser can't really know if the code-gen backend uses the comments. diff for Parser.java @@ -440,7 +440,10 @@ throw new ParseException(Constants.getString(jsp.error.unterminated, new Object[] { OPEN_COMMENT })); - parser.flushCharData(parser.tmplStart, parser.tmplStop); + listener.setTemplateInfo(parser.tmplStart, parser.tmplStop); + listener.handleComment(start, stop,reader.getChars(start, stop)); + return true; } return false; 2) handleTagBegin is called with hasBody == true when a prefix:myTag / is encountered (similar to 2622). I'm not entirely sure this is a bug, it all depends on what _exactly_ the intended use of the hasBody parameter in handleTagBegin and handleTagEnd in Parser.java, my assumption is that it is used to determine if a the tag has indeed a body. If so then it should be false when the codepath below is invoked. Because an empty-element tag can't have a body. diff for Parser.java @@ -838,9 +841,9 @@ reader.advance(CLOSE_1.length()); listener.setTemplateInfo(parser.tmplStart, parser.tmplStop); listener.handleTagBegin(start, reader.mark(), attrs, prefix, - shortTagName, tli, ti, true); + shortTagName, tli, ti, false); listener.handleTagEnd(start, reader.mark(), prefix, - shortTagName, attrs, tli, ti, true); + shortTagName, attrs, tli, ti, false); } else { // Body can be either // - empty In the code handling the start-tag and end-tag case the following code is excuted: String bodyString = new String(reader.getChars(bodyStart, bodyStop)); hasBody = (bodyString.length() 0); Which seems to suggest that my assumption regarding the meaning of hasBody is correct. Resolution: Se patch below. /Regards Mikael Andersson --- c:\src\jakarta-tomcat-4.0.1-src\jasper\src\share\org\apache\jasper\compiler\Parser.java Sun Oct 14 11:14:32 2001 +++ +c:\src\jakarta-tomcat-4.0.1-src-changed\jasper\src\share\org\apache\jasper\compiler\Parser.java + Thu Apr 18 20:34:40 2002 @@ -440,7 +440,10 @@ throw new ParseException(Constants.getString(jsp.error.unterminated, new Object[] { OPEN_COMMENT })); - parser.flushCharData(parser.tmplStart, parser.tmplStop); + listener.setTemplateInfo(parser.tmplStart, parser.tmplStop); + listener.handleComment(start, stop,reader.getChars(start, stop)); + return true; } return false; @@ -838,9 +841,9 @@ reader.advance(CLOSE_1.length()); listener.setTemplateInfo(parser.tmplStart, parser.tmplStop); listener.handleTagBegin(start, reader.mark(), attrs, prefix, - shortTagName, tli, ti, true); + shortTagName, tli, ti, false); listener.handleTagEnd(start, reader.mark(), prefix, - shortTagName, attrs, tli, ti, true); + shortTagName, attrs, tli, ti, false); } else { // Body can be either // - empty -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8468] New: - getPathInfo() grows with each self-invocation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8468. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8468 getPathInfo() grows with each self-invocation Summary: getPathInfo() grows with each self-invocation Product: Tomcat 4 Version: 4.0.3 Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have a servlet that contains a form to invoke itself. The PathInfo grows longer each invokation like PathInfo =/MyServlet/MyServlet/MyServlet/MyServlet/MyServlet/MyServlet/trigger wheras PathInfo only should be /trigger The form is String tServletName=getServletConfig().getServletName(); out.println(pform action=\+tServletName+/trigger\); -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8468] - getPathInfo() grows with each self-invocation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8468. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8468 getPathInfo() grows with each self-invocation --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 14:11 --- Created an attachment (id=1684) Servlet that displays the behaviour -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/xdocs resources.xml
remm02/04/24 07:11:18 Modified:xdocsresources.xml Log: - Add clustering article by Filip Hanik and the Tomcat book project to the list. Revision ChangesPath 1.2 +9 -2 jakarta-tomcat-site/xdocs/resources.xml Index: resources.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs/resources.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- resources.xml 4 Apr 2002 05:20:23 - 1.1 +++ resources.xml 24 Apr 2002 14:11:18 - 1.2 @@ -19,8 +19,12 @@ section name=Books ul -libApache Jakarta-Tomcat/b, by James Goodwillbr/ -iAPress/i +li + bApache Jakarta-Tomcat/b, by James Goodwillbr/ + iAPress/i +/li +li + ba href=http://tomcatbook.sourceforge.net/;Tomcat Book Project/a/b /li /ul @@ -31,6 +35,9 @@ ul li ba href=http://www.ubeans.com/tomcat/index.html;Apache 1.3.23 + Tomcat 4.0.2 + Load Balancing/a/b, by Pascal Forget +/li +li + ba href=http://www.theserverside.com/resources/article.jsp?l=Tomcat;Clustering Technologies - In Memory Session Replication in Tomcat 4/a/b, by Filip Hanik /li /ul -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-site/xdocs resources.xml
Thanks Remy ;) - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 4:11 PM To: [EMAIL PROTECTED] Subject: cvs commit: jakarta-tomcat-site/xdocs resources.xml remm02/04/24 07:11:18 Modified:xdocsresources.xml Log: - Add clustering article by Filip Hanik and the Tomcat book project to the list. Revision ChangesPath 1.2 +9 -2 jakarta-tomcat-site/xdocs/resources.xml Index: resources.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs/resources.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- resources.xml4 Apr 2002 05:20:23 - 1.1 +++ resources.xml24 Apr 2002 14:11:18 - 1.2 @@ -19,8 +19,12 @@ section name=Books ul -libApache Jakarta-Tomcat/b, by James Goodwillbr/ -iAPress/i +li + bApache Jakarta-Tomcat/b, by James Goodwillbr/ + iAPress/i +/li +li + ba href=http://tomcatbook.sourceforge.net/;Tomcat Book Project/a/b /li /ul @@ -31,6 +35,9 @@ ul li ba href=http://www.ubeans.com/tomcat/index.html;Apache 1.3.23 + Tomcat 4.0.2 + Load Balancing/a/b, by Pascal Forget +/li +li + ba href=http://www.theserverside.com/resources/article.jsp?l=Tomc atClustering Technologies - In Memory Session Replication in Tomcat 4/a/b, by Filip Hanik /li /ul -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8468] - getPathInfo() grows with each self-invocation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8468. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8468 getPathInfo() grows with each self-invocation [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Component|Unknown |Catalina Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 14:18 --- Using the servlet name won't give the right result. Also, since the FORM target is relative to the current URL, that's how the nexting occurs. The bug database is not meant to be used to solv user problems. Please use tomcat-user or IRC for that. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8470] New: - missing content-length from the header, Apache/Tomcat/AJP12 Connector spins out of control
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8470. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8470 missing content-length from the header, Apache/Tomcat/AJP12 Connector spins out of control Summary: missing content-length from the header, Apache/Tomcat/AJP12 Connector spins out of control Product: Tomcat 3 Version: 3.2.2 Final Platform: Sun OS/Version: Solaris Status: NEW Severity: Critical Priority: Other Component: Connectors AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The following defect occured several months ago, when we deployed Tomcat 3.2.2 (beta 4) w/ AJP12 Connector in production environment, We are now considering an upgrade to Tomcat 4 with AJP13 (AJP14?) connector but it is imperative to us, if the following defect was solved, by ree- engineering or patch to either the Connector or the Container. What follows is an email send out to the Tomcat dev newsgroup: -- it will be best if I describe our configuration at first: We are running Solaris 7, Tomcat 3.2.2 b4 (beta 4) + AJP12 Connector (Tomcat configured with max of 500 threads), JVM: Sun 1.3.0_02 Hot Spot Native Threads, Apache 1.3.19 (max of 1024 child processes) We have had substantial traffic on our server (we have 7 servers load balanced with the configuration specified above) We found that if the incoming HTTP request has content-length missing from the header, and the request gets channeled via the AJP12 connector to the Tomcat and the servlet, it appears that all subsequent request are causing AJP12 connections to raise (All in ESTABLISHED mode) and Tomcat refuses to process any more request , eventually eating up great deal of CPU time, we needed to do restart and both Apache and the Tomcat to recover from this condition. We have then decided to bypass all requests with the content-length missing in the Ajp12ConnectionHandler.java int contentLength = reqA.getMimeHeaders().getIntHeader(content- length); if (contentLength != -1) { BufferedServletInputStream sis = (BufferedServletInputStream)reqA.getInputStream(); sis.setLimit(contentLength); } + else { + resA.finish(); + socket.close(); + return; + } contextM.service( reqA, resA ); //resA.finish(); // is part of contextM ! socket.close(); } catch (Exception e) { // XXX // this isn't what we want, we want to log the problem somehow System.out.println(HANDLER THREAD PROBLEM: + e); e.printStackTrace(); } Note that in the above socket.close() is not executed when an exception is thrown in the service method we are considering adding a finally clause to handle such a case: i.e contextM.service( reqA, resA ); //resA.finish(); // is part of contextM ! - socket.close(); } catch (Exception e) { // XXX // this isn't what we want, we want to log the problem somehow System.out.println(HANDLER THREAD PROBLEM: + e); e.printStackTrace(); } + } finally() { + if (socket != null) + socket.close(); + } - I believe that potential offending code could in the servlet application that tries to read input stream request.getInputStream() without the content-length following is what the servlet code looks like: private int readInputStream(HttpServletRequest request) { int clientDayOfYear = 0; try { InputStreamReader isr=new InputStreamReader(request.getInputStream()); BufferedReader br=new BufferedReader(isr); clientDayOfYear = new Integer(br.readLine().toString()).intValue(); isr.close(); isr=null; br.close(); br=null; } catch (IOException e) { clientDayOfYear=0; } return clientDayOfYear; } We know that our change to the Tomcat code is temporary at best (it allows us to go on!) I am looking for the feedback on the quality of our code change as well as maybe to a deeper reasons why content-length missing from the header together with request.getInputStream() would cause Apache/AJP12 to have connections open (All in ESTABLISHED mode) and eventually eat up all available CPU resources -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For
Re: Using InstallAnywhere for Tomcat installer
+1 from me. Having a cross-platform and consistent installer would be good for tomcat. My only concern - I hope the 'one licence' would cover all versions of tomcat and more than one release manager ( and maybe it can be assigned to Mr. Gump and automated ). Costin On Tue, 23 Apr 2002, Remy Maucherat wrote: I have been contacted by Zero G Software with the possibility of using InstallAnywhere for making a Tomcat installer. Tomcat currently uses NSIS for the Windows installer, and while it is powerful enough to get the job done, it is not multiplatform, and has a few annoying functional limitations. However, there's a major advantage to using NSIS, because it is open-source software. To get around this, Zero G has offered to donate a license of InstallAnywhere to Tomcat, as well as installer code. If we decide to use InstallAnywhere, it would probably be a good idea to put the installer code in a separate repository (jakarta-tomcat-installer ?), and also move the NSIS script there. The rationale is that while a NSIS install script is very small (one file, plus a few resources), an InstallAnywhere script is made of a significant number of Java classes. Of course, I don't see a reason for stopping to use the (already working) NSIS script, at least in the immediate future. Comments / votes ? Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using InstallAnywhere for Tomcat installer
I believe Apache httpd server is using MSI and InstallShield - and this is neither cross-ASF nor free. I'm not sugesting an exclusive deal with InstallAnywhere - we can try one of the OSS installers in parallel ( if someone has the time to do so ) and if they provide the same features, we'll just default to the free one. I'll change my vote to +0 - I don't have time for that, but if someone else wants to spend the time with a better cross platform installer - I think he should be able to choose the tool he wants. Costin On Wed, 24 Apr 2002, GOMEZ Henri wrote: Don't want to do the OSS passionaria but we should try to use only OSS tools on Apache. NSIS is OSS so keep. For Free Java installer we have : IZPack : http://www.izforge.com/izpack/ VAInstall : http://vainstall.sourceforge.net/ FreeInstaller : http://www.xenonsoft.demon.co.uk/products/freeinstaller/index.html -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Using InstallAnywhere for Tomcat installer
+1 from me. Having a cross-platform and consistent installer would be good for tomcat. My only concern - I hope the 'one licence' would cover all versions of tomcat and more than one release manager ( and maybe it can be assigned to Mr. Gump and automated ). That's brilliant. This way, if Zero G agrees, it would also be available for use by other Apache projects (therefore addressing Jon's problem). Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
VIRUS: sent by issa@infotel.opt.mr = W32Klez.gen@mm
Heads up on this virus. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Continue, select one of the above, and then
That is probably a virus! issa wrote: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
More W32Klez.gen@mm Viruses: mnavarro@bdoc.com
This will be my last post of these viruses, since they seem to be proliferating here. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[VOTE] Release Plan for Apache Tomcat 4.1
I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
[X] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: I will try and get the NetWare plugins for the JK2 stuff built and posted. Mike Anderson -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Using InstallAnywhere for Tomcat installer
GOMEZ Henri wrote: I don't refuse anything, just expose that I'd rather like an OSS Java installer. I've recently been pointedly reminded that I'm not even a committer, but as the project guidelines encourage developers to comment and cast a nonbinding vote, I'll put on my flameproof suite and agree that I would prefer an OSS installer if at all possible. Using propriatary code has drawbacks like: - Unless the license is more liberal than I suspect, nobody but official Apache projects will be able to use the installer. Sometimes non-Apache projects do use Apache code, that's sort of half the advantage of being Open Source. Diluting that advantage would be a shame. - Contributing time and $$$ to a project that's being used as an advertisement for a potential competitor (that isn't contributing source code) is troubling. In this case not enough to make me (or probably anyone else) leave, but its annoying. If they want to participate, why don't they make plans to donate source code like everyone else? - If you aren't on the official list of supported platforms, you're hosed. With an OSS solution, a frustrated user of an obscure platform can make it work and then contribute the solution back to the community. - Although perhaps a verboten topic for discussion, there's the whole Open Source thing. Using a commercial installer if Open Source options are available is troubling from a philisophical standpoint. If you really buy into the advantage of Open Source, why dilute those advantages? If there's currently not an OSS solution available, then in the interest of expedience, I withdraw any objections. Which sounds sort of funny since it's nonbinding anyway, but what the heck. (Any personal email on this topic to /dev/null, keep it public please.) -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
On Wed, 24 Apr 2002, Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [X] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using InstallAnywhere for Tomcat installer
InstallAnywhere has both binary and byte-code installers. In fact the binary installers is just a self-estracting executable with byte-code. So in essence it works on any platform that has a JVM. InstallAnywhere is stable, very easy to use both as an end-user and as a build manager. I'm not going to get into a philosophical discussion about why to use OSS, but in the case of installers, InstallAnywhere is the best for Java apps, regardless of whether its proprietary or not. ~~K Kevin Z Grey Software Engineer -Original Message- From: Christopher K. St. John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 12:07 PM To: [EMAIL PROTECTED] Subject: Re: Using InstallAnywhere for Tomcat installer GOMEZ Henri wrote: I don't refuse anything, just expose that I'd rather like an OSS Java installer. I've recently been pointedly reminded that I'm not even a committer, but as the project guidelines encourage developers to comment and cast a nonbinding vote, I'll put on my flameproof suite and agree that I would prefer an OSS installer if at all possible. Using propriatary code has drawbacks like: - Unless the license is more liberal than I suspect, nobody but official Apache projects will be able to use the installer. Sometimes non-Apache projects do use Apache code, that's sort of half the advantage of being Open Source. Diluting that advantage would be a shame. - Contributing time and $$$ to a project that's being used as an advertisement for a potential competitor (that isn't contributing source code) is troubling. In this case not enough to make me (or probably anyone else) leave, but its annoying. If they want to participate, why don't they make plans to donate source code like everyone else? - If you aren't on the official list of supported platforms, you're hosed. With an OSS solution, a frustrated user of an obscure platform can make it work and then contribute the solution back to the community. - Although perhaps a verboten topic for discussion, there's the whole Open Source thing. Using a commercial installer if Open Source options are available is troubling from a philisophical standpoint. If you really buy into the advantage of Open Source, why dilute those advantages? If there's currently not an OSS solution available, then in the interest of expedience, I withdraw any objections. Which sounds sort of funny since it's nonbinding anyway, but what the heck. (Any personal email on this topic to /dev/null, keep it public please.) -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7686] - Issue with pathInfo in complex include() scenarios
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7686. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7686 Issue with pathInfo in complex include() scenarios [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 16:21 --- I think your test is incorrect. Your included servlet can access the path information of the outer request, and has access to the included paths through the attributes (which your servlet is never using). If you were doing the includes based on the pathInfo attribute, it apparently would be working ok. Note: The fix for bug 8092 may be needed for this to work (only available in the nightlies at the moment). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. And what do we do with 4.0? I still have problems with resources and lifecycles there and no enough time to fix them. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] Release Plan for Apache Tomcat 4.1
ballot [X] +1 I approve this plan, and will help Usual rpm packaging, connector stuff for Linux with/without eapi. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
+1 Costin On Wed, 24 Apr 2002, Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Using InstallAnywhere for Tomcat installer
Kevin Grey wrote: So in essence it works on any platform that has a JVM. Nah, it only works fully on officially supported platforms. Which makes sense, because the whole advantage of using a good installer is that it paves over the nasty platform-specific install issues. There's a list at: http://www.zerog.com/products_ia_01.html The key words are Support for nearly every platform. InstallAnywhere is the best for Java apps, regardless of whether its proprietary or not. I won't argue, I've never heard a bad thing said about InstallAnywhere. But totally ignoring ethical issues is a bad long-term strategy. Certainly Tomcat wouldn't exist at all if it weren't for people considering some philisophical issues. Costin's suggestion to try it out in parallel with some of the Open Source options seemed pretty reasonable. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] Release Plan for Apache Tomcat 4.1
ballot [X] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Larry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8478] New: - Debugging information in HTML output
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8478. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8478 Debugging information in HTML output Summary: Debugging information in HTML output Product: Tomcat 4 Version: 4.0.1 Final Platform: Sun OS/Version: Solaris Status: NEW Severity: Blocker Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When using coyote connector, site looks very bad, because debugging information are displayed in generated HTML code. Here's exameple of HTTP output: body id=topBG leftmargin=0 topmargin=0 marginwidth=0 marginheight=0 script language=JavaScript src=/static_js/mm_functions.js/script HTTP/1.1 200 Date: Wed, 24 Apr 2002 16:45:43 GMT Server: Apache/1.3.23 (Unix) mod_jk/1.1.0 Connection: close Content-Type: text/html; charset=UTF-8 Definition of connector in server.xml: !--Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler acceptCount=10 debug=0 connectionTimeout=2/-- Maciej Mochol -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5735] - HTTP connector running out of processors under heavy load
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5735. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5735 HTTP connector running out of processors under heavy load --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 17:04 --- I would recommend that you dump the stack for all running threads when you experience this problem. This can help identify what is causing the problem. By reviewing the stack dump for each thread you can determine whether the problem is due to Tomcat or your application. On unix you do a kill -QUIT {tomcat java pid) to cause the thread stack's to be dumped to catalina .out. A Processor for Tomcat runs your application code, delays in your code can cause additional processor threads to be created to handle new requests. Possible application or configuration problems which can delay requests: Connection delays due to networked services such as a db. Connection delays due to running out of pooled resources. Thread synchronization deadlocks. A cascading affect where many new processors get created due to excessively long JVM Garbage Collections. start java with -verbose:gc to detect this. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Replacing WebappClassLoader
Volker Leidl wrote: I tried to configure tomcat 4.0.2 to use my own class loader implementation for web-app class loading. The documentation implies that this can be done by secifying a loaderClass attribute in my Context/Loader element in server.xml. Loader specifies an org.apache.catalina.Loader object, not an java.lang.ClassLoader. You'd need to do something like this: package com.distributopia.mtc; import java.io.*; import org.apache.catalina.*; import org.apache.catalina.loader.*; public class TestLoader extends WebappLoader { public TestLoader(ClassLoader parent) { super(parent); System.out.println(TestLoader.TestLoader(+parent+)); } public void setDebug(int debug) { System.out.println(TestLoader.setDebug(+debug+)); super.setDebug(debug); } public void start() throws LifecycleException { System.out.println(TestLoader.start()); // instead of super.start(), do your own thing here super.start(); } } Compile it, jar it up, copy it over to $TOMCAT_HOME/server/lib, and you're set. Sort of. Stepping through the code of org.apache.catalina.loader.WebappLoader (which i still want to use) I found out that the loaderClass Property does get set, but it seems to be ignored since org.apache.catalina.loader.WebappClassLoader gets instantiated explicitly (line 615-, cvs revision 1.12.2.5). Is this intended? Perhaps I missed something in the code. What the example above does is override the start() method. It just re-dispatches it to the original, but what you'd need to do is reimplement it to use your classloader, instead of the one WebAppClassLoader uses. This does not work. Actually, neither does my suggestion, at leat not on HEAD. I could have sworn it used to work, but maybe I just wasn't paying enough attention to the log messages. Anyway, running the above I get this: ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with TestLoader at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:374) I'll test further, but first I wanted to get some feedback on whether I've made some stupid mistake. I kinda sorta half suspect this is related to the way Tomcat hardcodes all the MBeans instead of generating them dynamically using reflection, but I'm very unsure about it. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
There are a few additional items I would like to see added. 1. Port my recent mod_jk/apache1.3 new features to mod_jk/Apache2.0 and to jk2 as costin requested. This makes those connectors for use with Apache more consistent. Ok. 2. Resolve a problem Craig mentioned with Context start/stop/reload where not all resources are removed/restarted such as Filters and Listeners. I don't see what you're talking about. If it's the problem with startup/shutdown order, then it has been fixed. 3. Metrics generated that document real performance improvements in Jasper 2 to justify releasing it with Tomcat 4.1. Even if it's not much faster, it is a lot more maintainable and tweakable in the long run. So to test it, we should release it. 4. Implement my recent proposal for jasper 2 so that it recognizes changes to dependent compile time included pages and recompiles the dependent JSP page. This is a frequent problem/question Tomcat users report. Ok. 5. Go through the bug reports and create a FAQ for frequent problems. Include this on the Tomcat site and with the distribution. I have already started work on the framework and some initial FAQ's. Ok. I also think the release schedule is too aggressive. I would like to hold off on a beta 1 until May 10, beta 2 May 24, RC 1 June 3. I'd say I hope it won't be needed, as the HEAD branch has recieved all the bugfixes the main branch had. From the get go, I'd say it should be reasonably stable. So at least to see where we are in terms of stability, I really want to cut a Beta 1 ASAP. If it turns out to be good, then the schedule indicated may be realistic. For example, one of the major new modules (the new HTTP/1.1 connector) has recieved separate testing through Coyote, and has been found to be solid. So I'm optimistic :) I am +1 for doing a release and will help. Thanks :) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PROPOSAL] jasper2 detection of compile time page include changes
+1 on the idea. With minor changes, we can also implement a compiler server that compiles out-of-date pages in the background thread. This would greatly improve the response time for accessing the pages, when recompilations are needed. Date: Wed, 24 Apr 2002 10:52:51 -0500 From: Glenn Nielsen [EMAIL PROTECTED] Subject: [PROPOSAL] jasper2 detection of compile time page include changes To: [EMAIL PROTECTED] MIME-version: 1.0 Content-transfer-encoding: 7bit X-Accept-Language: en Delivered-to: mailing list [EMAIL PROTECTED] Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N List-Post: mailto:[EMAIL PROTECTED] List-Subscribe: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Id: Tomcat Developers List tomcat-dev.jakarta.apache.org A common problem Tomcat users have is that Jasper does not detect when a compile time included file %@include file=...% changes so that it can recompile dependent JSP pages. This propsoal maps out a possible solution for this. Create a new class (JspDependency) which is used to store mapping of JSP pages to dependent compile time included files. This class will be created for each web application context and the data it depends upon serialized to a special file in the work directory on context stop, and read from that file on context startup. Proposed filename is JSP_DEPENDENCY.ser. Here is how this integrates into Jasper: On context start instantiate a JspDependency object and read in the dependencies from JSP_DEPENDENCY.ser. If there are dependencies, start a background thread which checks for changes in compile time included files once each 5-15 minutes. Perhaps make this configurable. If changes are detected, set flags for dependent JSP pages which are affected. Using a thread to accomplish this rather than having JSP Load do the dependency checks should reduce the request latency overhead for detecting these changes. The JSP Load method will call a method in JspDependency to determine whether the current page needs to be recompiled due to dependency changes. This will just be a quick test of a boolean, actual dependency checks are done by the background thread. The JSP page compiler will call a method in JspDependency to remove all dependencies for the current JSP page on compile start, then call an add method for each compile time include dependency found. After a JSP page compile has completed any changes to dependencies are written back out to the JSP_DEPENDENCY.ser file. Comments or suggestions? Regards, Glenn -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
On Wed, 24 Apr 2002, Remy Maucherat wrote: I'd say I hope it won't be needed, as the HEAD branch has recieved all the bugfixes the main branch had. From the get go, I'd say it should be reasonably stable. So at least to see where we are in terms of stability, I really want to cut a Beta 1 ASAP. If it turns out to be good, then the schedule indicated may be realistic. Besides testing done by people who download the nightly builds of Tomcat 4, the HEAD branch code is also the version of Tomcat used in the Java Web Services Developer pack EA1 and EA2 releases, so it has received a very large amount of extra testing both within Sun and from the many people who have downloaded and used the Pack (and that is a sizeable number). Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Replacing WebappClassLoader
Dear Tomcat Dev, Is there a website that have the instruction on how to connection Tomcat 4 with Apache 2? Please help. Made me running tomcat as module of apache. thanks -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 8:44 AM Subject: [VOTE] Release Plan for Apache Tomcat 4.1 I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. [X] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Replacing WebappClassLoader
Christopher K. St. John wrote: Loader specifies an org.apache.catalina.Loader object, not an java.lang.ClassLoader. You'd need to do something like this: Ack. You were talking about the loaderClass attribute, not the className attribute. I wasn't paying close enough attention, sorry. But what I suggested is probably still your best bet if you need to get this done without fixing WebappLoader to properly use the classLoader attribute. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
+1 Amy Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
PGP-keys issue on Tomcat 4.0.3 (via Webmaster)
Via webmaster, please check the Original Message that follows. Have fun, Paulo Gaspar -Original Message- From: Erik Agsjo [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: PGP-keys Hi. paranoia I just downloaded the tomcat 4.0.3 binaries for linux (mod_jk-01.so and mod_webapp.so) and decided to verify the signatures provided. They checked out fine, after I added the keys from the KEYS file to my keyring. I would be nice if these keys were available from a keyserver, I failed to find them anywhere. Also, if the keys were signed by someone else than the keyowner, the point of signing the binaries would be much improved. I mean, if someone has access to the distribution directory and replaces the binaries with copies containing evil trojans, it would be simple for that individual to replace the KEYS file and signatures as well. What is worse it that that the signature for the tgz (jakarta-tomcat-4.0.3.tar.gz) is bad. At least, that is what gpg (GnuPG) 1.0.6 says. /paranoia Thanks for you time, Erik Agsjo Noptec -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Problems with tomcat downloads for OS X (via Webmaster)
Via webmaster, please check the Original Message that follows. Have fun, Paulo Gaspar -Original Message- From: Gunnar Schomaker [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: starting problems with tomcat packages on os x Dear frinds, I hope you will forward my message to the matching place ;-) THX.:! I have downloaded the tomcat binaries for OS X and I was very confused during the installation process. I was guided by the following instruction link. http://developer.apple.com/internet/macosx/tomcat1.html and http://developer.apple.com/internet/macosx/tomcat2.html (very usefull links for servlet beginners like me ;-) now I know that the instructions are right, but something goes wrong during unpacking the binaries. At the download section I found the hint that there are problems with the current tar version on OS X Clients, so i used the stuffit expander. My installation result was that the webserver worked fine, but the JSP and Servlet Example part did not. It was hard for me to find out the the problem was a missing 's' in some file ending names. So I did'nt know if the problem was caused by StuffIt or by the archive on your webserver. I tried the version 4.0.1 and 4.0.3. They both have the same problem. Some class files have after unpacking a wrong ending (.clas and not .class). So it may be usfull to fix it, if it's caused by the archive, otherwise it may be usefull to give an other hint for OS X user. It's a new System and I can imagine that I'm not the only newbe-one ... I' hope the Information is usefull for you ... best regards from germany dipl. Inf. Gunnar Schomaker -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java JkMain.java
costin 02/04/24 12:45:09 Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java JkMain.java Log: Potential fix for 8478. Check if the response has been already commited, and don't recommit. Display a small info notice - COMMIT action shouldn't be called twice or after the first chunk. Revision ChangesPath 1.15 +39 -36 jakarta-tomcat-connectors/jk/java/org/apache/jk/server/JkCoyoteHandler.java Index: JkCoyoteHandler.java === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/server/JkCoyoteHandler.java,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- JkCoyoteHandler.java 23 Apr 2002 08:11:05 - 1.14 +++ JkCoyoteHandler.java 24 Apr 2002 19:45:09 - 1.15 @@ -239,47 +239,50 @@ if( actionCode==ActionCode.ACTION_COMMIT ) { org.apache.coyote.Response res=(org.apache.coyote.Response)param; -if( log.isInfoEnabled() ) -log.info(COMMIT sending headers + res + + res.getMimeHeaders() ); - - -C2BConverter c2b=(C2BConverter)res.getNote( utfC2bNote ); -if( c2b==null ) { -c2b=new C2BConverter( UTF8 ); -res.setNote( utfC2bNote, c2b ); -} - -MsgContext ep=(MsgContext)res.getNote( epNote ); -MsgAjp msg=(MsgAjp)ep.getNote( headersMsgNote ); -msg.reset(); -msg.appendByte(HandlerRequest.JK_AJP13_SEND_HEADERS); -msg.appendInt( res.getStatus() ); - -// s-b conversion, message -msg.appendBytes( null ); - -// XXX add headers - -MimeHeaders headers=res.getMimeHeaders(); -int numHeaders = headers.size(); -msg.appendInt(numHeaders); -for( int i=0; inumHeaders; i++ ) { -MessageBytes hN=headers.getName(i); -// no header to sc conversion - there's little benefit -// on this direction -c2b.convert ( hN ); -msg.appendBytes( hN ); +if( res.isCommited() ) { +if( log.isInfoEnabled() ) +log.info(Response already commited ); +} else { +if( log.isInfoEnabled() ) +log.info(COMMIT sending headers + res + + res.getMimeHeaders() ); + +C2BConverter c2b=(C2BConverter)res.getNote( utfC2bNote ); +if( c2b==null ) { +c2b=new C2BConverter( UTF8 ); +res.setNote( utfC2bNote, c2b ); +} + +MsgContext ep=(MsgContext)res.getNote( epNote ); +MsgAjp msg=(MsgAjp)ep.getNote( headersMsgNote ); +msg.reset(); +msg.appendByte(HandlerRequest.JK_AJP13_SEND_HEADERS); +msg.appendInt( res.getStatus() ); + +// s-b conversion, message +msg.appendBytes( null ); -MessageBytes hV=headers.getValue(i); -c2b.convert( hV ); -msg.appendBytes( hV ); +// XXX add headers + +MimeHeaders headers=res.getMimeHeaders(); +int numHeaders = headers.size(); +msg.appendInt(numHeaders); +for( int i=0; inumHeaders; i++ ) { +MessageBytes hN=headers.getName(i); +// no header to sc conversion - there's little benefit +// on this direction +c2b.convert ( hN ); +msg.appendBytes( hN ); + +MessageBytes hV=headers.getValue(i); +c2b.convert( hV ); +msg.appendBytes( hV ); +} +ep.setType( JkHandler.HANDLE_SEND_PACKET ); +ep.getSource().invoke( msg, ep ); } -ep.setType( JkHandler.HANDLE_SEND_PACKET ); -ep.getSource().invoke( msg, ep ); } else if( actionCode==ActionCode.ACTION_RESET ) { if( log.isInfoEnabled() ) log.info(RESET ); - } else
RE: Tomcat 4+Slide1.0.16+ISAPI Filter
Here is an excerpt of an email I sent Ignacio detailing some of the issues I am finding: Basically, it seems as though the entire issue is centered around authentication through the ISAPI Filter. I am thinking that the filter is also having trouble with: Webfolders - because it first sends a POST request. and Webdrive - because it first sends an OPTIONS request. -Original Message- From: Robert Priest Sent: Friday, April 19, 2002 4:12 PM To: 'Ignacio J. Ortega' Subject: Traces - Hitting ISAPI Filter from Remote Machine. In all of them [the requests], the url i was attempting to use was: http://priest10428/slide/test The only one that works from a remote machine is IE. USING IE questions and observations: Why does this one work while the others do not? Now, looking at the trace, IE sends a GET Request, and iis/isapi_redirect properly responds with the correct Realm Challenge Request. After that we put in our credentials and everything shows up fine. We can browse our directories perfectly. In WebDrive an OPTIONS request is first sent, which comes back with a 500 Server Error. In MS WebFolders, a POST Request (if you see the request, it looks wrong too) with an invalid url which brings up the wrong Challenge Request popup ( looks like the IIS Auth even though I have that turned off). USING WEBFOLDERS This one is strange. Althought the webfolders that I tried to set up was http://priest10428/slide/test , from the logs (isapi_redirect.log), it looks like somehow the filter is getting the wrong url from webfolders. Instead of the url above you see the following in the log: [Fri Apr 19 15:19:58 2002] [jk_isapi_plugin.c (708)]: HttpFilterProc started [Fri Apr 19 15:19:58 2002] [jk_isapi_plugin.c (758)]: In HttpFilterProc Virtual Host redirection of /priest10428/_vti_bin/shtml.dll/_vti_rpc and lastly, but MOST Importantly, WebDrive. USING WEBDRIVE 5.1 observation: Now webdrive is sending an OPTIONS Request, first. In the isapi_redirect.log the url looks correct. you see: [Fri Apr 19 16:07:00 2002] [jk_isapi_plugin.c (708)]: HttpFilterProc started [Fri Apr 19 16:07:00 2002] [jk_isapi_plugin.c (758)]: In HttpFilterProc Virtual Host redirection of /priest10428/slide/test [Fri Apr 19 16:07:00 2002] [jk_uri_worker_map.c (447)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Apr 19 16:07:00 2002] [jk_uri_worker_map.c (464)]: Attempting to map URI '/priest10428/slide/test' [Fri Apr 19 16:07:00 2002] [jk_uri_worker_map.c (570)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match [Fri Apr 19 16:07:00 2002] [jk_isapi_plugin.c (764)]: In HttpFilterProc test Default redirection of /slide/test [Fri Apr 19 16:07:00 2002] [jk_uri_worker_map.c (447)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Apr 19 16:07:00 2002] [jk_uri_worker_map.c (464)]: Attempting to map URI '/slide/test' [Fri Apr 19 16:07:00 2002] [jk_uri_worker_map.c (489)]: jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 - /slide/ [Fri Apr 19 16:07:00 2002] [jk_isapi_plugin.c (774)]: HttpFilterProc [/slide/test] is a servlet url - should redirect to ajp13 [Fri Apr 19 16:07:00 2002] [jk_isapi_plugin.c (785)]: HttpFilterProc fowarding original URI [/slide/test] [Fri Apr 19 16:07:00 2002] [jk_isapi_plugin.c (837)]: HttpFilterProc check if [/slide/test] is points to the web-inf directory which I believe is the correct chain of events, but the next line should read: HttpExtensionProc started but everything just stops right there and the what is returned is a 500 Server Error. It is as if IIS never calls the Extension (HttpExtensionProc() method). Well, that is what I have noticed. Does any of this raise an eyebrow with you? Please let me know if you would like me to try something else,or you have any idea. Thank you Robert. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:36 PM To: Tomcat Users List Subject: Re: Tomcat 4+Slide1.0.16+ISAPI Filter Has anyone else out there tried get the ISAPI filter working with slide 1.0.16 and Tomcat 4.0.x? I have been trying for a while with no success. It works in a browser, but I cannot get it to work with Win2k Webfolders or WebDrive 5.1. If anyone knows this to work or can offer any assistance I would appreciate it. WebDAV is extremely demending on sending data in the request, which is a problem when using the native connectors as this is usually the last thing which works. It has been reported that mod_jk works with Apache, but it is unclear how well it works with the IIS JK. Remy -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
On Wed, 24 Apr 2002, Glenn Nielsen wrote: There are a few additional items I would like to see added. 1. Port my recent mod_jk/apache1.3 new features to mod_jk/Apache2.0 and to jk2 as costin requested. This makes those connectors for use with Apache more consistent. mod_jk2 has lower priority - there is no chance it'll be 'release quality' in this time frame. I do hope to have it ready for a beta, but for 4.1 ( and 4.0.x, 3.3.x ) mod_jk1 remains the server connector. coyote-Jk2 is stable as a Ajp13/Socket connector - i.e. all that matter for mod_jk1. The Unix socket and all advanced features of jk2/java will not be 'release quality' either ( but with a bit of luck and some help from Nacho and maybe others we can have them working and beta-level). I also think the release schedule is too aggressive. I would like to hold off on a beta 1 until May 10, beta 2 May 24, RC 1 June 3. We could switch the numbering scheme to follow the 'original' idea - numbered milestones. Like Apache 2 is doing. Instead of beta1, RC1, etc - we'll just use 4.1.0, 4.1.1, etc - with the 'release quality' happening when everyone is happy. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Node.java PageDataImpl.java
kinman 02/04/24 14:12:53 Modified:jasper2/src/share/org/apache/jasper/compiler Node.java PageDataImpl.java Log: - Removed the static field in Node.java, because it is not thread safe. Instead rely on traversing the nodes to find the page root. Revision ChangesPath 1.7 +20 -35 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Node.java Index: Node.java === RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Node.java,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- Node.java 19 Apr 2002 20:35:01 - 1.6 +++ Node.java 24 Apr 2002 21:12:52 - 1.7 @@ -1,7 +1,7 @@ /* - * $Header: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Node.java,v 1.6 2002/04/19 20:35:01 kinman Exp $ - * $Revision: 1.6 $ - * $Date: 2002/04/19 20:35:01 $ + * $Header: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Node.java,v 1.7 2002/04/24 21:12:52 kinman Exp $ + * $Revision: 1.7 $ + * $Date: 2002/04/24 21:12:52 $ * * * @@ -85,11 +85,6 @@ protected Node parent; /** - * The root node of this page. - */ -private static Root currentRoot; - -/** * Constructor. * @param start The location of the jsp page * @param parent The enclosing node @@ -155,10 +150,6 @@ return parent; } -public Node getCurrentRoot() { - return currentRoot; -} - public int getBeginJavaLine() { return beginJavaLine; } @@ -176,25 +167,17 @@ } /** - * Warning: This method is valid only when used from the correct context, - * namely when the Root node for the current page has been visited first, - * and the proper bookkeeping (ttpushCurrentRoot/popCurrentRoot/tt) - * has been performed. - * * @return true if the current page is in xml syntax, false otherwise. */ public boolean isXmlSyntax() { - return currentRoot.isXmlSyntax(); -} - -public static void pushCurrentRoot(Root root) { - root.setParentRoot(currentRoot); - currentRoot = root; -} + Node r = this; + while (!(r instanceof Node.Root)) { + r = r.getParent(); + if (r == null) + return false; + } -public static Root popCurrentRoot() { - currentRoot = currentRoot.getParentRoot(); - return currentRoot; + return r.isXmlSyntax(); } /** @@ -237,6 +220,12 @@ Root(Attributes attrs, Mark start, Node parent) { super(attrs, start, parent); + + // Figure out and set the parent root + Node r = parent; + while ((r != null) !(r instanceof Node.Root)) + r = r.getParent(); + parentRoot = (Node.Root) r; } public void accept(Visitor v) throws JasperException { @@ -247,13 +236,13 @@ return false; } + /** + * @ return The enclosing root to this root. Usually represents the + * page that includes this one. + */ public Root getParentRoot() { return parentRoot; } - - public void setParentRoot(Root root) { - parentRoot = root; - } } /** @@ -860,17 +849,13 @@ } public void visit(Root n) throws JasperException { - Node.pushCurrentRoot(n); doVisit(n); visitBody(n); - Node.popCurrentRoot(); } public void visit(JspRoot n) throws JasperException { - Node.pushCurrentRoot(n); doVisit(n); visitBody(n); - Node.popCurrentRoot(); } public void visit(PageDirective n) throws JasperException { 1.2 +4 -9 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageDataImpl.java Index: PageDataImpl.java === RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageDataImpl.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- PageDataImpl.java 28 Mar 2002 18:46:16 - 1.1 +++ PageDataImpl.java 24 Apr 2002 21:12:52 - 1.2 @@ -1,7 +1,7 @@ /* - * $Header: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageDataImpl.java,v 1.1 2002/03/28 18:46:16 kinman Exp $ - * $Revision: 1.1 $ - * $Date: 2002/03/28 18:46:16 $ + * $Header: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageDataImpl.java,v 1.2
Tomcat4.0 crashes when servlet forwarding to itself
Hello, I just had a bug in one of my servlets. It was forwarding to itself. Not a big problem, but, it caused Tomcat to crash. This is the first time Tomcat crashed with me, so I'm really surprised. Code snippet: //adr is a String with the name of the servlet. RequestDispatcher dispatcher = context.getNamedDispatcher(adr); try{ dispatcher.forward(request, response); } catch(Exception e){ e.printStackTrace(); } Best regards, Roland -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PROPOSAL] New version numbering scheme
Costin has suggested to me in a private email that the Tomcat project could adopt the Apache 2 numbering scheme (starting with Apache Tomcat 4.1). I think this is a good idea. For the uninitiated, the numbering is: major.minor.build build_stability So for example, the first 4.1.x release would probably be numbered: Apache Tomcat 4.1.0 Alpha ballot [ ] Yes [ ] No /ballot (feel free to provide comments to justify your choice) I vote yes. If the opinion is that this is a good idea, I'll revise the release plan for 4.1 to reflect this change. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [PROPOSAL] New version numbering scheme
De: Remy Maucherat [mailto:[EMAIL PROTECTED]] Enviado el: miércoles 24 de abril de 2002 23:41 Which will be the rules to advance the build numbers? Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PROPOSAL] New version numbering scheme
Which will be the rules to advance the build numbers? The method in httpd land seems to be once every 1-2 weeks, as long as there are significant changes. Sometimes, one major change (minor security fix or higher priority fix) is enough to cause a build number advance. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PROPOSAL] New version numbering scheme
I like the idea. +1 for me. Amy Remy Maucherat wrote: Costin has suggested to me in a private email that the Tomcat project could adopt the Apache 2 numbering scheme (starting with Apache Tomcat 4.1). I think this is a good idea. For the uninitiated, the numbering is: major.minor.build build_stability So for example, the first 4.1.x release would probably be numbered: Apache Tomcat 4.1.0 Alpha ballot [ ] Yes [ ] No /ballot (feel free to provide comments to justify your choice) I vote yes. If the opinion is that this is a good idea, I'll revise the release plan for 4.1 to reflect this change. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: AJP connector silent when RealPlayer is client.
On Wed, Apr 24, 2002 at 11:20:47AM +0200, GOMEZ Henri wrote: After investigation of virtually every other possibility, it seems that mod_jk (AJP 1.3) fails to respond to queries that originate from RealPlayer (v8 and RealOne on win32 tested). The platform is RedHat Linux, running Apache 1.3 with mod_jk to Tomcat 4.0.1 (mod_jk from 4.0.3). Any other request to Apache from any other client works perfectly. When RealPlayer requests a URL in a directory handled by AJP, it accepts the connection and the request, but returns no data and holds the connection open. Could you try with a more recent release of TC 4.0 (4.0.3 for example) What happen if you replace TC 4.0.1 with a TC 3.3.1 (for test purposes :) It works correctly with 4.0.3. Sorry to trouble you. We're using JBoss with the 4.0.1 bundle. Scott msg25759/pgp0.pgp Description: PGP signature
RE: [PROPOSAL] New version numbering scheme
On Wed, 24 Apr 2002, Ignacio J. Ortega wrote: De: Remy Maucherat [mailto:[EMAIL PROTECTED]] Enviado el: miércoles 24 de abril de 2002 23:41 Which will be the rules to advance the build numbers? Probably every time the release manager feels the code is stable and better than the previous build. I'm +1 on the proposal, with the mention that the 'label' should be attached _after_ one week or so - i.e. after the milestone is tested. Each milestone should work and pass some basic tests. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] Release Plan for Apache Tomcat 4.1
+0 Saludos , Ignacio J. Ortega -Mensaje original- De: Remy Maucherat [mailto:[EMAIL PROTECTED]] Enviado el: miércoles 24 de abril de 2002 17:44 Para: [EMAIL PROTECTED] Asunto: [VOTE] Release Plan for Apache Tomcat 4.1 I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PROPOSAL] New version numbering scheme
On Wed, 24 Apr 2002, Ignacio J. Ortega wrote: De: Remy Maucherat [mailto:[EMAIL PROTECTED]] Enviado el: miércoles 24 de abril de 2002 23:41 Which will be the rules to advance the build numbers? Probably every time the release manager feels the code is stable and better than the previous build. I'm +1 on the proposal, with the mention that the 'label' should be attached _after_ one week or so - i.e. after the milestone is tested. Each milestone should work and pass some basic tests. +1. Very good policy IMO, as it avoids the need for the release manager to try to estimate the stability of the milestone. If accepted, I'll document the new policy in the release plan. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[JK2] Some questions
Hola, isapi_redirector2.dll has started to load and log this night :) and is giving me a beautiful NPE when trying the ajp13 connector from tc33, it's suppoused to work, ? i have some caveats about the way the default logger logs by default ;), the code is trying printf to stderr, what can i do? into IIS there is no stderr to log to by default, i'll need to readd the register keys for default logger file and log level :(, It seems to me rather messy because i will need to override and/or ignore those properties setted in the wk2.p file, to, at least, be consistent and to have only one place to configure log.. ANother Caveat is the serverRoot property, there is no serverRoot available here in CrapLand ;), i've mimic the serverRoot with a registry value, but it seems to me that the default config values should be more agnostic.. Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PROPOSAL] New version numbering scheme
On Wed, 24 Apr 2002, Remy Maucherat wrote: Date: Wed, 24 Apr 2002 14:59:45 -0700 From: Remy Maucherat [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: Re: [PROPOSAL] New version numbering scheme Which will be the rules to advance the build numbers? The method in httpd land seems to be once every 1-2 weeks, as long as there are significant changes. Sometimes, one major change (minor security fix or higher priority fix) is enough to cause a build number advance. Remy is too modest to point out that he's used this approach on the Slide project as well (http://jakarta.apache.org/slide and it seems to work quite nicely. +1 Remy Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/server/isapi jk_isapi_plugin.c jk_iis.h
nacho 02/04/24 16:00:14 Modified:jk/native2/server/isapi jk_isapi_plugin.c jk_iis.h Log: * Reading the config file * Removed some debug code * Load and does some logging :) XXX: trying ajp13 worker issues a NPE, needs absolute paths for be able to log. Revision ChangesPath 1.8 +14 -23 jakarta-tomcat-connectors/jk/native2/server/isapi/jk_isapi_plugin.c Index: jk_isapi_plugin.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/server/isapi/jk_isapi_plugin.c,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- jk_isapi_plugin.c 20 Apr 2002 03:06:18 - 1.7 +++ jk_isapi_plugin.c 24 Apr 2002 23:00:14 - 1.8 @@ -60,7 +60,7 @@ * Author: Gal Shachor [EMAIL PROTECTED] * * Author: Larry Isaacs [EMAIL PROTECTED] * * Author: Ignacio J. Ortega [EMAIL PROTECTED] * - * Version: $Revision: 1.7 $ * + * Version: $Revision: 1.8 $ * ***/ // This define is needed to include wincrypt,h, needed to get client certificates @@ -105,7 +105,6 @@ static char worker_file[MAX_PATH * 2]; static char server_root[MAX_PATH * 2]; -FILE *fLog; #define URI_SELECT_OPT_PARSED 0 @@ -117,9 +116,9 @@ static int init_jk(char *serverName); -static int initialize_extension(void); +static int initialize_extension(); -static int read_registry_init_data(void); +static int read_registry_init_data(); static int get_registry_config_parameter(HKEY hkey, const char *tag, @@ -172,11 +171,9 @@ strcpy(pVer-lpszFilterDesc, VERSION_STRING); if (!is_inited) { -fprintf(fLog,GetFilterVersion::!is_inited\n); return initialize_extension(); } -fprintf(fLog,GetFilterVersion::Return TRUE\n); return TRUE; } @@ -412,7 +409,6 @@ if (!is_inited) { return initialize_extension(); } - return TRUE; } @@ -523,9 +519,6 @@ char dir[_MAX_DIR]; char fname[_MAX_FNAME]; char file_name[_MAX_PATH]; - -fLog=fopen(c:\\isapi.log,a); -fprintf(fLog,DllMain::ulReason=%d\n,ulReason); switch (ulReason) { case DLL_PROCESS_DETACH: @@ -544,8 +537,6 @@ } else { fReturn = JK_FALSE; } -fprintf(fLog,DllMain::fReturn=%d\n,fReturn); -fclose(fLog); return fReturn; } @@ -553,8 +544,10 @@ { int rc = JK_FALSE; -jk_env_t *env=jk2_create_config(); - +jk_env_t *env=jk2_create_config(); + +rc=workerEnv-config-setPropertyString( env, workerEnv-config, config.file, worker_file ); + /* Logging the initialization type: registry or properties file in virtual dir */ if (using_ini_file) { @@ -571,13 +564,11 @@ return rc; } -static int initialize_extension(void) +static int initialize_extension() { -fprintf(fLog,initialize_extension::is_inited=%d\n,is_inited); if (read_registry_init_data()) { is_inited = JK_TRUE; } -fprintf(fLog,initialize_extension::is_inited=%d\n,is_inited); return is_inited; } @@ -598,7 +589,7 @@ return -1; } -static int read_registry_init_data(void) +static int read_registry_init_data() { char tmpbuf[INTERNET_MAX_URL_LENGTH]; HKEY hkey; @@ -658,7 +649,7 @@ return JK_FALSE; } -if(get_registry_config_parameter(hkey, +if(rc=get_registry_config_parameter(hkey, EXTENSION_URI_TAG, tmpbuf, sizeof(extension_uri))) { @@ -667,7 +658,7 @@ ok = JK_FALSE; } -if(get_registry_config_parameter(hkey, +if(rc=get_registry_config_parameter(hkey, SERVER_ROOT_TAG, tmpbuf, sizeof(server_root))) { @@ -675,7 +666,7 @@ } else { ok = JK_FALSE; } -if(get_registry_config_parameter(hkey, +if(rc=get_registry_config_parameter(hkey, JK_WORKER_FILE_TAG, tmpbuf, sizeof(worker_file))) { @@ -684,7 +675,7 @@ ok = JK_FALSE; } -if(get_registry_config_parameter(hkey, +
cvs commit: jakarta-tomcat-connectors/jk/native2/server/isapi jk_isapi_plugin.c
nacho 02/04/24 16:06:07 Modified:jk/native2/server/isapi jk_isapi_plugin.c Log: Doh, Build then commit ;) Revision ChangesPath 1.9 +9 -9 jakarta-tomcat-connectors/jk/native2/server/isapi/jk_isapi_plugin.c Index: jk_isapi_plugin.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/server/isapi/jk_isapi_plugin.c,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- jk_isapi_plugin.c 24 Apr 2002 23:00:14 - 1.8 +++ jk_isapi_plugin.c 24 Apr 2002 23:06:07 - 1.9 @@ -60,7 +60,7 @@ * Author: Gal Shachor [EMAIL PROTECTED] * * Author: Larry Isaacs [EMAIL PROTECTED] * * Author: Ignacio J. Ortega [EMAIL PROTECTED] * - * Version: $Revision: 1.8 $ * + * Version: $Revision: 1.9 $ * ***/ // This define is needed to include wincrypt,h, needed to get client certificates @@ -116,9 +116,9 @@ static int init_jk(char *serverName); -static int initialize_extension(); +static int initialize_extension(void); -static int read_registry_init_data(); +static int read_registry_init_data(void); static int get_registry_config_parameter(HKEY hkey, const char *tag, @@ -564,7 +564,7 @@ return rc; } -static int initialize_extension() +static int initialize_extension(void) { if (read_registry_init_data()) { is_inited = JK_TRUE; @@ -589,7 +589,7 @@ return -1; } -static int read_registry_init_data() +static int read_registry_init_data(void) { char tmpbuf[INTERNET_MAX_URL_LENGTH]; HKEY hkey; @@ -649,7 +649,7 @@ return JK_FALSE; } -if(rc=get_registry_config_parameter(hkey, +if(get_registry_config_parameter(hkey, EXTENSION_URI_TAG, tmpbuf, sizeof(extension_uri))) { @@ -658,7 +658,7 @@ ok = JK_FALSE; } -if(rc=get_registry_config_parameter(hkey, +if(get_registry_config_parameter(hkey, SERVER_ROOT_TAG, tmpbuf, sizeof(server_root))) { @@ -666,7 +666,7 @@ } else { ok = JK_FALSE; } -if(rc=get_registry_config_parameter(hkey, +if(get_registry_config_parameter(hkey, JK_WORKER_FILE_TAG, tmpbuf, sizeof(worker_file))) { @@ -675,7 +675,7 @@ ok = JK_FALSE; } -if(rc=get_registry_config_parameter(hkey, +if(get_registry_config_parameter(hkey, URI_SELECT_TAG, tmpbuf, sizeof(tmpbuf))) { @@ -776,7 +776,7 @@ jk_uriEnv_t *newUri; jk_bean_t *jkb; jk_env_t *env; - if( workerEnv==NULL ) { +if( workerEnv==NULL ) { env=jk2_create_workerEnv(); } -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [JK2] Some questions
First - Nacho, my next commit ( probably tommorow, after I check everything ) will be large, please commit whatever you have changed and I'll resolve the conflicts. The biggest change is using JK_OK / JK_ERR consistently for return types and using java style rc=function() if( rc != JK_OK ) ... instead of the if( function() ) { } The second change is some cleanup in the dispatch() and jk_handle, so JNI/SHM will use the same mechanism and code. Now answers: isapi_redirector2.dll has started to load and log this night :) and is giving me a beautiful NPE when trying the ajp13 connector from tc33, it's suppoused to work, ? Is it a NPE or a core dump ? I got it working with Apache + 3.3, 4.0, 4.1 ( ajp13-socket, unix, jni ), but I only did basic tests. Send me the trace, I'll take a look. i have some caveats about the way the default logger logs by default ;), the code is trying printf to stderr, what can i do? into IIS there is no stderr to log to by default, 2 choices - either don't do anything until the file is set, or implement a jk_log_windows.c that sends all messages to the windows even log. The second can sit in common/ and be conditionally compiled - in case someone else wants to use it ( for apache or another server ), it's not specific to IIS ( but windows ). ( the log should go to whatever IIS or the server is using normally ) i'll need to readd the register keys for default logger file and log level :(, It seems to me rather messy because i will need to override and/or ignore those properties setted in the wk2.p file, to, at least, be consistent and to have only one place to configure log.. If you need to - then add them. That's not the biggest problem and we can change later. ANother Caveat is the serverRoot property, there is no serverRoot available here in CrapLand ;), i've mimic the serverRoot with a registry value, but it seems to me that the default config values should be more agnostic.. serverRoot is used to locate the conf/ and logs/ and will be used to locate webapps/ ( with Glen's fix ). ( I'm not sure - there are 2 servers - probably we should find a way to keep all logs, confs, files in the same place ). BTW, many thanks - I can't finish this without your help, is much harder than I ever expected. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2 build.xml
nacho 02/04/24 16:11:11 Modified:jk/native2 build.xml Log: * Less libs needed to build mod_jk2 * Changed the name to isapi_redirector2 Revision ChangesPath 1.23 +3 -3 jakarta-tomcat-connectors/jk/native2/build.xml Index: build.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/build.xml,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- build.xml 20 Apr 2002 22:51:10 - 1.22 +++ build.xml 24 Apr 2002 23:11:11 - 1.23 @@ -123,12 +123,12 @@ import fileName=libhttpd.lib if=win32 / import fileName=libapr.lib if=win32 / import fileName=libaprutil.lib if=win32 / - import fileName=wsock32.lib if=win32 / + !-- import fileName=wsock32.lib if=win32 / import fileName=kernel32.lib if=win32 / import fileName=user32.lib if=win32 / import fileName=gdi32.lib if=win32 / import fileName=winspool.lib if=win32 / - import fileName=comdlg32.lib if=win32 / + import fileName=comdlg32.lib if=win32 /-- linkOpt value=/libpath:quot;${build.compiler.base}/libquot; if=win32 / linkOpt value=/libpath:quot;${apr.lib}quot; if=win32 / linkOpt value=/libpath:quot;${apr-util.lib}quot; if=win32 / @@ -334,7 +334,7 @@ target name=iis depends=init if=iis.detect mkdir dir=${build.dir}/isapi / -so sofile=isapi_redirector +so sofile=isapi_redirector2 buildDir=${build.dir}/isapi optimize=${so.optimize} debug=${so.debug} -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/include jk_service.h
nacho 02/04/24 16:12:50 Modified:jk/native2/common jk_uriMap.c jk_logger_file.c jk/native2/server/apache2 jk_service_apache2.c jk/native2/include jk_service.h Log: * Cosmetics * win32 tweaks to build Revision ChangesPath 1.24 +2 -2 jakarta-tomcat-connectors/jk/native2/common/jk_uriMap.c Index: jk_uriMap.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_uriMap.c,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- jk_uriMap.c 12 Apr 2002 23:09:50 - 1.23 +++ jk_uriMap.c 24 Apr 2002 23:12:50 - 1.24 @@ -67,7 +67,7 @@ * servlet container. * * Author: Gal Shachor [EMAIL PROTECTED] - * Version: $Revision: 1.23 $ + * Version: $Revision: 1.24 $ */ #include jk_pool.h @@ -417,7 +417,7 @@ /* This takes care of 'shorter' matches */ if( _this-debug 0 ) env-l-jkLog(env, env-l, JK_LOG_INFO, - uriMap.mapUri() tentative prefix match %s, + uriMap.mapUri() tentative prefix match %s\n, uwr-prefix ); longest_match = uwr-prefix_len; best_match = i; 1.19 +2 -2 jakarta-tomcat-connectors/jk/native2/common/jk_logger_file.c Index: jk_logger_file.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_logger_file.c,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- jk_logger_file.c 12 Apr 2002 21:49:03 - 1.18 +++ jk_logger_file.c 24 Apr 2002 23:12:50 - 1.19 @@ -59,7 +59,7 @@ * Description: Utility functions (mainly configuration) * * Author: Gal Shachor [EMAIL PROTECTED] * * Author: Henri Gomez [EMAIL PROTECTED] * - * Version: $Revision: 1.18 $ * + * Version: $Revision: 1.19 $ * ***/ #include jk_env.h @@ -163,7 +163,7 @@ return JK_FALSE; } _this-jkLog(env, _this,JK_LOG_ERROR, - Initilizing log file %s\n, _this-name ); + Initializing log file %s\n, _this-name ); _this-logger_private = f; if( oldF!=NULL ) { fclose( oldF ); 1.16 +5 -5 jakarta-tomcat-connectors/jk/native2/server/apache2/jk_service_apache2.c Index: jk_service_apache2.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/server/apache2/jk_service_apache2.c,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- jk_service_apache2.c 12 Apr 2002 21:55:05 - 1.15 +++ jk_service_apache2.c 24 Apr 2002 23:12:50 - 1.16 @@ -59,7 +59,7 @@ * Description: Apache 2 plugin for Jakarta/Tomcat * Author: Gal Shachor [EMAIL PROTECTED] * Henri Gomez [EMAIL PROTECTED] - * Version: $Revision: 1.15 $ + * Version: $Revision: 1.16 $ */ #include apu_compat.h @@ -308,7 +308,7 @@ /* Utility functions */ /* = */ -static unsigned jk2_get_content_length(jk_env_t *env, request_rec *r) +static long jk2_get_content_length(jk_env_t *env, request_rec *r) { if(r-clength 0) { return r-clength; @@ -316,7 +316,7 @@ char *lenp = (char *)apr_table_get(r-headers_in, Content-Length); if(lenp) { -int rc = atoi(lenp); +long rc = atol(lenp); if(rc 0) { return rc; } @@ -326,7 +326,7 @@ return 0; } -static int jk2_init_ws_service(jk_env_t *env, jk_ws_service_t *s, +static int JK_METHOD jk2_init_ws_service(jk_env_t *env, jk_ws_service_t *s, jk_worker_t *worker, void *serverObj) { apr_port_t port; @@ -534,7 +534,7 @@ * jk shouldn't do it instead, and the user should get the *
cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java
costin 02/04/24 16:20:38 Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java Log: extra 't' Revision ChangesPath 1.16 +1 -1 jakarta-tomcat-connectors/jk/java/org/apache/jk/server/JkCoyoteHandler.java Index: JkCoyoteHandler.java === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/server/JkCoyoteHandler.java,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- JkCoyoteHandler.java 24 Apr 2002 19:45:09 - 1.15 +++ JkCoyoteHandler.java 24 Apr 2002 23:20:38 - 1.16 @@ -239,7 +239,7 @@ if( actionCode==ActionCode.ACTION_COMMIT ) { org.apache.coyote.Response res=(org.apache.coyote.Response)param; -if( res.isCommited() ) { +if( res.isCommitted() ) { if( log.isInfoEnabled() ) log.info(Response already commited ); } else { -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet JspServlet.java
kinman 02/04/24 16:49:05 Modified:jasper2/src/share/org/apache/jasper/servlet JspServlet.java Log: - Fixed a typo that causes class not to be loaded after compiling the page. Revision ChangesPath 1.5 +1 -1 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServlet.java Index: JspServlet.java === RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServlet.java,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- JspServlet.java 24 Apr 2002 11:58:00 - 1.4 +++ JspServlet.java 24 Apr 2002 23:49:05 - 1.5 @@ -620,7 +620,7 @@ if ((jsw.servletClass == null) || outDated) { try { synchronized (jsw) { - if (jsw.servletClass == null) { + if (jsw.servletClass == null || outDated) { URL [] urls = new URL[1]; File outputDir = new File(normalize(ctxt.getOutputDir())); urls[0] = outputDir.toURL(); -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5585] - Error page not displayed
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5585. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5585 Error page not displayed [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-04-24 23:54 --- Please note that buffer=none is set in the page directive. This has the effect of writing to the reponse buffer directly. By the time the error happen, the reponse has already been committed, hence the error is not displayed. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [JK2] Some questions
First - Nacho, my next commit ( probably tommorow, after I check everything ) will be large, please commit whatever you have changed and I'll resolve the conflicts. Done, go ahead.. Is it a NPE or a core dump ? I got it working with Apache + 3.3, 4.0, 4.1 ( ajp13-socket, unix, jni ), but I only did basic tests. Send me the trace, I'll take a look. jk_uriMap.c/411, it seems the worker is null, it gives a NPE when trying to log the worker name found to service the uri. i have some caveats about the way the default logger logs by default ;), 2 choices - either don't do anything until the file is set, or This way I've lost all the logs at the jk start, prior to read the wk2.p file, it's hard to debug a config failure this way.. implement a jk_log_windows.c that sends all messages to the windows even log. I'll try this weekend, not very difficult, i'm starting to understand the undergoings of jk2, and is nice, verbose but nice.. ;) i'll need to readd the register keys for default logger file and log level :(, It seems to me rather messy because i will need to override and/or ignore those properties setted in the wk2.p file, to, at least, be consistent and to have only one place to configure log.. If you need to - then add them. That's not the biggest problem and we can change later. Well, i would like to reduce the registry settings needed at a minimun, registry settings are little evil to me, tomcat-user is plenty of problems related to config settings, at least until these nice installers came into play, I much prefer text configs.. value, but it seems to me that the default config values should be more agnostic.. serverRoot is used to locate the conf/ and logs/ and will be used to locate webapps/ ( with Glen's fix ). ( I'm not sure - there are 2 servers - probably we should find a way to keep all logs, confs, files in the same place ). This can work for apache, win32 or *x but for IIS it's really hard, i much prefer to keep all this things near tomcat, not near the System32 directory :), anyway having a totally agnostic way, given the OOP over C style jk2 has, this could be done by making a specialized config ( inheriting from the actual one ) for every server? this specialized config would make the need asumptions for the server using jk2? Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5666] - Implicit object _value on jsp pages
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5666. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5666 Implicit object _value on jsp pages [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-04-25 00:01 --- This is a FIXED for jasper2 and WONTFIX for jasper, because it is really harmless and jasper is eventually going to be replaced by jasper. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
On Thu, 2002-04-25 at 01:44, Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [X] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Why is JDK needed to install Apache Tomcat 4.0 on WinNT?
On Thu, 2002-04-25 at 02:37, Duncan McLean wrote: * Beginning October 17, 2001, it is permissable to redistribute * * the javac compiler with the Java 2 Runtime Environment (JRE).* Which gives permission to JRE packagers like IBM to include javac in the JRE. Most JRE's still don't have it included, so I'm guessing Tomcat is playing it safe here. Does that answer your question or did I misread something? Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PROPOSAL] New version numbering scheme
On Thu, 2002-04-25 at 07:41, Remy Maucherat wrote: ballot [X] Yes [ ] No /ballot I actually like the Linux style, with odd minor numbers for unstable releases and even for stable ones, but this is not bad too. Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5903] - version attribute in jsp:root
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5903. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5903 version attribute in jsp:root [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-04-25 00:37 --- Fixed in jasper2. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [JK2] Some questions
On Thu, 25 Apr 2002, Ignacio J. Ortega wrote: keep all logs, confs, files in the same place ). This can work for apache, win32 or *x but for IIS it's really hard, i much prefer to keep all this things near tomcat, not near the System32 directory :), anyway having a totally agnostic way, given the OOP over C style jk2 has, this could be done by making a specialized config ( inheriting from the actual one ) for every server? this specialized config would make the need asumptions for the server using jk2? The set serverRoot to tomcat.home/catalina.base. We need a base directory for all locations. That should be the only setting you need in the registry - the top level dir where we can start seeing conf/, logs/, etc. That's very confusing for apache - we have apache/conf and tomcat/conf, but for IIS it should be easier - you have only one dir :-) Advanced configuration is possible - but we should start with workers2.properties then do 'auto-guessing' ( Glen ) and special settings on the various components. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Replacing WebappClassLoader
hung [EMAIL PROTECTED] writes: Dear Tomcat Dev, Is there a website that have the instruction on how to connection Tomcat 4 with Apache 2? Please help. Made me running tomcat as module of apache. This sort of question is most appropriate on the Tomcat User list. The documentation for what you're asking about is located under the Connectors section of the left nav in the following links: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/index.html http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/index.html -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JSP no reload
Hi All, Is there is a setting in Jasper to disable Tomcat from checking the timestamp on the page everytime there is a request? It seems important as the more include files are there in the JSP page the more checking that could happen, additionaly due to the nature of Java creating a File object and check the file system each time could be an expensive process. Regards Sam