DO NOT REPLY [Bug 23471] New: - No Java compiler was found to compile the generated source for the JSP
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=23471. 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=23471 No Java compiler was found to compile the generated source for the JSP Summary: No Java compiler was found to compile the generated source for the JSP Product: Tomcat 5 Version: 5.0.12 Platform: All OS/Version: Other Status: NEW Severity: Critical Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] when java syntax error exists in %! %, it generate java source correct but report no compiler found and suggest as follow: org.apache.jasper.JasperException: Unable to compile class for JSP No Java compiler was found to compile the generated source for the JSP. This can usually be solved by copying manually $JAVA_HOME/lib/tools.jar from the JDK to the common/lib directory of the Tomcat server, followed by a Tomcat restart. If using an alternate Java compiler, please check its installation and access path. at org.apache.jasper.compiler.DefaultErrorHandler.javacError (DefaultErrorHandler.java:128) at org.apache.jasper.compiler.ErrorDispatcher.javacError (ErrorDispatcher.java:351) at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:413) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:453) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:437) at org.apache.jasper.JspCompilationContext.compile (JspCompilationContext.java:555) at org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:291) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:301) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat/proposals/JmxSupport/WEB-INF/classes/org/apache/tomcat/modules/config MxInterceptor.java DynamicMBeanProxy.java
hgomez 2003/09/29 00:38:10
Modified:proposals/JmxSupport/WEB-INF/classes/org/apache/tomcat/modules/config
MxInterceptor.java DynamicMBeanProxy.java
Log:
Add JRMP support if we ever use this Interceptor
Revision ChangesPath
1.2 +127 -53
jakarta-tomcat/proposals/JmxSupport/WEB-INF/classes/org/apache/tomcat/modules/config/MxInterceptor.java
Index: MxInterceptor.java
===
RCS file:
/home/cvs/jakarta-tomcat/proposals/JmxSupport/WEB-INF/classes/org/apache/tomcat/modules/config/MxInterceptor.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- MxInterceptor.java30 Sep 2002 02:17:43 - 1.1
+++ MxInterceptor.java29 Sep 2003 07:38:10 - 1.2
@@ -58,12 +58,24 @@
*/
package org.apache.tomcat.modules.config;
-import org.apache.tomcat.core.*;
-import org.apache.tomcat.util.io.FileUtil;
-import java.io.*;
-import java.util.*;
+import java.io.IOException;
+import java.net.InetAddress;
-import javax.management.*;
+import javax.management.Attribute;
+import javax.management.MBeanServer;
+import javax.management.ObjectName;
+
+import mx4j.adaptor.rmi.jrmp.JRMPAdaptorMBean;
+import mx4j.tools.naming.NamingServiceMBean;
+import mx4j.util.StandardMBeanProxy;
+
+import org.apache.tomcat.core.BaseInterceptor;
+import org.apache.tomcat.core.Context;
+import org.apache.tomcat.core.ContextManager;
+import org.apache.tomcat.core.Request;
+import org.apache.tomcat.core.Response;
+import org.apache.tomcat.core.TomcatException;
+import org.apache.tomcat.modules.config.DynamicMBeanProxy;
/**
*
@@ -72,11 +84,12 @@
public class MxInterceptor extends BaseInterceptor {
MBeanServer mserver;
-private int port=-1;
+private intport=-1;
private String host;
-private String auth;
+private String auth;
private String user;
private String password;
+private String type = http;
// Tomcat callbacks
@@ -101,7 +114,7 @@
/* Public methods */
-/** Enable the MX4J internal adapter
+/** Enable the MX4J internal adaptor
*/
public void setPort( int i ) {
port=i;
@@ -140,58 +153,119 @@
return password != null password.length() 0;
}
+ public void setType(String type) {
+ this.type = type;
+ }
+
+ public String getType() {
+ return type;
+ }
+
/* Start/stop */
ObjectName serverName=null;
-/** Initialize the worker. After this call the worker will be
- * ready to accept new requests.
- */
-public void loadAdapter() throws IOException {
-try {
-serverName = new ObjectName(Http:name=HttpAdaptor);
-mserver.createMBean(mx4j.adaptor.http.HttpAdaptor, serverName, null);
+ /** Initialize the JRMP Adaptor for JMX.
+ */
+ private void loadJRMPAdaptor()
+ {
+ try
+ {
+ // Create the RMI Naming registry
+ ObjectName naming = new ObjectName(Naming:type=registry);
+ mserver.createMBean(mx4j.tools.naming.NamingService, naming,
null, new Object[] {new Integer(port)}, new String[] {int});
+ NamingServiceMBean nsmbean =
(NamingServiceMBean)StandardMBeanProxy.create(NamingServiceMBean.class, mserver,
naming);
+ nsmbean.start();
+
+ // Create the JRMP adaptor
+ ObjectName adaptor = new ObjectName(Adaptor:protocol=JRMP);
+ mserver.createMBean(mx4j.adaptor.rmi.jrmp.JRMPAdaptor,
adaptor, null);
+ JRMPAdaptorMBean jrmpmbean =
(JRMPAdaptorMBean)StandardMBeanProxy.create(JRMPAdaptorMBean.class, mserver, adaptor);
+
+ // Set the JNDI name with which will be registered
+ String jndiName = jrmp;
+ jrmpmbean.setJNDIName(jndiName);
+
+ String lHost = host;
+
+ if (lHost == null)
+ lHost = localhost;
+ else if (lHost.length() == 0)
+ lHost =
InetAddress.getLocalHost().getHostName();
+
+ log( Started mx4j jrmp adaptor + ((host != null) ? for
host + host : ) + at port + port);
+
+
jrmpmbean.putJNDIProperty(javax.naming.Context.INITIAL_CONTEXT_FACTORY,
com.sun.jndi.rmi.registry.RegistryContextFactory);
+
cvs commit: jakarta-tomcat/src/examples/WEB-INF/classes/sessions DummyCart.java
hgomez 2003/09/29 00:39:50 Modified: proposals/Log4jHelper/WEB-INF/classes/org/apache/tomcat/modules/loggers/log4j Log4jHelper.java CRS.java src/examples/WEB-INF/classes/examples FooTagExtraInfo.java LogTag.java ExampleTagBase.java ShowSource.java FooTag.java src/examples/WEB-INF/classes/dates JspCalendar.java src/examples/WEB-INF/classes HelloW.java SnoopServlet.java servletToJsp.java Hello.java SessionExample.java LocalStrings_fr.properties HelloWorldExample.java RequestHeaderExample.java CookieExample.java CookieExample1.java RequestParamExample.java RequestInfoExample.java proposals/PasswordPrompter/WEB-INF/classes/org/apache/tomcat/modules/config PasswordPrompter.java src/admin/WEB-INF/classes/tadm AntTEI.java ModuleAdmin.java GTestTag.java ThreadAdmin.java TomcatIterateTEI.java AntServletLogger.java TomcatAdmin.java TomcatIterate.java ContextAdmin.java GTestTEI.java AntTarget.java AntProperty.java AntTag.java ModuleAdminTEI.java TomcatAdminTEI.java src/examples/WEB-INF/classes/error Smart.java proposals/StreamHandler/WEB-INF/classes/org/apache/tomcat/modules/config StreamHandler.java proposals/StreamHandler/WEB-INF/classes/org/apache/tomcat/util/net StreamHandlerFactory.java src/examples/WEB-INF/classes/num NumberGuessBean.java proposals/PasswordPrompter/WEB-INF/classes/org/apache/tomcat/util/io Prompter.java src/examples/WEB-INF/classes/cal TableBean.java JspCalendar.java Entries.java src/examples/WEB-INF/classes/colors ColorGameBean.java src/examples/WEB-INF/classes/sessions DummyCart.java Log: More imports cleaned (the wildcard for example) Revision ChangesPath 1.2 +5 -1 jakarta-tomcat/proposals/Log4jHelper/WEB-INF/classes/org/apache/tomcat/modules/loggers/log4j/Log4jHelper.java Index: Log4jHelper.java === RCS file: /home/cvs/jakarta-tomcat/proposals/Log4jHelper/WEB-INF/classes/org/apache/tomcat/modules/loggers/log4j/Log4jHelper.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Log4jHelper.java 7 Apr 2003 00:29:22 - 1.1 +++ Log4jHelper.java 29 Sep 2003 07:39:48 - 1.2 @@ -58,9 +58,13 @@ */ package org.apache.tomcat.modules.loggers.log4j; -import org.apache.tomcat.core.*; import org.apache.log4j.Level; import org.apache.log4j.LogManager; +import org.apache.tomcat.core.BaseInterceptor; +import org.apache.tomcat.core.Context; +import org.apache.tomcat.core.ContextManager; +import org.apache.tomcat.core.Request; +import org.apache.tomcat.core.TomcatException; /** * Interceptor to add context-seperation support for log4j logging. 1.2 +7 -4 jakarta-tomcat/proposals/Log4jHelper/WEB-INF/classes/org/apache/tomcat/modules/loggers/log4j/CRS.java Index: CRS.java === RCS file: /home/cvs/jakarta-tomcat/proposals/Log4jHelper/WEB-INF/classes/org/apache/tomcat/modules/loggers/log4j/CRS.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- CRS.java 7 Apr 2003 00:29:22 - 1.1 +++ CRS.java 29 Sep 2003 07:39:48 - 1.2 @@ -58,10 +58,13 @@ */ package org.apache.tomcat.modules.loggers.log4j; -import java.util.*; -import org.apache.tomcat.core.*; -import org.apache.log4j.*; -import org.apache.log4j.spi.*; +import java.util.Hashtable; + +import org.apache.log4j.Hierarchy; +import org.apache.log4j.Level; +import org.apache.log4j.spi.LoggerRepository; +import org.apache.log4j.spi.RepositorySelector; +import org.apache.log4j.spi.RootCategory; /** * Implimentation to add context-seperation support for log4j logging. 1.2 +3 -1 jakarta-tomcat/src/examples/WEB-INF/classes/examples/FooTagExtraInfo.java Index: FooTagExtraInfo.java === RCS file: /home/cvs/jakarta-tomcat/src/examples/WEB-INF/classes/examples/FooTagExtraInfo.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- FooTagExtraInfo.java 20 Nov 1999 06:13:50 - 1.1 +++ FooTagExtraInfo.java 29 Sep 2003 07:39:48 - 1.2 @@ -1,6 +1,8 @@ package examples; -import
cvs commit: jakarta-tomcat/proposals/build2/WEB-INF/src AntTEI.java AntServletLogger.java AntTarget.java AntTag.java AntProperty.java
hgomez 2003/09/29 00:40:14
Modified:proposals/build2/WEB-INF/src AntTEI.java
AntServletLogger.java AntTarget.java AntTag.java
AntProperty.java
Log:
More imports cleaned (the wildcard for example)
Revision ChangesPath
1.2 +0 -9 jakarta-tomcat/proposals/build2/WEB-INF/src/AntTEI.java
Index: AntTEI.java
===
RCS file: /home/cvs/jakarta-tomcat/proposals/build2/WEB-INF/src/AntTEI.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AntTEI.java 28 Apr 2001 19:31:36 - 1.1
+++ AntTEI.java 29 Sep 2003 07:40:14 - 1.2
@@ -1,13 +1,4 @@
package tadm;
-import java.util.Vector;
-import java.util.Enumeration;
-import java.io.File;
-import java.net.URL;
-import javax.servlet.http.*;
-
-import javax.servlet.jsp.*;
-import javax.servlet.jsp.tagext.*;
-
import javax.servlet.jsp.tagext.TagData;
import javax.servlet.jsp.tagext.TagExtraInfo;
import javax.servlet.jsp.tagext.VariableInfo;
1.2 +5 -3
jakarta-tomcat/proposals/build2/WEB-INF/src/AntServletLogger.java
Index: AntServletLogger.java
===
RCS file:
/home/cvs/jakarta-tomcat/proposals/build2/WEB-INF/src/AntServletLogger.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AntServletLogger.java 28 Apr 2001 19:31:36 - 1.1
+++ AntServletLogger.java 29 Sep 2003 07:40:14 - 1.2
@@ -1,8 +1,10 @@
package tadm;
-import org.apache.tools.ant.*;
+import java.io.IOException;
+import java.io.PrintStream;
-import java.io.*;
-import javax.servlet.http.*;
+import org.apache.tools.ant.BuildEvent;
+import org.apache.tools.ant.BuildException;
+import org.apache.tools.ant.BuildLogger;
public class AntServletLogger implements BuildLogger {
protected java.io.Writer out;
1.2 +4 -11 jakarta-tomcat/proposals/build2/WEB-INF/src/AntTarget.java
Index: AntTarget.java
===
RCS file: /home/cvs/jakarta-tomcat/proposals/build2/WEB-INF/src/AntTarget.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AntTarget.java28 Apr 2001 19:31:36 - 1.1
+++ AntTarget.java29 Sep 2003 07:40:14 - 1.2
@@ -1,16 +1,9 @@
package tadm;
-import java.util.Vector;
-import java.util.Enumeration;
-import java.io.*;
-import java.net.URL;
-import javax.servlet.http.*;
-import javax.servlet.*;
+import javax.servlet.jsp.JspException;
+import javax.servlet.jsp.tagext.Tag;
+import javax.servlet.jsp.tagext.TagSupport;
-import javax.servlet.jsp.*;
-import javax.servlet.jsp.tagext.*;
-
-import org.apache.tools.ant.*;
-import org.apache.tomcat.util.test.*;
+import tadm.AntTag;
/**
* Child tag to add ant targets to Ant taglib.
1.2 +14 -8 jakarta-tomcat/proposals/build2/WEB-INF/src/AntTag.java
Index: AntTag.java
===
RCS file: /home/cvs/jakarta-tomcat/proposals/build2/WEB-INF/src/AntTag.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AntTag.java 28 Apr 2001 19:31:36 - 1.1
+++ AntTag.java 29 Sep 2003 07:40:14 - 1.2
@@ -1,14 +1,20 @@
package tadm;
-import java.util.*;
-import java.io.*;
-import java.net.URL;
-import javax.servlet.http.*;
-import javax.servlet.*;
+import java.io.File;
+import java.io.IOException;
+import java.io.PrintWriter;
+import java.util.Enumeration;
+import java.util.Hashtable;
+import java.util.Properties;
+import java.util.Vector;
-import javax.servlet.jsp.*;
-import javax.servlet.jsp.tagext.*;
+import javax.servlet.jsp.JspException;
+import javax.servlet.jsp.tagext.TagSupport;
-import org.apache.tools.ant.*;
+import org.apache.tools.ant.BuildException;
+import org.apache.tools.ant.Project;
+import org.apache.tools.ant.ProjectHelper;
+
+import tadm.AntServletLogger;
/**
* This tag will run ant tasks
1.2 +6 -12 jakarta-tomcat/proposals/build2/WEB-INF/src/AntProperty.java
Index: AntProperty.java
===
RCS file: /home/cvs/jakarta-tomcat/proposals/build2/WEB-INF/src/AntProperty.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AntProperty.java 28 Apr 2001 19:31:36 - 1.1
+++ AntProperty.java 29 Sep 2003 07:40:14 - 1.2
@@ -1,17 +1,11 @@
package tadm;
-import java.util.Vector;
-import java.util.Enumeration;
-import java.io.*;
-import java.net.URL;
-import javax.servlet.http.*;
-import
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/resources LocalStrings_fr.properties
hgomez 2003/09/29 00:41:11 Modified:src/share/org/apache/tomcat/resources LocalStrings_fr.properties Log: Fix translation Revision ChangesPath 1.7 +2 -2 jakarta-tomcat/src/share/org/apache/tomcat/resources/LocalStrings_fr.properties Index: LocalStrings_fr.properties === RCS file: /home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/resources/LocalStrings_fr.properties,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- LocalStrings_fr.properties31 Oct 2002 09:26:42 - 1.6 +++ LocalStrings_fr.properties29 Sep 2003 07:41:10 - 1.7 @@ -5,7 +5,7 @@ # This is the French locale and is fr_FR # StaticInterceptor -defaultservlet.directorylistingfor=Directory Listing for: +defaultservlet.directorylistingfor=Liste du répertoire pour: defaultservlet.upto=Jusqu''à: defaultservlet.subdirectories=Sous-Dossiers: defaultservlet.files=Fichiers: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/doc AJPv13.html serverxml.html
hgomez 2003/09/29 00:42:59 Modified:src/doc AJPv13.html serverxml.html Log: Update ajp13 doc (ping/pong added), and also MxInterceptor (added jrmp) Revision ChangesPath 1.7 +11 -0 jakarta-tomcat/src/doc/AJPv13.html Index: AJPv13.html === RCS file: /home/cvs/jakarta-tomcat/src/doc/AJPv13.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- AJPv13.html 9 Oct 2001 17:59:58 - 1.6 +++ AJPv13.html 29 Sep 2003 07:42:59 - 1.7 @@ -235,6 +235,11 @@ TDShutdown/TD TDThe web server asks the container to shut itself down. /TR + TR +TD ALIGN=CENTER8/TD +TDPing/TD +TDThe web server asks the container to quickly respond with a Pong. + /TR /TABLE PThe servlet container can send the following types of messages to the web @@ -271,6 +276,12 @@ TDGet Body Chunk/TD TDGet further data from the request if it hasn't all been transferred yet./TD + /TR + /TR +TR +TD ALIGN=CENTER9/TD +TDPong/TD +TDReply to a Ping request./TD /TR /TABLE 1.32 +12 -8 jakarta-tomcat/src/doc/serverxml.html Index: serverxml.html === RCS file: /home/cvs/jakarta-tomcat/src/doc/serverxml.html,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- serverxml.html7 Nov 2002 13:23:32 - 1.31 +++ serverxml.html29 Sep 2003 07:42:59 - 1.32 @@ -2160,9 +2160,9 @@ h4Description/h4 pJMX MBeans support has been added to Tomcat 3.3.2, which allow you to manage -Tomcat from any JMX console or via a simple browser by the build in HTTP Adaptor/p +Tomcat from any JMX console (JRMP) or via a simple browser by the build in HTTP Adaptor/p pTo enable JMX, you should add the lt;MxInterceptor /gt; in server.xml/p -pTo also activate the HTTP Adaptor you should at least define the listen port/p +pTo also activate the HTTP/JRMP Adaptor you should at least define the port/p h4Attributes/h4 @@ -2173,13 +2173,18 @@ thDefault/th /tr tr valign=top +tdtype/td +tdindicate what kind of adapter you want to use, HTTP or JRMP./td +tdHTTP/td + /tr + tr valign=top tdport/td -tdport where the JMX HTTP Adaptor will listen to, HTTP Adaptor will only be loaded if the port is set/td -td-1, no http adaptor loaded/td +tdport where the JMX HTTP/JRMP adaptor will listen to, no adaptor will be loaded if not set/td +tdno adaptor/td /tr tr valign=top tdhost/td -tdhost/ip where the JMX HTTP Adaptor will listen to, only available when using codeMX4J/code HTTP Adaptor/td +tdhost/ip where the JMX HTTP/JRMP Adaptor will listen to, only available when using codeMX4J/code implementation/td tdnull/td /tr tr valign=top @@ -2205,8 +2210,7 @@ h4Example(s)/h4 pre -lt;MxInterceptor port=quot;8999quot; host=quot;mysystemquot; authentication=quot;basicquot; user=quot;adminquot; password=quot;changeillicoquot;/gt; -lt;erceptor /gt; +lt;MxInterceptor type=quot;HTTPquot; port=quot;8999quot; host=quot;mysystemquot; authentication=quot;basicquot; user=quot;adminquot; password=quot;changeillicoquot; /gt; /pre hr size=5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/native/mod_jk OBSOLETE.txt
hgomez 2003/09/29 00:43:33 Added: src/native/mod_jk OBSOLETE.txt Log: A note to warn users that this version of mod_jk is obsolete Revision ChangesPath 1.1 jakarta-tomcat/src/native/mod_jk/OBSOLETE.txt Index: OBSOLETE.txt === $Id: OBSOLETE.txt,v 1.1 2003/09/29 07:43:33 hgomez Exp $ The mod_jk in this directory is obsolete and you should instead use the one present in jakarta-tomcat-connectors project. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/tests/share/gtest GTest.java
hgomez 2003/09/29 00:43:40 Modified:src/tests/share/gtest GTest.java Log: More imports cleaned (the wildcard for example) Revision ChangesPath 1.4 +11 -4 jakarta-tomcat/src/tests/share/gtest/GTest.java Index: GTest.java === RCS file: /home/cvs/jakarta-tomcat/src/tests/share/gtest/GTest.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- GTest.java20 Jan 2001 21:50:24 - 1.3 +++ GTest.java29 Sep 2003 07:43:40 - 1.4 @@ -58,10 +58,17 @@ */ package org.apache.tomcat.task; -import java.net.*; -import java.io.*; -import java.util.*; -import java.net.*; +import java.io.FileInputStream; +import java.io.IOException; +import java.io.InputStream; +import java.io.OutputStream; +import java.io.OutputStreamWriter; +import java.io.PrintWriter; +import java.net.Socket; +import java.net.SocketException; +import java.util.Enumeration; +import java.util.Hashtable; +import java.util.StringTokenizer; /** Test a web application. Will send a http request and - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 12428] - request.getUserPrincipal(): Misinterpretation of specification?
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=12428. 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=12428 request.getUserPrincipal(): Misinterpretation of specification? --- Additional Comments From [EMAIL PROTECTED] 2003-09-29 08:20 --- Created an attachment (id=8384) Filter attempting to store principal in the session - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/procrun - New directory
mturk 2003/09/29 01:59:43 jakarta-tomcat-connectors/procrun - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/procrun extend.h icoi.ico icos.ico icow.ico splash.bmp tomcat.c tomcat.dsp tomcat.dsw tomcat.rc tomcatp.ico tomcatr.ico tomcats.ico
mturk 2003/09/29 02:01:40 Added: procrun extend.h icoi.ico icos.ico icow.ico splash.bmp tomcat.c tomcat.dsp tomcat.dsw tomcat.rc tomcatp.ico tomcatr.ico tomcats.ico Log: Add the procrun tomcat extension to the j-t-c. Revision ChangesPath 1.1 jakarta-tomcat-connectors/procrun/extend.h Index: extend.h === /* * The Apache Software License, Version 1.1 * * Copyright (c) 2000-2003 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright *notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright *notice, this list of conditions and the following disclaimer in *the documentation and/or other materials provided with the *distribution. * * 3. The end-user documentation included with the redistribution, *if any, must include the following acknowledgment: * This product includes software developed by the *Apache Software Foundation (http://www.apache.org/). *Alternately, this acknowledgment may appear in the software itself, *if and wherever such third-party acknowledgments normally appear. * * 4. The names Apache and Apache Software Foundation must *not be used to endorse or promote products derived from this *software without prior written permission. For written *permission, please contact [EMAIL PROTECTED] * * 5. Products derived from this software may not be called Apache, *nor may Apache appear in their name, without prior written *permission of the Apache Software Foundation. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation. For more * information on the Apache Software Foundation, please see * http://www.apache.org/. * * Portions of this software are based upon public domain software * originally written at the National Center for Supercomputing Applications, * University of Illinois, Urbana-Champaign. */ /* * procrun * * Contributed by Mladen Turk [EMAIL PROTECTED] * * 05 Aug 2002 * */ #define IDB_BMPSPLASH 201 #define IDI_ICOI 202 #define IDI_ICOS 203 #define IDI_ICOW 204 #define IDD_DLGSPLASH 205 #define IDL_INFO 206 #define PROCRUN_REGKEY_ROOT SOFTWARE\\Apache Software Foundation\\Tomcat Service Manager #define PROCRUN_GUI_DISPLAY Tomcat Service Manager 1.1 jakarta-tomcat-connectors/procrun/icoi.ico Binary file 1.1 jakarta-tomcat-connectors/procrun/icos.ico Binary file 1.1 jakarta-tomcat-connectors/procrun/icow.ico Binary file 1.1 jakarta-tomcat-connectors/procrun/splash.bmp Binary file 1.1 jakarta-tomcat-connectors/procrun/tomcat.c Index: tomcat.c === /* * The Apache Software License, Version 1.1 * * Copyright (c) 2000-2003 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of
cvs commit: jakarta-tomcat-connectors/procrun/bin - New directory
mturk 2003/09/29 02:03:22 jakarta-tomcat-connectors/procrun/bin - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe
mturk 2003/09/29 02:04:33 Added: procrun/bin tomcat.exe tomcatw.exe Log: Add the tomcat and tomcatw binaries. Revision ChangesPath 1.1 jakarta-tomcat-connectors/procrun/bin/tomcat.exe Binary file 1.1 jakarta-tomcat-connectors/procrun/bin/tomcatw.exe Binary file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/procrun README.txt
mturk 2003/09/29 02:06:33 Added: procrun README.txt Log: Simple readme for build instructions. Revision ChangesPath 1.1 jakarta-tomcat-connectors/procrun/README.txt Index: README.txt === Copy all files except extend.h from procrun. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15735] - Misspelling in french
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=15735. 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=15735 Misspelling in french [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18939] - Adding a New Mobile Device
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=18939. 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=18939 Adding a New Mobile Device [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID Summary|Adding a New Mobile Device |Adding a New Mobile Device --- Additional Comments From [EMAIL PROTECTED] 2003-09-29 09:30 --- The bug report seems invalid, thanks to clarify and reopen if necessary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8155] - Tomcat from RPM doesn't do logrotate
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=8155. 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=8155 Tomcat from RPM doesn't do logrotate --- Additional Comments From [EMAIL PROTECTED] 2003-09-29 09:31 --- You should consider using the RPM provided by JPackage projet (www.jpackage.org). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8155] - Tomcat from RPM doesn't do logrotate
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=8155. 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=8155 Tomcat from RPM doesn't do logrotate [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4893] - Tomcat dies with following error..
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=4893. 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=4893 Tomcat dies with following error.. [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23477] New: - the admin and manager webapps is not available when host appbase is out of catalina home.
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=23477. 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=23477 the admin and manager webapps is not available when host appbase is out of catalina home. Summary: the admin and manager webapps is not available when host appbase is out of catalina home. Product: Tomcat 5 Version: 5.0.12 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] According the log, when start depoy context, it still try find them from host_appbase's parent directory. (Forgive me for my bad English, God bless someone could understand it!) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23478] New: - StringIndexOutOfBoundsException with an empty jsp file name
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=23478. 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=23478 StringIndexOutOfBoundsException with an empty jsp file name Summary: StringIndexOutOfBoundsException with an empty jsp file name Product: Tomcat 3 Version: 3.3.1 Final Platform: All URL: http://mypc/.jsp OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If there is no file name in the URL, like in http://mypc/.jsp, I get the following exception: java.lang.StringIndexOutOfBoundsException: String index out of range: 0 at java.lang.String.charAt(Compiled Code) at org.apache.jasper.compiler.JasperMangler.fixInvalidChars(Compiled Code) at org.apache.jasper.compiler.JasperMangler.init(JasperMangler.java:258) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23477] - the admin and manager webapps is not available when host appbase is out of catalina home.
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=23477. 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=23477 the admin and manager webapps is not available when host appbase is out of catalina home. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-09-29 09:56 --- Their docBase is relative to the host appBase, so this is normal (we obviously cannot hardcode an absolute path). You have to modify the context files to specify something abslute (or move admin and manager elsewhere). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
TC 3.3.2
Hi to all, I commited the last part of clean imports and started to take a look at bugzilla where many reports seems still open. What's the strategy now ? Should we close those which seems invalid ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/bin catalina.bat catalina.xml
remm2003/09/29 03:27:20
Modified:catalina/src/bin catalina.bat catalina.xml
Log:
- Set -Dsun.io.useCanonCaches=false for Windows. This decreases
startup performance significantly, but is needed for now (since Sun doesn't
seem to be willing to fix the bug in a timely fashion).
Revision ChangesPath
1.4 +3 -1 jakarta-tomcat-catalina/catalina/src/bin/catalina.bat
Index: catalina.bat
===
RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/bin/catalina.bat,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- catalina.bat 4 Aug 2002 18:19:43 - 1.3
+++ catalina.bat 29 Sep 2003 10:27:20 - 1.4
@@ -36,6 +36,8 @@
rem $Id$
rem ---
+set CATALINA_OPTS=%CATALINA_OPTS% -Dsun.io.useCanonCaches=false
+
rem Guess CATALINA_HOME if not defined
if not %CATALINA_HOME% == goto gotHome
set CATALINA_HOME=.
1.9 +1 -1 jakarta-tomcat-catalina/catalina/src/bin/catalina.xml
Index: catalina.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/bin/catalina.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- catalina.xml 17 Jan 2003 10:17:29 - 1.8
+++ catalina.xml 29 Sep 2003 10:27:20 - 1.9
@@ -20,7 +20,7 @@
property name=catalina.tmpdir location=${catalina.base}/temp/
property name=catalina.out location=${catalina.base}/logs/catalina.out/
property name=catalina.policy
location=${catalina.base}/conf/catalina.policy/
- property name=catalina.jvm.args value=/
+ property name=catalina.jvm.args value=-Dsun.io.useCanonCaches=false/
property name=catalina.source.path
value=${catalina.home}/../../jakarta-servletapi-5/src/share:${catalina.home}/../../jakarta-tomcat-jasper/jasper2/src/share:${catalina.home}/../../jakarta-tomcat-connectors/coyote/src/java:${catalina.home}/../../jakarta-tomcat-catalina/catalina/src/share/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 build.properties.default build.xml tomcat.nsi
remm2003/09/29 03:27:40
Modified:.build.properties.default build.xml tomcat.nsi
Log:
- Set -Dsun.io.useCanonCaches=false for Windows. This decreases
startup performance significantly, but is needed for now (since Sun doesn't
seem to be willing to fix the bug in a timely fashion).
- Update after procrun move.
Revision ChangesPath
1.109 +1 -4 jakarta-tomcat-5/build.properties.default
Index: build.properties.default
===
RCS file: /home/cvs/jakarta-tomcat-5/build.properties.default,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -r1.108 -r1.109
--- build.properties.default 23 Sep 2003 18:41:11 - 1.108
+++ build.properties.default 29 Sep 2003 10:27:40 - 1.109
@@ -73,9 +73,6 @@
commons-daemon.jar=${commons-daemon.lib}/commons-daemon.jar
commons-daemon.loc=jakarta-commons/daemon
commons-daemon.cvs.loc=jakarta-commons/daemon
-commons-daemon.procrun.home=${commons-daemon.lib}/bin
-commons-daemon.procrun.exe=${commons-daemon.procrun.home}/tomcat.exe
-commons-daemon.procrunw.exe=${commons-daemon.procrun.home}/tomcatw.exe
commons-daemon.jsvc.tar.gz=${commons-daemon.lib}/bin/jsvc.tar.gz
1.161 +4 -2 jakarta-tomcat-5/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
retrieving revision 1.160
retrieving revision 1.161
diff -u -r1.160 -r1.161
--- build.xml 28 Sep 2003 12:23:27 - 1.160
+++ build.xml 29 Sep 2003 10:27:40 - 1.161
@@ -1266,8 +1266,10 @@
fileset dir=resources /
/copy
copy file=${nsis.installoptions.dll} todir=${tomcat.dist} /
-copy file=${commons-daemon.procrun.exe}
tofile=${tomcat.dist}/bin/tomcat.exe /
-copy file=${commons-daemon.procrunw.exe}
tofile=${tomcat.dist}/bin/tomcatw.exe /
+copy file=${jtc.home}/procrun/bin/tomcat.exe
+tofile=${tomcat.dist}/bin/tomcat.exe /
+copy file=${jtc.home}/procrun/bin/tomcatw.exe
+tofile=${tomcat.dist}/bin/tomcatw.exe /
filter token=VERSION value=${version}/
copy file=tomcat.nsi tofile=${tomcat.dist}/tomcat.nsi
filtering=true/
1.35 +3 -3 jakarta-tomcat-5/tomcat.nsi
Index: tomcat.nsi
===
RCS file: /home/cvs/jakarta-tomcat-5/tomcat.nsi,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- tomcat.nsi16 Jun 2003 21:15:40 - 1.34
+++ tomcat.nsi29 Sep 2003 10:27:40 - 1.35
@@ -130,7 +130,7 @@
Call configure
- ExecWait '$INSTDIR\bin\tomcatw.exe //IS//Tomcat5 --DisplayName Apache Tomcat
--Description Apache Tomcat @VERSION@ Server - http://jakarta.apache.org/tomcat/;
--Install $INSTDIR\bin\tomcat.exe --ImagePath $INSTDIR\bin\bootstrap.jar
--StartupClass org.apache.catalina.startup.Bootstrap;main;start --ShutdownClass
org.apache.catalina.startup.Bootstrap;main;stop --Java java --JavaOptions -Xrs
--Startup manual'
+ ExecWait '$INSTDIR\bin\tomcatw.exe //IS//Tomcat5 --Group Tomcat --DisplayName
Apache Tomcat --Description Apache Tomcat @VERSION@ Server -
http://jakarta.apache.org/tomcat/; --Install $INSTDIR\bin\tomcat.exe --ImagePath
$INSTDIR\bin\bootstrap.jar --StartupClass
org.apache.catalina.startup.Bootstrap;main;start --ShutdownClass
org.apache.catalina.startup.Bootstrap;main;stop --Java java --JavaOptions -Xrs
--Startup manual'
SectionEnd
@@ -222,7 +222,7 @@
Section -post
- ExecWait '$INSTDIR\bin\tomcatw.exe //US//Tomcat5 --JavaOptions
-Dcatalina.home=\$INSTDIR\#-Djava.endorsed.dirs=\$INSTDIR\common\endorsed\#-Xrs
--StdOutputFile $INSTDIR\logs\stdout.log --StdErrorFile $INSTDIR\logs\stderr.log
--WorkingPath $INSTDIR'
+ ExecWait '$INSTDIR\bin\tomcatw.exe //US//Tomcat5 --JavaOptions
-Dcatalina.home=\$INSTDIR\#-Djava.endorsed.dirs=\$INSTDIR\common\endorsed\#-Dsun.io.useCanonCaches=false#-Xrs
--StdOutputFile $INSTDIR\logs\stdout.log --StdErrorFile $INSTDIR\logs\stderr.log
--WorkingPath $INSTDIR'
WriteUninstaller $INSTDIR\Uninstall.exe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-5 build.properties.default build.xml tomcat.nsi
[EMAIL PROTECTED] wrote: remm2003/09/29 03:27:40 Modified:.build.properties.default build.xml tomcat.nsi Log: - Set -Dsun.io.useCanonCaches=false for Windows. This decreases startup performance significantly, but is needed for now (since Sun doesn't seem to be willing to fix the bug in a timely fashion). It doesn't decrease startup performance significantly at all (maybe 2-3%). I actually had forgotten to remove the Watchdog and tester webapps before looking at the results ;-) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23482] New: - Sequential stopping and re-starting of web application leads to out of memory exception
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=23482. 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=23482 Sequential stopping and re-starting of web application leads to out of memory exception Summary: Sequential stopping and re-starting of web application leads to out of memory exception Product: Tomcat 4 Version: 4.1.27 Platform: Other OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Webapps:Manager AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] While performing automated tests against a web application running under Tomcat 4.1.27, an out of memory exception occured. This is due to the fact, that Tomcat obviously does not release the allocated memory (at least only minor parts of it) when the corresponding application is stopped. It can be reproduced very easily: Open up the Windows Task Manager as well as the Tomcat Manager. Write down the memory usage of java.exe within Windows Task Manager. Now stop and start the examples application within Tomcat Manager several times. The increase of memory usage is noticeable. Performing these operations in conjunction with larger web applications will result in an Out Of Memory Exception. My environment is as follows: Tomcat Version Apache Tomcat/4.1.27 JVM Version 1.4.1_03-b02 JVM Vendor Sun Microsystems Inc. OS Name Windows 2000 OS Version 5.0 OS Architecture x86 Please investigate. Best regards, Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23482] - Sequential stopping and re-starting of web application leads to out of memory exception
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=23482. 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=23482 Sequential stopping and re-starting of web application leads to out of memory exception [EMAIL PROTECTED] changed: What|Removed |Added Severity|Critical|Minor Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2003-09-29 12:46 --- Many improvements have been made in 5.0 (it was quite complex), and simple, precompiled webapps will now be completely GCed. However, in many situations, class definitions of the old webapp instance cannot be GCed (shutdown hook set by Ant, thread local stuff), so there will be a resource leak. Please do not reopen the bug, as it cannot be addressed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23483] New: - More than 42 channels causes JK2 to segfault
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=23483. 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=23483 More than 42 channels causes JK2 to segfault Summary: More than 42 channels causes JK2 to segfault Product: Tomcat 4 Version: 4.1.27 Platform: PC OS/Version: Linux Status: NEW Severity: Critical Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] workers2.properties setting up connections to Apache2 works great for up to 42 constructs like: [channel.un:somename] info=AF_UNIX socket connecting to host file=/home/somename/jakarta-tomcat/work/jk2.socket debug=0 but as soon as I add the 43rd, Apache segfaults on the restart. Is there some hard coded array or something somewhere? I'm using the Jk2 that came with Tomcat 4.1.27 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
As part of the mod_jk 1.2.5 release I promised to move the JTC download to
www.apache.org/dist so that the downloads can be mirrored. Here are the
changes I propose to make as I set this up.
First, here is the directory layout for mirrored downloads at
/www/www.apache.org/dist/jakarta/tomcat-connectors :
KEYS
jk
jk/README.html
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz.asc -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk/binaries
jk/binaries/aix
jk/binaries/freebsd
jk/binaries/iseries
jk/binaries/linux
jk/binaries/macosx
jk/binaries/netware
jk/binaries/solaris
jk/binaries/win32
jk/source
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk2
jk2/README.html
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz.asc -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
jk2/binaries
jk2/binaries/aix
jk2/binaries/freebsd
jk2/binaries/iseries
jk2/binaries/linux
jk2/binaries/macosx
jk2/binaries/netware
jk2/binaries/solaris
jk2/binaries/win32
jk2/source
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
Each binary directory would contain a tar.gz, rpm, or zip for the binary release
rather than .dll or .so files. The archive would be named:
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.tar.gz (.zip for
windows, .rpm for linux rpm's)
linux rpms would go in the binaries/linux directory.
Here is an example for mod_jk 1.2.5 for FreeBsd on i386 for apache 2:
jakarta-tomcat-connector-jk-1.2.5-freebsd4.8-i386-apache-2.0.47.tar.gz
This will allow us to put multiple binaries in the same directory for different
jk release versions, OS versions, and web server versions and make managing
the mirrored download and archive.apache.org directories easier.
httpd includes the source with their binary distributions, I recommend that we do
the same. The binary release should contain the contents of the source release
plus the binary files.
Here is what I propose we do:
1. Coyote - /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/
This contains 9 coyote connector beta release and one release candidate.
Do we need to keep these? If not, since coyote comes with the Tomcat releases,
why not completely remove coyote from the tomcat-connectors download?
+1 to remove coyote from the download completely since it is part of the Tomcat release.
If we keep them, I will make the following changes.
Take each release directory and create both a tar.gz and .zip for the
release, sign each. i.e. The jar files in v1.0-b1 are put into
apache-tomcat-coyote-1.0-b1.tar.gz.
Place the tar.gz and zip files in the
/www/archive.apache.org/dist/jakarta/tomcat-connectors/coyote/binaries/ directory.
2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/
Remove the docs directory, point users to jakarta.apache.org/tomcat in the README.html.
Remove the nightly directory, no nightlies have been done.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
3. JK2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/
Remove the docs directory, point users to jakarta.apache.org/tomcat in the README.html.
Remove the nightly directory, last nightly was done Oct. 5 2002.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
4. Add a section to http://jakarta.apache.org/site/sourceindex.cgi for downloading
the
tomcat connectors from the mirror.
5. Use a .htaccess file to add a permanent redirect for
jakarta.apache.org/builds/jakarta-tomcat-connectors to
www.apache.org/dist/jakarta/tomcat-connectors/ .
Comments and suggestions welcome.
Regards,
Glenn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
Glenn Nielsen a écrit :
As part of the mod_jk 1.2.5 release I promised to move the JTC download to
www.apache.org/dist so that the downloads can be mirrored. Here are the
changes I propose to make as I set this up.
First, here is the directory layout for mirrored downloads at
/www/www.apache.org/dist/jakarta/tomcat-connectors :
KEYS
jk
jk/README.html
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz.asc -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk/binaries
jk/binaries/aix
jk/binaries/freebsd
jk/binaries/iseries
jk/binaries/linux
jk/binaries/macosx
jk/binaries/netware
jk/binaries/solaris
jk/binaries/win32
jk/source
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk2
jk2/README.html
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz.asc -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
jk2/binaries
jk2/binaries/aix
jk2/binaries/freebsd
jk2/binaries/iseries
jk2/binaries/linux
jk2/binaries/macosx
jk2/binaries/netware
jk2/binaries/solaris
jk2/binaries/win32
jk2/source
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
Each binary directory would contain a tar.gz, rpm, or zip for the binary
release
rather than .dll or .so files. The archive would be named:
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.tar.gz
(.zip for windows, .rpm for linux rpm's)
linux rpms would go in the binaries/linux directory.
Here is an example for mod_jk 1.2.5 for FreeBsd on i386 for apache 2:
jakarta-tomcat-connector-jk-1.2.5-freebsd4.8-i386-apache-2.0.47.tar.gz
This will allow us to put multiple binaries in the same directory for
different
jk release versions, OS versions, and web server versions and make managing
the mirrored download and archive.apache.org directories easier.
httpd includes the source with their binary distributions, I recommend
that we do
the same. The binary release should contain the contents of the source
release
plus the binary files.
Here is what I propose we do:
1. Coyote -
/www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/
This contains 9 coyote connector beta release and one release candidate.
Do we need to keep these? If not, since coyote comes with the Tomcat
releases,
why not completely remove coyote from the tomcat-connectors download?
+1 to remove coyote from the download completely since it is part of the
Tomcat release.
If we keep them, I will make the following changes.
Take each release directory and create both a tar.gz and .zip for the
release, sign each. i.e. The jar files in v1.0-b1 are put into
apache-tomcat-coyote-1.0-b1.tar.gz.
Place the tar.gz and zip files in the
/www/archive.apache.org/dist/jakarta/tomcat-connectors/coyote/binaries/
directory.
2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/
Remove the docs directory, point users to jakarta.apache.org/tomcat in
the README.html.
Remove the nightly directory, no nightlies have been done.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
3. JK2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/
Remove the docs directory, point users to jakarta.apache.org/tomcat in
the README.html.
Remove the nightly directory, last nightly was done Oct. 5 2002.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
4. Add a section to http://jakarta.apache.org/site/sourceindex.cgi for
downloading the
tomcat connectors from the mirror.
5. Use a .htaccess file to add a permanent redirect for
jakarta.apache.org/builds/jakarta-tomcat-connectors to
www.apache.org/dist/jakarta/tomcat-connectors/ .
Comments and suggestions welcome.
I'm fine with it but the Linux RPMs are problematic since there is by
now just too many distributions to follow :
- Redhat 6.x, 7.x, 8.x/9.x
- Suse
- Mandrake.
There is way too mixed case, Apache 1.3, 2.0, 1.3 with SSL, so I suggest
to make a link to www.jpackage.org which take care of all the current
distro and produce rpms accordingly...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
Glenn Nielsen wrote: 1. Coyote - /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/ This contains 9 coyote connector beta release and one release candidate. Do we need to keep these? If not, since coyote comes with the Tomcat releases, why not completely remove coyote from the tomcat-connectors download? +1 to remove coyote from the download completely since it is part of the Tomcat release. +1. 2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/ Remove the docs directory, point users to jakarta.apache.org/tomcat in the README.html. Remove the nightly directory, no nightlies have been done. Reorganize the releases as described above. Move old releases to archive.apache.org/dist, move the current release to www.apache.org/dist . 3. JK2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/ Remove the docs directory, point users to jakarta.apache.org/tomcat in the README.html. Remove the nightly directory, last nightly was done Oct. 5 2002. Reorganize the releases as described above. Move old releases to archive.apache.org/dist, move the current release to www.apache.org/dist . What will the new docs location be, then (I need to link it from the main TC docs) ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
Henri Gomez wrote:
Glenn Nielsen a écrit :
As part of the mod_jk 1.2.5 release I promised to move the JTC
download to
www.apache.org/dist so that the downloads can be mirrored. Here are the
changes I propose to make as I set this up.
First, here is the directory layout for mirrored downloads at
/www/www.apache.org/dist/jakarta/tomcat-connectors :
KEYS
jk
jk/README.html
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz.asc -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk/binaries
jk/binaries/aix
jk/binaries/freebsd
jk/binaries/iseries
jk/binaries/linux
jk/binaries/macosx
jk/binaries/netware
jk/binaries/solaris
jk/binaries/win32
jk/source
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk2
jk2/README.html
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz.asc -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
jk2/binaries
jk2/binaries/aix
jk2/binaries/freebsd
jk2/binaries/iseries
jk2/binaries/linux
jk2/binaries/macosx
jk2/binaries/netware
jk2/binaries/solaris
jk2/binaries/win32
jk2/source
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
Each binary directory would contain a tar.gz, rpm, or zip for the
binary release
rather than .dll or .so files. The archive would be named:
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.tar.gz
(.zip for windows, .rpm for linux rpm's)
linux rpms would go in the binaries/linux directory.
Here is an example for mod_jk 1.2.5 for FreeBsd on i386 for apache 2:
jakarta-tomcat-connector-jk-1.2.5-freebsd4.8-i386-apache-2.0.47.tar.gz
This will allow us to put multiple binaries in the same directory for
different
jk release versions, OS versions, and web server versions and make
managing
the mirrored download and archive.apache.org directories easier.
httpd includes the source with their binary distributions, I recommend
that we do
the same. The binary release should contain the contents of the
source release
plus the binary files.
Here is what I propose we do:
1. Coyote -
/www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/
This contains 9 coyote connector beta release and one release candidate.
Do we need to keep these? If not, since coyote comes with the Tomcat
releases,
why not completely remove coyote from the tomcat-connectors download?
+1 to remove coyote from the download completely since it is part of
the Tomcat release.
If we keep them, I will make the following changes.
Take each release directory and create both a tar.gz and .zip for the
release, sign each. i.e. The jar files in v1.0-b1 are put into
apache-tomcat-coyote-1.0-b1.tar.gz.
Place the tar.gz and zip files in the
/www/archive.apache.org/dist/jakarta/tomcat-connectors/coyote/binaries/
directory.
2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/
Remove the docs directory, point users to jakarta.apache.org/tomcat in
the README.html.
Remove the nightly directory, no nightlies have been done.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
3. JK2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/
Remove the docs directory, point users to jakarta.apache.org/tomcat in
the README.html.
Remove the nightly directory, last nightly was done Oct. 5 2002.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
4. Add a section to http://jakarta.apache.org/site/sourceindex.cgi for
downloading the
tomcat connectors from the mirror.
And something like:
http://www.apache.org/dyn/closer.cgi/jakarta-tomcat-connectors/jk2/ in the
mod_jk documentation we have a link to download.
5. Use a .htaccess file to add a permanent redirect for
jakarta.apache.org/builds/jakarta-tomcat-connectors to
www.apache.org/dist/jakarta/tomcat-connectors/ .
Comments and suggestions welcome.
I'm fine with it but the Linux RPMs are problematic since there is by
now just too many distributions to follow :
- Redhat 6.x, 7.x, 8.x/9.x
- Suse
- Mandrake.
There is way too mixed case, Apache 1.3, 2.0, 1.3 with SSL, so I suggest
to make a link to www.jpackage.org which take care of all the current
distro and produce rpms accordingly...
The *.so are quite easy to use
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.so
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 12428] - request.getUserPrincipal(): Misinterpretation of specification?
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=12428. 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=12428 request.getUserPrincipal(): Misinterpretation of specification? --- Additional Comments From [EMAIL PROTECTED] 2003-09-29 13:17 --- I tried your suggestion, code attached, but it did not work. Turns out that the filter is getting called pretty late in the game. By the time the filter is called, a null Principal was already seen and configured in to the context. I need to work at the Pipeline/Valve level to get this to work. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 tomcat.nsi
remm2003/09/29 06:16:08 Modified:.tomcat.nsi Log: - Group should actually not be used. I misunderstood Mladen's instructions. Revision ChangesPath 1.36 +2 -2 jakarta-tomcat-5/tomcat.nsi Index: tomcat.nsi === RCS file: /home/cvs/jakarta-tomcat-5/tomcat.nsi,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- tomcat.nsi29 Sep 2003 10:27:40 - 1.35 +++ tomcat.nsi29 Sep 2003 13:16:08 - 1.36 @@ -130,7 +130,7 @@ Call configure - ExecWait '$INSTDIR\bin\tomcatw.exe //IS//Tomcat5 --Group Tomcat --DisplayName Apache Tomcat --Description Apache Tomcat @VERSION@ Server - http://jakarta.apache.org/tomcat/; --Install $INSTDIR\bin\tomcat.exe --ImagePath $INSTDIR\bin\bootstrap.jar --StartupClass org.apache.catalina.startup.Bootstrap;main;start --ShutdownClass org.apache.catalina.startup.Bootstrap;main;stop --Java java --JavaOptions -Xrs --Startup manual' + ExecWait '$INSTDIR\bin\tomcatw.exe //IS//Tomcat5 --DisplayName Apache Tomcat --Description Apache Tomcat @VERSION@ Server - http://jakarta.apache.org/tomcat/; --Install $INSTDIR\bin\tomcat.exe --ImagePath $INSTDIR\bin\bootstrap.jar --StartupClass org.apache.catalina.startup.Bootstrap;main;start --ShutdownClass org.apache.catalina.startup.Bootstrap;main;stop --Java java --JavaOptions -Xrs --Startup manual' SectionEnd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
New tags
I propose putting new tags (hopefully on Friday, sometimes next week otherwise): - 5.0.13 (this could be a release candidate beta :)) - 4.1.28 (connector fixes, reloading fix, other fixes) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23489] New: - Problems when posting Unicode characters to a 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=23489. 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=23489 Problems when posting Unicode characters to a servlet Summary: Problems when posting Unicode characters to a servlet Product: Tomcat 4 Version: 4.0 Final Platform: PC OS/Version: Windows NT/2K Status: UNCONFIRMED Severity: Major Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When using forms that accept say ISO charsets that represents characters on 2 bytes, even though the browser encodes them properly (e.g. %413 etc.), they are translated into the String as 2 separate characters( e.g. as if it was %41%03). It works fine with UTF-8 chars as far as I can cee though. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23490] New: - [PATCH] ant task I18N for manager 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=23490. 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=23490 [PATCH] ant task I18N for manager webapp Summary: [PATCH] ant task I18N for manager webapp Product: Tomcat 5 Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Webapps:Manager AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, Current ant task don't work for other than English. Here is a patch. Could you commit it? regargs, Takashi Okamoto Index: AbstractCatalinaTask.java === RCS file: /home/cvspublic/jakarta-tomcat-catalina/catalina/src/share/org/apache/ catalina/ant/AbstractCatalinaTask.java,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 AbstractCatalinaTask.java --- AbstractCatalinaTask.java 18 Jul 2002 16:48:13 - 1.1.1.1 +++ AbstractCatalinaTask.java 29 Sep 2003 16:46:36 - @@ -89,7 +89,10 @@ // - Instance Variables - + /** +* manager webapp's encoding. +*/ +private static String CHARSET = utf-8; // - Properties @@ -245,7 +248,7 @@ } // Process the response message -reader = new InputStreamReader(hconn.getInputStream()); +reader = new InputStreamReader(hconn.getInputStream(), CHARSET); StringBuffer buff = new StringBuffer(); String error = null; boolean first = true; - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 3.3.2
-Original Message- From: Henri Gomez [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 5:56 AM To: Tomcat Developers List Subject: TC 3.3.2 Hi to all, I commited the last part of clean imports and started to take a look at bugzilla where many reports seems still open. What's the strategy now ? I should have my builds running again shortly. I'll try to get the nightly binaries updated and accessible again. Should we close those which seems invalid ? +1 I'll help review open bugs. I'm also in favor of WONTFIX any Tomcat 3.2.x related bugs. Larry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2
- Original Message - From: Henri Gomez [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, September 29, 2003 2:55 AM Subject: TC 3.3.2 Hi to all, I commited the last part of clean imports and started to take a look at bugzilla where many reports seems still open. What's the strategy now ? Should we close those which seems invalid ? Without looking, I believe that most of the open bugs for 3.3 are either for the native connectors (and so are really j-t-c bugs), or for the Http10Interceptor (which we are deprecating/removing). Of course, most of the 91 open Tomcat 3 bugs are for 3.2.x. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
TC4.1: StandardWrapperValve infinite recursion
Hello I have a question regarding the status of Bug# 19312 (and 21834) http://marc.theaimsgroup.com/?l=tomcat-devm=105170151514979w=2 It was reported against 4.1.24 but is not fixed in 4.1.27 nor is it fixed in the jakarta-tomcat-4.0 CVS tree. Someone was working on it in April but nothing has happened. The suggested patch look fine to me and makes the two log() methods in the class work the same way - fallback to System.out if no logger can be found. Any particular reason for not applying it? We have seen two serious negative effects caused by the infinite recursion in the log method: - JVM heap increases rapidly to the max value before the thread trying to log crashes with OOM or stack overflow. The JVM never releases this memory to the OS for some reason. - When using the -server flag the JVM would sometimes hang when this bug was hit and only a 'kill -9' would be able to stop it. /Urban - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23390] - Invalid direct reference to form
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=23390. 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=23390 Invalid direct reference to form --- Additional Comments From [EMAIL PROTECTED] 2003-09-29 18:05 --- I have my web.xml set up session-config session-timeout120/session-timeout /session-config I do not reference my login page directly I am redirected from my index.jsp. If I log in right away everything works correctly, but if I open my page and do not log in until after 2 hours I get the error message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat 4.1 XSS vulnerability
Anyone know how serious this is?
It also appears to affect Tomcat 4.1.27 when using mod_jk as well. Below
is a sample trace of a HTTP session.
-Dave
telnet localhost 8080
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET /666%0a%0ascriptalert(asdf);/script666.jsp HTTP/1.0
Host: localhost
HTTP/1.1 404 /666
scriptalert(asdf);/script666.jsp
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Date: Mon, 29 Sep 2003 18:39:23 GMT
Server: Apache Coyote/1.0
Connection: close
htmlheadtitleApache Tomcat/4.1.27 - Error
report/titleSTYLE!--H1{font-family : sans-serif,Arial,Tahoma;color :
white;background-color : #0086b2;} H3{font-family :
sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
BODY{font-family : sans-serif,Arial,Tahoma;color : black;background-color
: white;} B{color : white;background-color : #0086b2;} HR{color :
#0086b2;} --/STYLE /headbodyh1HTTP Status 404 - /666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp/h1HR
size=1 noshadepbtype/b Status report/ppbmessage/b u/666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp/u/ppbdescription/b
uThe requested resource (/666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp) is not
available./u/pHR size=1 noshadeh3Apache
Tomcat/4.1.27/h3/body/htmlConnection closed by foreign host.
On Sun, September 28, 2003 at 3:14 am, Kan Ogawa sent the following
Jakarta Tomcat 4.1 cross-site scripting vulnerability, which was
reported last year, is not yet resolved.
http://www.securityfocus.com/archive/82/288502/2002-08-16/2002-08-22/0
I verified this vulnerability on Tomcat 4.1.27 with Coyote HTTP/1.1
connector.
http://localhost:8080/666%0a%0ascriptalert(asdf);/script666.jsp
On the other hand, on Tomcat 5.0, it was not reproduced.
Do you neglect to resolve it to Tomcat 4.x, Tomcat committers?
Regards,
--
Kan Ogawa
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jakarta Tomcat 4.1 XSS vulnerability
Howdy,
I'm not a big security buff, but three things come to mind:
- The original post with the exploit is more than a year old, yet we
haven't heard anything about this actually used maliciously -- how come?
- Is it really a vulnerability? What can you get from this exploit?
All I see is tomcat returning a 404 (not found) response with the
javascript specified in the GET request, but javascript is executed on
the client anyhow, so who cares?
- What would the fix be? Not include the requested URL in the default
404 response page?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: David Rees [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 2:41 PM
To: Tomcat Developers List
Subject: Re: Jakarta Tomcat 4.1 XSS vulnerability
Anyone know how serious this is?
It also appears to affect Tomcat 4.1.27 when using mod_jk as well.
Below
is a sample trace of a HTTP session.
-Dave
telnet localhost 8080
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET /666%0a%0ascriptalert(asdf);/script666.jsp HTTP/1.0
Host: localhost
HTTP/1.1 404 /666
scriptalert(asdf);/script666.jsp
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Date: Mon, 29 Sep 2003 18:39:23 GMT
Server: Apache Coyote/1.0
Connection: close
htmlheadtitleApache Tomcat/4.1.27 - Error
report/titleSTYLE!--H1{font-family : sans-serif,Arial,Tahoma;color
:
white;background-color : #0086b2;} H3{font-family :
sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
BODY{font-family : sans-serif,Arial,Tahoma;color :
black;background-color
: white;} B{color : white;background-color : #0086b2;} HR{color :
#0086b2;} --/STYLE /headbodyh1HTTP Status 404 - /666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp/h1HR
size=1 noshadepbtype/b Status report/ppbmessage/b
u/666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp/u/pp
bd
escription/b
uThe requested resource (/666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp) is not
available./u/pHR size=1 noshadeh3Apache
Tomcat/4.1.27/h3/body/htmlConnection closed by foreign host.
On Sun, September 28, 2003 at 3:14 am, Kan Ogawa sent the following
Jakarta Tomcat 4.1 cross-site scripting vulnerability, which was
reported last year, is not yet resolved.
http://www.securityfocus.com/archive/82/288502/2002-08-16/2002-08-22/0
I verified this vulnerability on Tomcat 4.1.27 with Coyote HTTP/1.1
connector.
http://localhost:8080/666%0a%0ascriptalert(asdf);/script666.jsp
On the other hand, on Tomcat 5.0, it was not reproduced.
Do you neglect to resolve it to Tomcat 4.x, Tomcat committers?
Regards,
--
Kan Ogawa
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
Henri Gomez wrote:
Glenn Nielsen a écrit :
As part of the mod_jk 1.2.5 release I promised to move the JTC
download to
www.apache.org/dist so that the downloads can be mirrored. Here are the
changes I propose to make as I set this up.
First, here is the directory layout for mirrored downloads at
/www/www.apache.org/dist/jakarta/tomcat-connectors :
KEYS
jk
jk/README.html
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz.asc -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk/binaries
jk/binaries/aix
jk/binaries/freebsd
jk/binaries/iseries
jk/binaries/linux
jk/binaries/macosx
jk/binaries/netware
jk/binaries/solaris
jk/binaries/win32
jk/source
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk2
jk2/README.html
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz.asc -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
jk2/binaries
jk2/binaries/aix
jk2/binaries/freebsd
jk2/binaries/iseries
jk2/binaries/linux
jk2/binaries/macosx
jk2/binaries/netware
jk2/binaries/solaris
jk2/binaries/win32
jk2/source
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
Each binary directory would contain a tar.gz, rpm, or zip for the
binary release
rather than .dll or .so files. The archive would be named:
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.tar.gz
(.zip for windows, .rpm for linux rpm's)
linux rpms would go in the binaries/linux directory.
Here is an example for mod_jk 1.2.5 for FreeBsd on i386 for apache 2:
jakarta-tomcat-connector-jk-1.2.5-freebsd4.8-i386-apache-2.0.47.tar.gz
This will allow us to put multiple binaries in the same directory for
different
jk release versions, OS versions, and web server versions and make
managing
the mirrored download and archive.apache.org directories easier.
httpd includes the source with their binary distributions, I recommend
that we do
the same. The binary release should contain the contents of the
source release
plus the binary files.
Here is what I propose we do:
1. Coyote -
/www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/
This contains 9 coyote connector beta release and one release candidate.
Do we need to keep these? If not, since coyote comes with the Tomcat
releases,
why not completely remove coyote from the tomcat-connectors download?
+1 to remove coyote from the download completely since it is part of
the Tomcat release.
If we keep them, I will make the following changes.
Take each release directory and create both a tar.gz and .zip for the
release, sign each. i.e. The jar files in v1.0-b1 are put into
apache-tomcat-coyote-1.0-b1.tar.gz.
Place the tar.gz and zip files in the
/www/archive.apache.org/dist/jakarta/tomcat-connectors/coyote/binaries/
directory.
2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/
Remove the docs directory, point users to jakarta.apache.org/tomcat in
the README.html.
Remove the nightly directory, no nightlies have been done.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
3. JK2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/
Remove the docs directory, point users to jakarta.apache.org/tomcat in
the README.html.
Remove the nightly directory, last nightly was done Oct. 5 2002.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
4. Add a section to http://jakarta.apache.org/site/sourceindex.cgi for
downloading the
tomcat connectors from the mirror.
5. Use a .htaccess file to add a permanent redirect for
jakarta.apache.org/builds/jakarta-tomcat-connectors to
www.apache.org/dist/jakarta/tomcat-connectors/ .
Comments and suggestions welcome.
I'm fine with it but the Linux RPMs are problematic since there is by
now just too many distributions to follow :
- Redhat 6.x, 7.x, 8.x/9.x
- Suse
- Mandrake.
There is way too mixed case, Apache 1.3, 2.0, 1.3 with SSL, so I suggest
to make a link to www.jpackage.org which take care of all the current
distro and produce rpms accordingly...
I am not familiar with jpackage, are you saying that they are creating
distributions of mod_jk for linux?
Glenn
--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
--
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
Remy Maucherat wrote: Glenn Nielsen wrote: 1. Coyote - /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/ This contains 9 coyote connector beta release and one release candidate. Do we need to keep these? If not, since coyote comes with the Tomcat releases, why not completely remove coyote from the tomcat-connectors download? +1 to remove coyote from the download completely since it is part of the Tomcat release. +1. 2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/ Remove the docs directory, point users to jakarta.apache.org/tomcat in the README.html. Remove the nightly directory, no nightlies have been done. Reorganize the releases as described above. Move old releases to archive.apache.org/dist, move the current release to www.apache.org/dist . 3. JK2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/ Remove the docs directory, point users to jakarta.apache.org/tomcat in the README.html. Remove the nightly directory, last nightly was done Oct. 5 2002. Reorganize the releases as described above. Move old releases to archive.apache.org/dist, move the current release to www.apache.org/dist . What will the new docs location be, then (I need to link it from the main TC docs) ? There are already docs for jk/jk2 in the tomcat docs directory: I was going to point the README.html file at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html The goal is to only put source or binary distributions on www.apache.org/dist and keep all the docs at jakarta.apacheo.org/tomcat/ . Generated docs for a specific version are also available within the source distribution. 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
jean-frederic clere wrote:
Henri Gomez wrote:
Glenn Nielsen a écrit :
As part of the mod_jk 1.2.5 release I promised to move the JTC
download to
www.apache.org/dist so that the downloads can be mirrored. Here are the
changes I propose to make as I set this up.
First, here is the directory layout for mirrored downloads at
/www/www.apache.org/dist/jakarta/tomcat-connectors :
KEYS
jk
jk/README.html
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz.asc -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk/binaries
jk/binaries/aix
jk/binaries/freebsd
jk/binaries/iseries
jk/binaries/linux
jk/binaries/macosx
jk/binaries/netware
jk/binaries/solaris
jk/binaries/win32
jk/source
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk2
jk2/README.html
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz.asc -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
jk2/binaries
jk2/binaries/aix
jk2/binaries/freebsd
jk2/binaries/iseries
jk2/binaries/linux
jk2/binaries/macosx
jk2/binaries/netware
jk2/binaries/solaris
jk2/binaries/win32
jk2/source
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
Each binary directory would contain a tar.gz, rpm, or zip for the
binary release
rather than .dll or .so files. The archive would be named:
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.tar.gz
(.zip for windows, .rpm for linux rpm's)
linux rpms would go in the binaries/linux directory.
Here is an example for mod_jk 1.2.5 for FreeBsd on i386 for apache 2:
jakarta-tomcat-connector-jk-1.2.5-freebsd4.8-i386-apache-2.0.47.tar.gz
This will allow us to put multiple binaries in the same directory for
different
jk release versions, OS versions, and web server versions and make
managing
the mirrored download and archive.apache.org directories easier.
httpd includes the source with their binary distributions, I
recommend that we do
the same. The binary release should contain the contents of the
source release
plus the binary files.
Here is what I propose we do:
1. Coyote -
/www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/
This contains 9 coyote connector beta release and one release candidate.
Do we need to keep these? If not, since coyote comes with the Tomcat
releases,
why not completely remove coyote from the tomcat-connectors download?
+1 to remove coyote from the download completely since it is part of
the Tomcat release.
If we keep them, I will make the following changes.
Take each release directory and create both a tar.gz and .zip for the
release, sign each. i.e. The jar files in v1.0-b1 are put into
apache-tomcat-coyote-1.0-b1.tar.gz.
Place the tar.gz and zip files in the
/www/archive.apache.org/dist/jakarta/tomcat-connectors/coyote/binaries/
directory.
2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/
Remove the docs directory, point users to jakarta.apache.org/tomcat
in the README.html.
Remove the nightly directory, no nightlies have been done.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
3. JK2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/
Remove the docs directory, point users to jakarta.apache.org/tomcat
in the README.html.
Remove the nightly directory, last nightly was done Oct. 5 2002.
Reorganize the releases as described above. Move old releases to
archive.apache.org/dist,
move the current release to www.apache.org/dist .
4. Add a section to http://jakarta.apache.org/site/sourceindex.cgi
for downloading the
tomcat connectors from the mirror.
And something like:
http://www.apache.org/dyn/closer.cgi/jakarta-tomcat-connectors/jk2/ in
the mod_jk documentation we have a link to download.
Ok, nice catch. Yes, the docs will need to have any links to the
mod_jk download page fixed.
5. Use a .htaccess file to add a permanent redirect for
jakarta.apache.org/builds/jakarta-tomcat-connectors to
www.apache.org/dist/jakarta/tomcat-connectors/ .
Comments and suggestions welcome.
I'm fine with it but the Linux RPMs are problematic since there is by
now just too many distributions to follow :
- Redhat 6.x, 7.x, 8.x/9.x
- Suse
- Mandrake.
There is way too mixed case, Apache 1.3, 2.0, 1.3 with SSL, so I
suggest to make a link to www.jpackage.org which take care of all the
current distro and produce rpms accordingly...
The *.so are quite easy to use
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.so
I'm ok with that as long as we no longer need a separate directory for
each released version. I still
RE: Jakarta Tomcat 4.1 XSS vulnerability
On Mon, September 29, 2003 1at 1:57 am, Shapira, Yoav sent the following I'm not a big security buff, but three things come to mind: - The original post with the exploit is more than a year old, yet we haven't heard anything about this actually used maliciously -- how come? Can't answer this one myself... - Is it really a vulnerability? What can you get from this exploit? You can hijack the user's session or steal information from a user's cookie pretty easily with a XSS flaw such as this one. All I see is tomcat returning a 404 (not found) response with the javascript specified in the GET request, but javascript is executed on the client anyhow, so who cares? - What would the fix be? Not include the requested URL in the default 404 response page? That's not the problem. If you look at the trace in my previous post, the problem is that the javascript was printed out un-encoded before any of the response headers. You can try plugging in the URL in your browser (just tack on 666%0a%0ascriptalert(asdf);/script666.jsp a URL) and you will receive a Javascript alert asdf. Malicious users could obviously write something much more malicious than a simple alert used as the example. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat 4.1 XSS vulnerability
Remy has already patched the HTTP Connector for this one (both Tomcat 45).
I believe that the patch still needs to be ported to the JK2 Connector.
- Original Message -
From: Shapira, Yoav [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Monday, September 29, 2003 11:57 AM
Subject: RE: Jakarta Tomcat 4.1 XSS vulnerability
Howdy,
I'm not a big security buff, but three things come to mind:
- The original post with the exploit is more than a year old, yet we
haven't heard anything about this actually used maliciously -- how come?
- Is it really a vulnerability? What can you get from this exploit?
All I see is tomcat returning a 404 (not found) response with the
javascript specified in the GET request, but javascript is executed on
the client anyhow, so who cares?
- What would the fix be? Not include the requested URL in the default
404 response page?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: David Rees [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 2:41 PM
To: Tomcat Developers List
Subject: Re: Jakarta Tomcat 4.1 XSS vulnerability
Anyone know how serious this is?
It also appears to affect Tomcat 4.1.27 when using mod_jk as well.
Below
is a sample trace of a HTTP session.
-Dave
telnet localhost 8080
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET /666%0a%0ascriptalert(asdf);/script666.jsp HTTP/1.0
Host: localhost
HTTP/1.1 404 /666
scriptalert(asdf);/script666.jsp
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Date: Mon, 29 Sep 2003 18:39:23 GMT
Server: Apache Coyote/1.0
Connection: close
htmlheadtitleApache Tomcat/4.1.27 - Error
report/titleSTYLE!--H1{font-family : sans-serif,Arial,Tahoma;color
:
white;background-color : #0086b2;} H3{font-family :
sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
BODY{font-family : sans-serif,Arial,Tahoma;color :
black;background-color
: white;} B{color : white;background-color : #0086b2;} HR{color :
#0086b2;} --/STYLE /headbodyh1HTTP Status 404 - /666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp/h1HR
size=1 noshadepbtype/b Status report/ppbmessage/b
u/666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp/u/pp
bd
escription/b
uThe requested resource (/666
lt;scriptgt;alert(quot;asdfquot;);lt;/scriptgt;666.jsp) is not
available./u/pHR size=1 noshadeh3Apache
Tomcat/4.1.27/h3/body/htmlConnection closed by foreign host.
On Sun, September 28, 2003 at 3:14 am, Kan Ogawa sent the following
Jakarta Tomcat 4.1 cross-site scripting vulnerability, which was
reported last year, is not yet resolved.
http://www.securityfocus.com/archive/82/288502/2002-08-16/2002-08-22/0
I verified this vulnerability on Tomcat 4.1.27 with Coyote HTTP/1.1
connector.
http://localhost:8080/666%0a%0ascriptalert(asdf);/script666.jsp
On the other hand, on Tomcat 5.0, it was not reproduced.
Do you neglect to resolve it to Tomcat 4.x, Tomcat committers?
Regards,
--
Kan Ogawa
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged. This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else. If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message is intended only for the use of the person(s) listed above as the
intended recipient(s), and may contain information that is PRIVILEGED and
CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or
distribute this message or any attachment. If you received this communication in
error, please notify us immediately by e-mail and then delete all copies of this
message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent through the
Internet is not secure. Do not send confidential or sensitive information, such as
social security numbers, account numbers, personal identification numbers and
passwords, to us via ordinary (unencrypted) e-mail.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat 4.1 XSS vulnerability
On Mon, September 29, 2003 1at 2:32 pm, Bill Barker sent the following Remy has already patched the HTTP Connector for this one (both Tomcat 45). I believe that the patch still needs to be ported to the JK2 Connector. Thanks for the update, Bill. Hope to see Tomcat 4.1.28 out soon, look like we could be seeing it as soon as next week. Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jakarta Tomcat 4.1 XSS vulnerability
Howdy, This is interesting, hopefully you won't mind educating me a bit further... - Is it really a vulnerability? What can you get from this exploit? You can hijack the user's session or steal information from a user's cookie pretty easily with a XSS flaw such as this one. How would you hijack the user's session? By that do you mean just getting the session ID from the JSESSION cookie on the user's hard-drive? That's not the problem. If you look at the trace in my previous post, the problem is that the javascript was printed out un-encoded before any of the response headers. You can try plugging in the URL in your browser (just tack on 666%0a%0ascriptalert(asdf);/script666.jsp a URL) and you will receive a Javascript alert asdf. Malicious users could obviously write something much more malicious than a simple alert used as the example. But whatever a malicious user writes would be executed on their own PC, right? It won't run on the tomcat server or on anyone else's machines. So the worst they can do is harm their own PC? Or did I misunderstand something? Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jakarta Tomcat 4.1 XSS vulnerability
Hey, Just thought I'd pop in on this one. Fairly standard XSS attack: -Insert/execute javascript to pull some key piece of data (ex. value of the jsessionid cookie) -This same bit of javascript will then make a http request (through one several means) to an attackers website which involves that key piece of data (ex. as a get parameter) Now I'm not sure if TC uses some additional authentication methods to prevent this from being an issue (ex. a session can only come from one ip). So this may or may not be a valid scenario. Chad Johnson Web Services Developer WS Packaging Group, Inc. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 2:34 PM To: Tomcat Developers List Subject: RE: Jakarta Tomcat 4.1 XSS vulnerability Howdy, This is interesting, hopefully you won't mind educating me a bit further... - Is it really a vulnerability? What can you get from this exploit? You can hijack the user's session or steal information from a user's cookie pretty easily with a XSS flaw such as this one. How would you hijack the user's session? By that do you mean just getting the session ID from the JSESSION cookie on the user's hard-drive? That's not the problem. If you look at the trace in my previous post, the problem is that the javascript was printed out un-encoded before any of the response headers. You can try plugging in the URL in your browser (just tack on 666%0a%0ascriptalert(asdf);/script666.jsp a URL) and you will receive a Javascript alert asdf. Malicious users could obviously write something much more malicious than a simple alert used as the example. But whatever a malicious user writes would be executed on their own PC, right? It won't run on the tomcat server or on anyone else's machines. So the worst they can do is harm their own PC? Or did I misunderstand something? Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jakarta Tomcat 4.1 XSS vulnerability
On Mon, September 29, 2003 1at 2:34 pm, Shapira, Yoav sent the following Howdy, This is interesting, hopefully you won't mind educating me a bit further... Not at all, but keep in mind I haven't studied all that much myself... ;-) - Is it really a vulnerability? What can you get from this exploit? You can hijack the user's session or steal information from a user's cookie pretty easily with a XSS flaw such as this one. How would you hijack the user's session? By that do you mean just getting the session ID from the JSESSION cookie on the user's hard-drive? Once you are able to insert arbritrary Javascript into a page, you could use that power to submit a request to your own website with the JSESSION cookie details. So an example scenario would look like this: 1. User has session open to www.unsecurebank.com. 2. User receives email from malicious user saying Buy my product here! but is actually a link to www.unsecurebank.com. The link exploits the XSS vulnerability and uses Javascript to send the cookie information back to the malicous user's website. 3. Malicous user now has access to www.unsecurebank.com. If www.unsecurebank.com also stored sensitive information in any cookies, the malicious user would now have that information as well! In this cause, www.unsecurebank.com could also perform IP address confirmation along with the JSESSION id, but this is only reliable when using HTTPS/SSL. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jakarta Tomcat 4.1 XSS vulnerability
Howdy, OK, makes sense. Thanks for the examples! Yoav Shapira Millennium ChemInformatics -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 3:50 PM To: Tomcat Developers List Subject: RE: Jakarta Tomcat 4.1 XSS vulnerability On Mon, September 29, 2003 1at 2:34 pm, Shapira, Yoav sent the following Howdy, This is interesting, hopefully you won't mind educating me a bit further... Not at all, but keep in mind I haven't studied all that much myself... ;-) - Is it really a vulnerability? What can you get from this exploit? You can hijack the user's session or steal information from a user's cookie pretty easily with a XSS flaw such as this one. How would you hijack the user's session? By that do you mean just getting the session ID from the JSESSION cookie on the user's hard-drive? Once you are able to insert arbritrary Javascript into a page, you could use that power to submit a request to your own website with the JSESSION cookie details. So an example scenario would look like this: 1. User has session open to www.unsecurebank.com. 2. User receives email from malicious user saying Buy my product here! but is actually a link to www.unsecurebank.com. The link exploits the XSS vulnerability and uses Javascript to send the cookie information back to the malicous user's website. 3. Malicous user now has access to www.unsecurebank.com. If www.unsecurebank.com also stored sensitive information in any cookies, the malicious user would now have that information as well! In this cause, www.unsecurebank.com could also perform IP address confirmation along with the JSESSION id, but this is only reliable when using HTTPS/SSL. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat 4.1 XSS vulnerability
David Rees wrote: Anyone know how serious this is? Lol. If you're affected by XSS, then you have a problem (no site in the world deserves any privilege: *all* need javascript blocking these days). It also appears to affect Tomcat 4.1.27 when using mod_jk as well. Below is a sample trace of a HTTP session. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat 4.1 XSS vulnerability
- Original Message - From: David Rees [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, September 29, 2003 12:33 PM Subject: Re: Jakarta Tomcat 4.1 XSS vulnerability On Mon, September 29, 2003 1at 2:32 pm, Bill Barker sent the following Remy has already patched the HTTP Connector for this one (both Tomcat 45). I believe that the patch still needs to be ported to the JK2 Connector. Thanks for the update, Bill. Hope to see Tomcat 4.1.28 out soon, look like we could be seeing it as soon as next week. Ok, that's what I get for working from memory. Actually, Remy's patch is currently only in TC 5. It still needs to be applied to TC 4 (as well as the JK2 Connector for both versions). Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat 4.1 XSS vulnerability
Actually this could be issue on a poorly configured site where the admin does not override the default error pages. It would make it very easy to steal someone's cookies or session. So while might be an issue (I personally haven't checked), its not an issue if the admin configures custom error pages to show instead of displaying the default. -Tim Remy Maucherat wrote: David Rees wrote: Anyone know how serious this is? Lol. If you're affected by XSS, then you have a problem (no site in the world deserves any privilege: *all* need javascript blocking these days). It also appears to affect Tomcat 4.1.27 when using mod_jk as well. Below is a sample trace of a HTTP session. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23502] New: - Incorrect path in generated SMAP file entries
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=23502. 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=23502 Incorrect path in generated SMAP file entries Summary: Incorrect path in generated SMAP file entries Product: Tomcat 5 Version: 5.0.12 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] One of the new features of Jasper in Tomcat 5 is that it attaches a Source Map attribute to class files to describe the file name and line number mapping from a JSP source file to the generated Java source file. The SMAP that I see in the class files generated by Jasper (5.0.12 beta) has a problem: In the *F section, there's a pair of lines that defines the JSP file. The first line is of the form + id source-name, where id is a unique identifier and source-name is the name of the JSP file. The source name created by Jasper contains path information, but according to JSR-045, it should be without path information. For example, when running the num/numguess.jsp program, the following lines are generated: + 0 /num/numguess.jsp num/numguess.jsp but this should be + 0 numguess.jsp num/numguess.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jakarta Tomcat 4.1 XSS vulnerability
On Mon, September 29, 2003 1at 2:49 pm, Shapira, Yoav sent the following Howdy, OK, makes sense. Thanks for the examples! Glad I could help. Hopefully you (and others) can use this information while designing web applications to avoid similar XSS issues in the future even if they are relatively unlikely to be exploited. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat 4.1 XSS vulnerability
I've found a very good explanation of XSS: http://www.spidynamics.com/whitepapers/SPIcross-sitescripting.pdf Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com [EMAIL PROTECTED] 9/29/03 2:26:54 PM Actually this could be issue on a poorly configured site where the admin does not override the default error pages. It would make it very easy to steal someone's cookies or session. So while might be an issue (I personally haven't checked), its not an issue if the admin configures custom error pages to show instead of displaying the default. -Tim Remy Maucherat wrote: David Rees wrote: Anyone know how serious this is? Lol. If you're affected by XSS, then you have a problem (no site in the world deserves any privilege: *all* need javascript blocking these days). It also appears to affect Tomcat 4.1.27 when using mod_jk as well. Below is a sample trace of a HTTP session. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
./configure -with-apxs=/usr/local/apache2/bin/apxsGlenn Nielsen wrote: As part of the mod_jk 1.2.5 release I promised to move the JTC download to BTW you forgot to generate a configure file for the release, users will have to run buildconf.sh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
Joseph Shraibman wrote: ./configure -with-apxs=/usr/local/apache2/bin/apxsGlenn Nielsen wrote: As part of the mod_jk 1.2.5 release I promised to move the JTC download to BTW you forgot to generate a configure file for the release, users will have to run buildconf.sh Running buildconf.sh is in the building mod_jk from source instructions. Glenn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23471] - No Java compiler was found to compile the generated source for the JSP
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=23471. 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=23471 No Java compiler was found to compile the generated source for the JSP --- Additional Comments From [EMAIL PROTECTED] 2003-09-30 01:07 --- I tried test again, when error in scriptlet(In % % block), jasper can reports error exactly, while error in %! % block, it reports as below. First reading this report, I have thought that there are some problems on my runtime environment, In fact, the environment is OK. I think the reports should enhance. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PATCH] ./jk/native/apache-2.0/mod_jk.c compile with Apache 2.1
Hi,
with Apache 2.1 and APR 1.0 seems that apu_compat.h is removed (see APR-util Changes);
attached a patch which works for me with both APR 0.9.4 and APR 1.0.0
Guenter.
--- mod_jk.c.orig Sat Sep 06 17:37:20 2003
+++ mod_jk.cTue Sep 30 03:57:24 2003
@@ -67,7 +67,6 @@
* mod_jk: keeps all servlet/jakarta related ramblings together.
*/
-#include apu_compat.h
#include ap_config.h
#include apr_lib.h
#include apr_date.h
@@ -88,9 +87,16 @@
/* moved to apr since http-2.0.19-dev */
#if (MODULE_MAGIC_NUMBER_MAJOR 20010523)
+#define apr_date_parse_http ap_parseHTTPdate
#include util_date.h
#endif
+/* changed with apr 1.0 */
+#include apr_version.h
+#if (APR_MAJOR_VERSION 1)
+#define apr_filepath_name_get apr_filename_of_pathname
+#endif
+
#include apr_strings.h
/*
* Jakarta (jk_) include files
@@ -273,7 +279,7 @@
* If the script gave us a Last-Modified header, we can't just
* pass it on blindly because of restrictions on future values.
*/
-ap_update_mtime(r, ap_parseHTTPdate(header_values[h]));
+ap_update_mtime(r, apr_date_parse_http(header_values[h]));
ap_set_last_modified(r);
} else {
apr_table_add(r-headers_out,
@@ -833,7 +839,7 @@
}
value = tmpv;
} else {
-value = ap_pstrdup(cmd-pool, value);
+value = apr_pstrdup(cmd-pool, value);
}
if(value) {
@@ -959,8 +965,8 @@
int *strl;
apr_array_header_t *format = conf-format;
-strs = ap_palloc(r-pool, sizeof(char *) * (format-nelts));
-strl = ap_palloc(r-pool, sizeof(int) * (format-nelts));
+strs = apr_palloc(r-pool, sizeof(char *) * (format-nelts));
+strl = apr_palloc(r-pool, sizeof(int) * (format-nelts));
items = (request_log_format_item *) format-elts;
for (i = 0; i format-nelts; ++i) {
strs[i] = process_item(r, items[i]);
@@ -968,7 +974,7 @@
for (i = 0; i format-nelts; ++i) {
len += strl[i] = strlen(strs[i]);
}
-str = ap_palloc(r-pool, len + 1);
+str = apr_palloc(r-pool, len + 1);
for (i = 0, s = str; i format-nelts; ++i) {
memcpy(s, strs[i], strl[i]);
s += strl[i];
@@ -1006,13 +1012,13 @@
static const char *log_worker_name(request_rec *r, char *a)
{
-return ap_table_get(r-notes, JK_WORKER_ID);
+return apr_table_get(r-notes, JK_WORKER_ID);
}
static const char *log_request_duration(request_rec *r, char *a)
{
-return ap_table_get(r-notes, JK_DURATION);
+return apr_table_get(r-notes, JK_DURATION);
}
static const char *log_request_line(request_rec *r, char *a)
@@ -1022,7 +1028,7 @@
* (note the truncation before the protocol string for HTTP/0.9 requests)
* (note also that r-the_request contains the unmodified request)
*/
-return (r-parsed_uri.password) ? ap_pstrcat(r-pool, r-method, ,
+return (r-parsed_uri.password) ? apr_pstrcat(r-pool, r-method, ,
apr_uri_unparse(r-pool, r-parsed_uri, 0),
r-assbackwards ? NULL : , r-protocol,
NULL)
: r-the_request;
@@ -1065,7 +1071,7 @@
}
static const char *log_request_query(request_rec *r, char *a)
{
-return (r-args != NULL) ? ap_pstrcat(r-pool, ?, r-args, NULL)
+return (r-args != NULL) ? apr_pstrcat(r-pool, ?, r-args, NULL)
: ;
}
static const char *log_status(request_rec *r, char *a)
@@ -1171,7 +1177,7 @@
* This might allocate a few chars extra if there's a backslash
* escape in the format string.
*/
-it-arg = ap_palloc(p, s - *sa + 1);
+it-arg = apr_palloc(p, s - *sa + 1);
d = it-arg;
s = *sa;
@@ -1232,7 +1238,7 @@
dummy[0] = s[-1];
dummy[1] = '\0';
-return ap_pstrcat(p, Unrecognized JkRequestLogFormat directive %,
+return apr_pstrcat(p, Unrecognized JkRequestLogFormat directive %,
dummy, NULL);
}
it-func = l-func;
@@ -1243,18 +1249,18 @@
static apr_array_header_t *parse_request_log_string(apr_pool_t *p, const char *s,
const char **err)
{
-apr_array_header_t *a = ap_make_array(p, 15, sizeof(request_log_format_item));
+apr_array_header_t *a = apr_array_make(p, 15, sizeof(request_log_format_item));
char *res;
while (*s) {
-if ((res = parse_request_log_item(p, (request_log_format_item *)
ap_push_array(a), s))) {
+if ((res = parse_request_log_item(p, (request_log_format_item *)
apr_array_push(a), s))) {
*err = res;
return NULL;
}
}
s = \n;
-parse_request_log_item(p, (request_log_format_item *) ap_push_array(a), s);
+parse_request_log_item(p, (request_log_format_item *)
DO NOT REPLY [Bug 23316] - Oracle JDBCRealms failed after tns listener restart.
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=23316. 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=23316 Oracle JDBCRealms failed after tns listener restart. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23506] New: - After recompiling servlet source, 503 error occured
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=23506. 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=23506 After recompiling servlet source, 503 error occured Summary: After recompiling servlet source, 503 error occured Product: Tomcat 4 Version: 4.1.27 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I recompiled source, and server reloaded it, and I tried to access the servlet, but 503 error occurred..When I restart server then the page is fine.. Error message is type : Status report message : This application is not currently available description : The requested service (This application is not currently available) is not currently available. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23506] - After recompiling servlet source, 503 error occured
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=23506. 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=23506 After recompiling servlet source, 503 error occured [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-09-30 03:02 --- did you check your logs, the bug is invalid because you didn't supply any information. check your logs, maybe your redeployment failed, and also provide us with a test case - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk aphowto.xml
glenn 2003/09/29 20:09:06 Modified:jk/xdocs/jk aphowto.xml Log: Update download links to use jakarta mirror cgi Revision ChangesPath 1.24 +7 -23 jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml Index: aphowto.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- aphowto.xml 25 Sep 2003 13:06:30 - 1.23 +++ aphowto.xml 30 Sep 2003 03:09:06 - 1.24 @@ -145,6 +145,9 @@ p It is recommended to use the binary version if one is available. If the binary is not available, follow the instructions for building mod_jk from source. +The mod_jk source can be downloaded from a mirror +a href=http://jakarta.apache.org/site/sourceindex.cgi/; +here/a /p p @@ -162,29 +165,10 @@ /p p -For example JK 1.2.5 can be found a href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/; -here/a and contains the following: -/p - -p -table - trthLocation/ththContents/th/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/aix/;aix/a/tdtdSAVF including mod_jk for Apache 2.0 for iSeries V5R1/V5R2/td/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/iseries/;iseries/a/tdtdSAVF including mod_jk for Apache 2.0 for iSeries V5R1/V5R2/td/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/linux/;linux/a/tdtdmod_jk.so (Apache 1.3 standard API and EAPI and Apache 2.0) for some Linux Archs/td/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/macosx/;macosx/a/tdtdContains the mod_jk.so for MacOS X/td/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/netware/;netware/a/tdtdmod_jk.nlm and nsapi.nlm for Netware/td/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/rpms/;rpms/a/tdtdContains the rpms (including sources and i386/ppc architectures)/td/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/solaris6/;solaris6/a/tdtdContains the mod_jk.so for Solaris 6/td/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/solaris8/;solaris8/a/tdtdContains the mod_jk.so for Solaris 8/td/tr - trtda href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/win32/;win32/a/tdtdContains the mod_jk.dll for Windows as well as other useful binaries./td/tr -/table -/p - -p -If you don't see your Operating System here, the doc may be outdated so just go -a href=http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.5/bin/; -here/a and check if one of the directory didn't cover your os +For example JK 1.2.5 can be downloaded from a mirror +a href=http://jakarta.apache.org/site/binindex.cgi/; +here/a and contains binary version for a variety of +operating systems for both Apache 1.3 and Apache 2. /p /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23477] - the admin and manager webapps is not available when host appbase is out of catalina home.
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=23477. 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=23477 the admin and manager webapps is not available when host appbase is out of catalina home. [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-09-30 03:52 --- Thanks for your comments. But why the admin and manager docBase is not relative to the catalina home since they installed in catalina home? Perhaps it will more convenient for users! thanks a lot. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk HOWTO-RELEASE
glenn 2003/09/29 21:15:52
Modified:jk HOWTO-RELEASE
Log:
Update docs for packaging releases and mirror downloads
Revision ChangesPath
1.8 +28 -32jakarta-tomcat-connectors/jk/HOWTO-RELEASE
Index: HOWTO-RELEASE
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/HOWTO-RELEASE,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- HOWTO-RELEASE 25 Sep 2003 13:08:42 - 1.7
+++ HOWTO-RELEASE 30 Sep 2003 04:15:51 - 1.8
@@ -157,48 +157,43 @@
Upload source distribution and documentation to www.apache.org
---
-ssh to www.apache.org and create the release directory.
-
-mkdir /www/www.apache.org/dist/jakarta/tomcat-connectors/jk/v1.2.5
+First update the KEYS on the server if you have added a new pgp key.
scp jakarta-tomcat-connectors/KEYS to the
/www/www.apache.org/dist/jakarta/tomcat-connectors
-directory on thewww.apache.org server.
-
-Copy a previous release directory README.html file to the new release
-directory and edit as necessary.
-
-Make the following directories in the release directory.
-
-mkdir bin doc rpms src
-
-Make the following directories in the bin directory.
+directory on the www.apache.org server.
-mkdir aix freebsd iseries linus macosx netware solaris6 solaris7 solaris8 win32
-
-scp jakarta-tomcat-connectors/jk/build/docs to the release doc directory.
-
-scp ~/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz* to the release src
-directory.
-
-scp -r jakarta-tomcat-connectors/jk/build/docs/*
www.apache.org:/www/www.apache.org/dist/jakarta/tomcat-connectors/jk/v1.2.5/doc
+scp jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz* to
+/www/www.apache.org/dist/jakarta/tomcat-connectors/jk/source
+scp jakarta-tomcat-connectors-jk-1.2.5-src.zip* to
+/www/www.apache.org/dist/jakarta/tomcat-connectors/jk/source
+
+ssh to www.apache.org and cd to the
+/www/www.apache.org/dist/jakarta/tomcat-connectors/jk directory.
+
+Remove the symlinks for current and replace them with a soft link
+to the new source distribution files.
+
+ln -s source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jakarta-tomcat-connectors-jk-src-current.tar.gz
+ln -s source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jakarta-tomcat-connectors-jk-src-current.tar.gz.asc
+ln -s source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.zip
jakarta-tomcat-connectors-jk-src-current.zip
+ln -s source/jakarta-tomcat-connectors-jk-1.2.5-src.zip.asc
jakarta-tomcat-connectors-jk-src-current.zip.asc
Make sure the group write bit is set on all files and directories
-in the new release directory.
+in the jk directory.
-chmod -R g+w /www/www.apache.org/dist/jakarta/tomcat-connectors/jk/v1.2.5
+chmod -R g+w /www/www.apache.org/dist/jakarta/tomcat-connectors/jk/
Build binaries and upload distributions to www.apache.org
--
Build mod_jk for a specific web server and OS. Package it as appropriate for
-
the OS and sign the archive using PGP. Please include the ASF License, the
-generated docs, and the tools.
+generated docs, and the tools. Please name the distribuiton as follows:
+
+jakarta-tomcat-connectors-jk-{version}-{os-version-cpu}-{web
server-version}.(tar.gz|zip)
-scp the binary distribution and pgp signature file to the appropriate bin/{os}
directory.
-Create or modify that bin/{os} directory README.html file for the binary release.
-You can find previous README.html files as a template in earlier releases.
+scp the binary distribution and pgp signature file to the appropriate binaries/{os}
directory.
Make sure the group write bit is on for all files you upload.
@@ -208,12 +203,13 @@
Reset JK_VERISRELEASE to 0 and update JK_VERSTRING, JK_VERMAJOR,
JK_VERMINOR, and JK_VERFIX as needed. Commit your changes to CVS.
-Move old release distributions to archive.apache.org
+Remove old release distributions from www.apache.org
-Move any old mod_jk distribution directories to the
-/www/archive.apache.org/dist/jakarta/tomcat-connectors/jk/
-directory on the archive.apache.org server.
+Verify that the old versions of the source and binary distributions are
+available at /www/archive.apache.org/dist/jakarta/tomcat-connector/jk .
+Copy old source distributions and binaries as needed, then remove the
+old source and binary distributions.
Announcements
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java
billbarker2003/09/29 21:17:37
Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java
Log:
Remove nls from the status line.
Revision ChangesPath
1.46 +5 -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.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- JkCoyoteHandler.java 18 Sep 2003 16:21:02 - 1.45
+++ JkCoyoteHandler.java 30 Sep 2003 04:17:37 - 1.46
@@ -346,7 +346,11 @@
ep.setNote( tmpMessageBytesNote, mb );
}
String message=res.getMessage();
-if( message==null ) message= HttpMessages.getMessage(res.getStatus());
+if( message==null ){
+message= HttpMessages.getMessage(res.getStatus());
+} else {
+message = message.replace('\n', ' ').replace('\r', ' ');
+}
mb.setString( message );
c2b.convert( mb );
msg.appendBytes(mb);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java
billbarker2003/09/29 21:18:45
Modified:jk/java/org/apache/jk/server Tag: coyote_10
JkCoyoteHandler.java
Log:
port patch.
Revision ChangesPath
No revision
No revision
1.32.2.4 +5 -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.32.2.3
retrieving revision 1.32.2.4
diff -u -r1.32.2.3 -r1.32.2.4
--- JkCoyoteHandler.java 30 Jul 2003 02:27:01 - 1.32.2.3
+++ JkCoyoteHandler.java 30 Sep 2003 04:18:45 - 1.32.2.4
@@ -299,7 +299,11 @@
ep.setNote( tmpMessageBytesNote, mb );
}
String message=res.getMessage();
-if( message==null ) message= HttpMessages.getMessage(res.getStatus());
+if( message==null ){
+message= HttpMessages.getMessage(res.getStatus());
+} else {
+message = message.replace('\n', ' ').replace('\r', ' ');
+}
mb.setString( message );
c2b.convert( mb );
msg.appendBytes(mb);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk release packaging and connector download move to www.apache.org/dist mirror and archive.apache.org
I have completed most of the below.
The directory layout is setup in
/www/www.apache.org/dist/jakarta/tomcat-connectors and
/www/archive.apache.org/dist/jakarta/tomcat-connectors .
The old coyote beta and milestone releases have been removed.
The webapp releases have been moved to the archive.
The latest jk2 release is setup on the mirror and previous releases
are in the archive.
The mod_jk 1.2.5 source distribution has been released on the mirror,
previous versions have been copied to the archive.
The jakarta site binindex.cgi and sourceindex.cgi have been updated.
The jk docs in the Tomcat 4.1 directory have been updated with the
download links fixed.
For now I am leaving the current jk/jk2 releases in place on the jakarta
site. After a few days I will remove them and put the .htaccess file in place.
The mod_jk 1.2.5 release is now accepting binary releases. Please consider
the following when packaging your binary release distributions:
Build binaries and upload distributions to www.apache.org
--
Build mod_jk for a specific web server and OS. Package it as appropriate for
the OS and sign the archive using PGP. Please include the ASF License, the
generated docs, and the tools. Please name the distribuiton as follows:
jakarta-tomcat-connectors-jk-{version}-{os-version-cpu}-{web server-version}.(tar.gz|zip)
scp the binary distribution and pgp signature file to the appropriate binaries/{os} directory.
Make sure the group write bit is on for all files you upload.
I will send out the announcement in a few days once some binaries have accumulated
and the mirrors have had a chance to rsync them.
Thanks,
Glenn
Glenn Nielsen wrote:
As part of the mod_jk 1.2.5 release I promised to move the JTC download to
www.apache.org/dist so that the downloads can be mirrored. Here are the
changes I propose to make as I set this up.
First, here is the directory layout for mirrored downloads at
/www/www.apache.org/dist/jakarta/tomcat-connectors :
KEYS
jk
jk/README.html
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz.asc -
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk/binaries
jk/binaries/aix
jk/binaries/freebsd
jk/binaries/iseries
jk/binaries/linux
jk/binaries/macosx
jk/binaries/netware
jk/binaries/solaris
jk/binaries/win32
jk/source
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz
jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc
jk2
jk2/README.html
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz.asc -
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
jk2/binaries
jk2/binaries/aix
jk2/binaries/freebsd
jk2/binaries/iseries
jk2/binaries/linux
jk2/binaries/macosx
jk2/binaries/netware
jk2/binaries/solaris
jk2/binaries/win32
jk2/source
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz
jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
Each binary directory would contain a tar.gz, rpm, or zip for the binary
release
rather than .dll or .so files. The archive would be named:
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.tar.gz
(.zip for windows, .rpm for linux rpm's)
linux rpms would go in the binaries/linux directory.
Here is an example for mod_jk 1.2.5 for FreeBsd on i386 for apache 2:
jakarta-tomcat-connector-jk-1.2.5-freebsd4.8-i386-apache-2.0.47.tar.gz
This will allow us to put multiple binaries in the same directory for
different
jk release versions, OS versions, and web server versions and make managing
the mirrored download and archive.apache.org directories easier.
httpd includes the source with their binary distributions, I recommend
that we do
the same. The binary release should contain the contents of the source
release
plus the binary files.
Here is what I propose we do:
1. Coyote -
/www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/
This contains 9 coyote connector beta release and one release candidate.
Do we need to keep these? If not, since coyote comes with the Tomcat
releases,
why not completely remove coyote from the tomcat-connectors download?
+1 to remove coyote from the download completely since it is part of the
Tomcat release.
If we keep them, I will make the following changes.
Take each release directory and create both a tar.gz and .zip for the
release, sign each. i.e. The jar files in v1.0-b1 are put into
apache-tomcat-coyote-1.0-b1.tar.gz.
Place the tar.gz and zip files in the
/www/archive.apache.org/dist/jakarta/tomcat-connectors/coyote/binaries/
directory.
2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/
Remove the docs directory, point users to jakarta.apache.org/tomcat in
the README.html.
Remove the nightly directory, no nightlies have
cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler JasperMangler.java
billbarker2003/09/29 21:49:59
Modified:src/share/org/apache/jasper/compiler JasperMangler.java
Log:
Fix problem with empty JSP file.
Fix for bug #23478.
Reported By: Jens [EMAIL PROTECTED]
Revision ChangesPath
1.12 +1 -1
jakarta-tomcat/src/share/org/apache/jasper/compiler/JasperMangler.java
Index: JasperMangler.java
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/jasper/compiler/JasperMangler.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- JasperMangler.java22 Sep 2003 09:17:46 - 1.11
+++ JasperMangler.java30 Sep 2003 04:49:59 - 1.12
@@ -168,7 +168,7 @@
// Fix for invalid characters. From CommandLineCompiler
StringBuffer modifiedClassName = new StringBuffer();
char c='/';
- if( Character.isDigit( className.charAt( 0 ) )) {
+ if( className.length() 0 Character.isDigit( className.charAt( 0 ) )) {
className=_ +className;
}
for (int i = 0; i className.length(); i++) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23477] - the admin and manager webapps is not available when host appbase is out of catalina home.
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=23477. 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=23477 the admin and manager webapps is not available when host appbase is out of catalina home. [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-09-30 04:55 --- This is not a user question forum. All docBase are relative to appBase. You can complain about that (but it's been like that since TC 4.0), but it's not a bug, and since you'll have to argue about it, you should post to tomcat-dev. Please do not reopen the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23478] - StringIndexOutOfBoundsException with an empty jsp file name
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=23478. 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=23478 StringIndexOutOfBoundsException with an empty jsp file name [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-09-30 05:13 --- Fixed now in the CVS and should appear in the next nightly. You will now get a normal 404 response. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 InternalOutputBuffer.java
billbarker2003/09/29 22:38:15
Modified:http11/src/java/org/apache/coyote/http11 Tag: coyote_10
InternalOutputBuffer.java
Log:
Port the no-nl patch from the Head branch.
Revision ChangesPath
No revision
No revision
1.16.2.2 +4 -2
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java
Index: InternalOutputBuffer.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java,v
retrieving revision 1.16.2.1
retrieving revision 1.16.2.2
diff -u -r1.16.2.1 -r1.16.2.2
--- InternalOutputBuffer.java 12 Sep 2003 10:28:38 - 1.16.2.1
+++ InternalOutputBuffer.java 30 Sep 2003 05:38:15 - 1.16.2.2
@@ -425,10 +425,12 @@
write( );
// Write message
-if (response.getMessage() == null) {
+String message = response.getMessage();
+if (message == null) {
write(HttpMessages.getMessage(status));
} else {
-write(response.getMessage());
+ message = message.replace('\r', ' ').replace('\n', ' ');
+write(message);
}
// End the response status line
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 InternalOutputBuffer.java
billbarker2003/09/29 22:40:27
Modified:http11/src/java/org/apache/coyote/http11 Tag: coyote_10
InternalOutputBuffer.java
Log:
Trying to escape the dreaded tab-police.
Revision ChangesPath
No revision
No revision
1.16.2.3 +1 -1
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java
Index: InternalOutputBuffer.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java,v
retrieving revision 1.16.2.2
retrieving revision 1.16.2.3
diff -u -r1.16.2.2 -r1.16.2.3
--- InternalOutputBuffer.java 30 Sep 2003 05:38:15 - 1.16.2.2
+++ InternalOutputBuffer.java 30 Sep 2003 05:40:27 - 1.16.2.3
@@ -429,7 +429,7 @@
if (message == null) {
write(HttpMessages.getMessage(status));
} else {
- message = message.replace('\r', ' ').replace('\n', ' ');
+message = message.replace('\r', ' ').replace('\n', ' ');
write(message);
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
