date:20030126

[GUMP] Build Failure - jakarta-tomcat-catalina

2003-01-26 Thread bobh


This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-01-26/jakarta-tomcat-catalina.html


Buildfile: build.xml

deploy-prepare:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-catalina/build

deploy-static:

deploy-catalina:
 [echo] Target: Catalina - Deploy ...

flags:

BUILD FAILED
java.lang.ClassCastException
at java.util.jar.JarFile.getInputStream(JarFile.java:323)
at 
org.apache.tools.ant.loader.AntClassLoader2.addPathFile(AntClassLoader2.java:279)
at org.apache.tools.ant.AntClassLoader.addPathElement(AntClassLoader.java:481)
at org.apache.tools.ant.AntClassLoader.setClassPath(AntClassLoader.java:381)
at org.apache.tools.ant.Project.createClassLoader(Project.java:305)
at org.apache.tools.ant.taskdefs.Available.eval(Available.java:285)
at org.apache.tools.ant.taskdefs.Available.execute(Available.java:247)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:185)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1273)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:373)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:185)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1273)
at org.apache.tools.ant.Project.executeTargets(Project.java:1217)
at org.apache.tools.ant.Main.runBuild(Main.java:610)
at org.apache.tools.ant.Main.start(Main.java:198)
at org.apache.tools.ant.Main.main(Main.java:245)

Total time: 2 seconds
java.lang.ClassCastException
at java.util.jar.JarFile.getInputStream(JarFile.java:323)
at 
org.apache.tools.ant.loader.AntClassLoader2.addPathFile(AntClassLoader2.java:279)
at org.apache.tools.ant.AntClassLoader.addPathElement(AntClassLoader.java:481)
at org.apache.tools.ant.AntClassLoader.setClassPath(AntClassLoader.java:381)
at org.apache.tools.ant.Project.createClassLoader(Project.java:305)
at org.apache.tools.ant.taskdefs.Available.eval(Available.java:285)
at org.apache.tools.ant.taskdefs.Available.execute(Available.java:247)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:185)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1273)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:373)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:185)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1273)
at org.apache.tools.ant.Project.executeTargets(Project.java:1217)
at org.apache.tools.ant.Main.runBuild(Main.java:610)
at org.apache.tools.ant.Main.start(Main.java:198)
at org.apache.tools.ant.Main.main(Main.java:245)

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

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

2003-01-26 Thread Craig McClanahan


This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-01-26/jakarta-tomcat-jk-ant.html


Buildfile: build.xml does not exist!
Build failed

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

Re: cvs commit: jakarta-tomcat build.xml

2003-01-26 Thread Bill Barker

- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, January 25, 2003 7:05 PM
Subject: cvs commit: jakarta-tomcat build.xml

 larryi  2003/01/25 19:05:33

   Modified:.build.xml
   Log:
   Update commons-logging default version and add commons-modeler
   properties.  Pass commons-modeler to http11 build.

modeler-1.0 doesn't work with j-t-c HEAD (the main reason that I was pushing
for a branch), and the j-t-c coyote_10 branch doesn't require modeler at all
for Tomcat 3.3.  What is the reason for adding in modeler to TC 3.3?

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/threads ThreadPool.java ThreadPoolMX.java

2003-01-26 Thread Bill Barker

I'll take Sam's suggestions (probably tomorrow, since it is a bit late for
me to get it right now :).

It's a bit of a gray area.  Tomcat 3.3 should gump-build fine as is.  As
long as you are using the HEAD commons-modeler, then you have no problems
building the HEAD j-t-c.  The branch is for the 'standard-build' of TC 3.3
(which, until Larry's patch) had no dependencies on any version of
commons-modeler.

- Original Message -
From: Ignacio J. Ortega [EMAIL PROTECTED]
To: 'Tomcat Developers List' [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, January 25, 2003 8:35 AM
Subject: RE: cvs commit:
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/threads
ThreadPool.java ThreadPoolMX.java


 Bill, we will need another gump descriptor to build coyote_10 tag jtc
 sources obviously, to allow tc33 to be gumped correctly?

 Anyone with more knowledge of gump can help ?

  billbarker2003/01/24 20:49:24
 
Modified:util/java/org/apache/tomcat/util/threads Tag: coyote_10
  ThreadPool.java
Removed: util/java/org/apache/tomcat/util/threads Tag: coyote_10
  ThreadPoolMX.java

 (Care with double posting please)

 Saludos,
 Ignacio J. Ortega

 --
 To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
mailto:[EMAIL PROTECTED]



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

Re: [ANN] Security update: Apache Tomcat 3.3.1a released

2003-01-26 Thread Bill Barker

I'm assuming that this was actually voted on in some list (certainly not
this one).  I'd just like to add my -0 vote (only because a -1 is pointless
now :).  The 3.3 branch needs to have a 3.3.2 release, and IMHO, a 3.3.1a
release is just a waste of time.

- Original Message -
From: Larry Isaacs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Saturday, January 25, 2003 8:30 PM
Subject: [ANN] Security update: Apache Tomcat 3.3.1a released

Tomcat 3.3.1a has been released to address the following two
vulnerabilities found in Tomcat 3.3.1 and earlier.  This
includes Tomcat 3.2.4 and earlier.

Tomcat 4.0.4, 4.0.6, 4.1.12, 4.1.18, and 4.1.19 have been
checked and do not have these vulnerabilities.

Vulnerability where, when used with JDK 1.3.1 or earlier, a
maliciously crafted request could return a directory listing
even when an index.html, index.jsp, or other welcome file is
present. File contents can be returned as well.  In the case
of Tomcat 3.2.4 and earlier, contents of files under WEB-INF
could be accessed.  If you are using Tomcat 3.3.1 or earlier
with JDK 1.3.1 or earlier, you should either upgrade to JDK 1.4
or later, or upgrade your Tomcat installation to Tomcat 3.3.1a
or a current release of Tomcat 4.

Vulnerability where a malicious web application could read the
contents of some files outside the web application via its web.xml
file in spite of the presence of a security manager. The content
of files that can be read as part of an XML document would be
accessible. If you are running Tomcat 3.3.1 or earlier with a
security manager, and are serving web applications whose web.xml
content is not known to be safe, you should upgrade your Tomcat
installation to 3.3.1a or a current release of Tomcat 4.

You may download Tomcat 3.3.1a binaries and updated jars from:
http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1a/bin/

Other Tomcat downloads may be obtained from:
http://jakarta.apache.org/site/binindex.cgi

These vulnerabilities have been fixed in the current Tomcat 3.3.2-dev
files found at:
http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3.x/

Larry

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

RE: [ANN] Security update: Apache Tomcat 3.3.1a released

2003-01-26 Thread Larry Isaacs

This was the quickest way to deal with a security
vulnerability that was discussed on tomcat-committers.
At the time Tomcat 3.3.x wasn't building and the
last good build doesn't pass one of the internal
tests.  Also, I haven't had time to clean out
the old mod_jk content and to other clean up that
is needed to prepare a release.  A timely release
of Tomcat 3.3.2 wasn't practical given  haven't been
able to keep up with its current state as well as
I would like.

Given that I have some available time now, Tomcat 3.3.2
is next on the agenda.  I'll try to put together a
release plan this week.

The commons-modeler addition was to get the http11
building again.  Yes, a version newer than 1.0 is needed,
but I just needed some properties I could override for now.
I need to review all this and make sure I am building
3.3.2 with the proper sources from J-T-C.

The remote connection to my work computer is in pretty
bad shape at the moment, so I may not be able to respond
further today.  I'll try to address and questions or
concerns on Monday.

Cheers,
Larry

 

 -Original Message-
 From: Bill Barker [mailto:[EMAIL PROTECTED]] 
 Sent: Sunday, January 26, 2003 5:30 AM
 To: Tomcat Developers List
 Subject: Re: [ANN] Security update: Apache Tomcat 3.3.1a released
 
 
 I'm assuming that this was actually voted on in some list 
 (certainly not
 this one).  I'd just like to add my -0 vote (only because a 
 -1 is pointless
 now :).  The 3.3 branch needs to have a 3.3.2 release, and 
 IMHO, a 3.3.1a
 release is just a waste of time.
 
 - Original Message -
 From: Larry Isaacs [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
 [EMAIL PROTECTED]
 Sent: Saturday, January 25, 2003 8:30 PM
 Subject: [ANN] Security update: Apache Tomcat 3.3.1a released
 
 
 Tomcat 3.3.1a has been released to address the following two
 vulnerabilities found in Tomcat 3.3.1 and earlier.  This
 includes Tomcat 3.2.4 and earlier.
 
 Tomcat 4.0.4, 4.0.6, 4.1.12, 4.1.18, and 4.1.19 have been
 checked and do not have these vulnerabilities.
 
 Vulnerability where, when used with JDK 1.3.1 or earlier, a
 maliciously crafted request could return a directory listing
 even when an index.html, index.jsp, or other welcome file is
 present. File contents can be returned as well.  In the case
 of Tomcat 3.2.4 and earlier, contents of files under WEB-INF
 could be accessed.  If you are using Tomcat 3.3.1 or earlier
 with JDK 1.3.1 or earlier, you should either upgrade to JDK 1.4
 or later, or upgrade your Tomcat installation to Tomcat 3.3.1a
 or a current release of Tomcat 4.
 
 Vulnerability where a malicious web application could read the
 contents of some files outside the web application via its web.xml
 file in spite of the presence of a security manager. The content
 of files that can be read as part of an XML document would be
 accessible. If you are running Tomcat 3.3.1 or earlier with a
 security manager, and are serving web applications whose web.xml
 content is not known to be safe, you should upgrade your Tomcat
 installation to 3.3.1a or a current release of Tomcat 4.
 
 You may download Tomcat 3.3.1a binaries and updated jars from:
 http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1a/bin/
 
 Other Tomcat downloads may be obtained from:
 http://jakarta.apache.org/site/binindex.cgi
 
 These vulnerabilities have been fixed in the current Tomcat 3.3.2-dev
 files found at:
 http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3.x/
 
 Larry
 
 --
 To unsubscribe, e-mail:   
 mailto:tomcat-dev- [EMAIL PROTECTED]
 For 
 additional commands, 
 e-mail: mailto:[EMAIL PROTECTED]
 
 
 
 --
 To unsubscribe, e-mail:   
 mailto:tomcat-dev- [EMAIL PROTECTED]
 For 
 additional commands, 
 e-mail: mailto:[EMAIL PROTECTED]
 
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

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

2003-01-26 Thread glenn

glenn   2003/01/26 10:55:51

  Modified:jasper2/src/share/org/apache/jasper/compiler Tag:
tomcat_4_branch Compiler.java
  Log:
  Dereference those objects which are only used during the generation
  of the java class from the JSP source or used during the javac compile.
  This should reduce the memory footprint of Tomcat in production for
  those who use JSP and where JSP pages get compiled or recompiled on
  a production system. This should also improve performance by reducing
  the number of objects in the old generation, thus reducing GC overhead.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.18.2.10 +26 -6 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Compiler.java
  
  Index: Compiler.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Compiler.java,v
  retrieving revision 1.18.2.9
  retrieving revision 1.18.2.10
  diff -u -r1.18.2.9 -r1.18.2.10
  --- Compiler.java 31 Dec 2002 14:00:36 -  1.18.2.9
  +++ Compiler.java 26 Jan 2003 18:55:51 -  1.18.2.10
  @@ -140,13 +140,17 @@
   public Compiler(JspCompilationContext ctxt, JspServletWrapper jsw) {
   this.jsw = jsw;
   this.ctxt = ctxt;
  - this.errDispatcher = new ErrorDispatcher();
   this.options = ctxt.getOptions();
   }
   
   // Lazy eval - if we don't need to compile we probably don't need the project
   private Project getProject() {
  +
  +if (errDispatcher == null) {
  +this.errDispatcher = new ErrorDispatcher();
  +}
   if( project!=null ) return project;
  +
   // Initializing project
   project = new Project();
   // XXX We should use a specialized logger to redirect to jasperlog
  @@ -237,6 +241,10 @@
// generate servlet .java file
Generator.generate(writer, this, pageNodes);
   writer.close();
  +// The writer is only used during the compile, dereference
  +// it in the JspCompilationContext when done to allow it
  +// to be GC'd and save memory.
  +ctxt.setWriter(null);
   }
   
   /** 
  @@ -353,8 +361,20 @@
   public void compile()
   throws FileNotFoundException, JasperException, Exception
   {
  -generateJava();
  -generateClass();
  +try {
  +generateJava();
  +generateClass();
  +} finally {
  +// Make sure these object which are only used during the
  +// generation and compilation of the JSP page get
  +// dereferenced so that they can be GC'd and reduce the
  +// memory footprint.
  +errDispatcher = null;
  +logger = null;
  +project = null;
  +pageInfo = null;
  +pageNodes = null;
  +}
   }
   
   /**
  
  
  

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

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

2003-01-26 Thread glenn

glenn   2003/01/26 11:00:19

  Modified:.RELEASE-NOTES-4.1.txt
  Log:
  Update release notes
  
  Revision  ChangesPath
  1.52  +6 -1  jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt
  
  Index: RELEASE-NOTES-4.1.txt
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt,v
  retrieving revision 1.51
  retrieving revision 1.52
  diff -u -r1.51 -r1.52
  --- RELEASE-NOTES-4.1.txt 21 Jan 2003 23:19:56 -  1.51
  +++ RELEASE-NOTES-4.1.txt 26 Jan 2003 19:00:19 -  1.52
  @@ -1041,6 +1041,11 @@
PageContextImpl:
pushBody()/popBody() error on tomcat 4.1.X.
   
  +[4.1.20] #15845
  + Fixed JSP page compiles so that objects created for performing
  + the JSP page compiles which are not reused are dereferenced so
  + they are eligible for GC. This should reduce the memory footprint
  + and improve GC performance.
   
   
   KNOWN ISSUES IN THIS RELEASE:
  
  
  

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

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

2003-01-26 Thread glenn

glenn   2003/01/26 11:00:58

  Modified:jasper2/src/share/org/apache/jasper/compiler Compiler.java
  Log:
  Dereference those objects which are only used during the generation
  of the java class from the JSP source or used during the javac compile.
  This should reduce the memory footprint of Tomcat in production for
  those who use JSP and where JSP pages get compiled or recompiled on
  a production system. This should also improve performance by reducing
  the number of objects in the old generation, thus reducing GC overhead.
  
  Revision  ChangesPath
  1.47  +27 -6 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Compiler.java
  
  Index: Compiler.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Compiler.java,v
  retrieving revision 1.46
  retrieving revision 1.47
  diff -u -r1.46 -r1.47
  --- Compiler.java 22 Jan 2003 20:39:28 -  1.46
  +++ Compiler.java 26 Jan 2003 19:00:58 -  1.47
  @@ -137,13 +137,17 @@
   public Compiler(JspCompilationContext ctxt, JspServletWrapper jsw) {
   this.jsw = jsw;
   this.ctxt = ctxt;
  - this.errDispatcher = new ErrorDispatcher();
   this.options = ctxt.getOptions();
   }
   
   // Lazy eval - if we don't need to compile we probably don't need the project
   private Project getProject() {
  +
  +if (errDispatcher == null) {
  +this.errDispatcher = new ErrorDispatcher();
  +}
   if( project!=null ) return project;
  +
   // Initializing project
   project = new Project();
   logger = new JasperAntLogger();
  @@ -275,6 +279,10 @@
// generate servlet .java file
Generator.generate(writer, this, pageNodes);
   writer.close();
  +// The writer is only used during the compile, dereference
  +// it in the JspCompilationContext when done to allow it
  +// to be GC'd and save memory.
  +ctxt.setWriter(null);
   
   long t4=System.currentTimeMillis();
   if( t4-t1  500 ) {
  @@ -416,11 +424,24 @@
   public void compile()
   throws FileNotFoundException, JasperException, Exception
   {
  -generateJava();
  -generateClass();
  - if (tfp != null) {
  - tfp.removeProtoTypeFiles(null);
  - }
  +try {
  +generateJava();
  +generateClass();
  +} finally {
  +if (tfp != null) {
  +tfp.removeProtoTypeFiles(null);
  +}
  +// Make sure these object which are only used during the
  +// generation and compilation of the JSP page get
  +// dereferenced so that they can be GC'd and reduce the
  +// memory footprint.
  +tfp = null;
  +errDispatcher = null;
  +logger = null;
  +project = null;
  +pageInfo = null;
  +pageNodes = null;
  +}
   }
   
   /**
  
  
  

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 15845] - 4.1.19 Memory Leak when creating compilier for JSP pages

2003-01-26 Thread bugzilla

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=15845.
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=15845

4.1.19 Memory Leak when creating compilier for JSP pages

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-01-26 19:03 ---
Unneded objects created for JSP page compiles are now dereferenced so that
they are eligible for GC.  Patch applied to both Tomcat 4.1 Jasper 2 and
Tomcat 5.0 Jasper 2.

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 15845] - 4.1.19 Memory Leak when creating compilier for JSP pages

2003-01-26 Thread bugzilla

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=15845.
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=15845

4.1.19 Memory Leak when creating compilier for JSP pages

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

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

2003-01-26 Thread Aditya

Although bug 15845 is listed as being for 4.1.19, it looks like it
affected Jasper2 even before that -- or am I reading the commit
message wrong?

Thanks,
Adi

 On 26 Jan 2003 19:00:19 -, [EMAIL PROTECTED] said:
 glenn 2003/01/26 11:00:19

   Modified: .  RELEASE-NOTES-4.1.txt Log: Update release notes
  
   Revision Changes Path 1.52 +6 -1
 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt
  
   Index: RELEASE-NOTES-4.1.txt
 ===
 RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt,v
 retrieving revision 1.51 retrieving revision 1.52 diff -u -r1.51
 -r1.52 --- RELEASE-NOTES-4.1.txt 21 Jan 2003 23:19:56 - 1.51 +++
 RELEASE-NOTES-4.1.txt 26 Jan 2003 19:00:19 - 1.52 @@ -1041,6
 +1041,11 @@ PageContextImpl: pushBody()/popBody() error on tomcat
 4.1.X.
   
   +[4.1.20] #15845 + Fixed JSP page compiles so that objects created
 for performing + the JSP page compiles which are not reused are
 dereferenced so + they are eligible for GC. This should reduce the
 memory footprint + and improve GC performance.
   
 KNOWN ISSUES IN THIS RELEASE:

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace

2003-01-26 Thread bugzilla

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=9931.
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=9931

Base64 decoder chokes on a whitespace





--- Additional Comments From [EMAIL PROTECTED]  2003-01-26 21:10 ---
Created an attachment (id=4551)
Patch (includes Daniel's patch) providing base64 encoding

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace

2003-01-26 Thread bugzilla

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=9931.
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=9931

Base64 decoder chokes on a whitespace





--- Additional Comments From [EMAIL PROTECTED]  2003-01-26 21:12 ---
Created an attachment (id=4552)
Simple uncomments the encode test

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace: FIXED?

2003-01-26 Thread bugzilla

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=9931.
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=9931

Base64 decoder chokes on a whitespace: FIXED?

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Base64 decoder chokes on a  |Base64 decoder chokes on a
   |whitespace  |whitespace: FIXED?



--- Additional Comments From [EMAIL PROTECTED]  2003-01-26 21:15 ---
I've just submitted a couple of patches that should fix encoding. Daniel Rall's
last patch is subsumed in these: + i was missing of the location of the
insertion point for the separator, and this was messing things up.

This *should* fix the problem.

Looking at the code, it should be possible to do this more economically on the
fly. I'll give that a go when I get a chance.

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace: FASTER?

2003-01-26 Thread bugzilla

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=9931.
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=9931

Base64 decoder chokes on a whitespace: FASTER?





--- Additional Comments From [EMAIL PROTECTED]  2003-01-26 22:38 ---
Created an attachment (id=4553)
Patch for Base64.java for inserting separators on the fly during encode

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

TC5 - Dependent on JDK1.4?

2003-01-26 Thread Tim Funk

org.apache.catalina.loader.WebappClassLoader.java [line 1957] uses 
java.io.File.toURI() which is in java 1.4 and not in java 1.3.

http://java.sun.com/j2se/1.4/docs/api/java/io/File.html#toURI()

All the discussions I have seen so far with respect to tomcat 5 and jdk 
1.4 state that tomcat 5 would not be dependent on jdk 1.4.

Is everyone developing tomcat 5 with jdk1.4 or am I missing something? 
Or will the 1.4 dependencies be factored out at a later date when a 
release might look feasible?


-Tim



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace: FASTER?

2003-01-26 Thread bugzilla

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=9931.
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=9931

Base64 decoder chokes on a whitespace: FASTER?





--- Additional Comments From [EMAIL PROTECTED]  2003-01-27 00:33 ---
I thought we should notify upstream in Jakarta Commons Sandbox: Codec.  So I
posted a bug: Bug 16440.  Then I noticed that Daniel Rall is listed as a
committer on Codec.  Hi Dan!

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace: FASTER?

2003-01-26 Thread bugzilla

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=9931.
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=9931

Base64 decoder chokes on a whitespace: FASTER?





--- Additional Comments From [EMAIL PROTECTED]  2003-01-27 00:39 ---
I tested Martin's latest patch (Attachment 4553) and it passes the uncommented test.

Also Martin and I discussed possibly adding a performance test with a much
bigger piece of test data.  If we decide to do this, we need to decide what
constitutes bad performance.  One idea that would not depend on the power of
the machine on which the tests run is to time the encoding and decoding of a
small piece of data (~ 1K to 5K) and then time the encoding and decoding of a
larger piece (~100K to 500K) and make sure that the increase in running time is
acceptable.  Currently, I imagine an O(n) algorithm would be acceptable so we
could make the test guarantee a 100-110% increase in running time.  We could do
something similar for memory usage.

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

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

2003-01-26 Thread Glenn Nielsen

You read it correctly. AFAIK, all previous versions of jasper
held on to objects which it no longer needed after a JSP compile.

Glenn

Aditya wrote:

Although bug 15845 is listed as being for 4.1.19, it looks like it
affected Jasper2 even before that -- or am I reading the commit
message wrong?

Thanks,
Adi



On 26 Jan 2003 19:00:19 -, [EMAIL PROTECTED] said:
glenn 2003/01/26 11:00:19




 Modified: .  RELEASE-NOTES-4.1.txt Log: Update release notes


  

 Revision Changes Path 1.52 +6 -1
jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt


  

 Index: RELEASE-NOTES-4.1.txt
===
RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt,v
retrieving revision 1.51 retrieving revision 1.52 diff -u -r1.51
-r1.52 --- RELEASE-NOTES-4.1.txt 21 Jan 2003 23:19:56 - 1.51 +++
RELEASE-NOTES-4.1.txt 26 Jan 2003 19:00:19 - 1.52 @@ -1041,6
+1041,11 @@ PageContextImpl: pushBody()/popBody() error on tomcat
4.1.X.


   

 +[4.1.20] #15845 + Fixed JSP page compiles so that objects created
for performing + the JSP page compiles which are not reused are
dereferenced so + they are eligible for GC. This should reduce the
memory footprint + and improve GC performance.


   

   KNOWN ISSUES IN THIS RELEASE:



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]





--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

using ajp (isapi_redirector2.dll) without tomcat

2003-01-26 Thread James Chang

Hi:

I am trying to get ajp to work with other jsp/servlet engines other then
tomcat.   Right now I am working on IIS with isapi_redirector2.dll and
listening on port 8009 with my own ajp listener.  The problem is somehow the 
dll never calls to port 8009 when I am accessing http://localhost/examples/*


I downloaded isapi_redirector2.dll from:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.2/bin/win32/

I have set up the registry settings and use the simple works2.properties file
as shown below.  IIS shows the dll is loaded correctly, but when I try to request to
http://localhost/examples/x , the isapi_redirector2.dll doesn't send any
request to port 8009.

Could anyone tell me what is wrong with my configuration file?  Or is
the dll somehow need tomcat to work (I have set it to use socket, but maybe
the dll needs some configuration file or shared library from tomcat)??

Any pointer will be usefull.
Thanks!


the registry I used is:
REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi
Redirector\2.0]
serverRoot=d:\\tm
extensionUri=/jakarta/isapi_redirector2.dll
workersFile=D:\\shared\\iisredir\\workers2.properties
authComplete=0
threadPool=5

All strings are properly installed.


My workers2.properties file contains:

# Define the communication channel
[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
tomcatId=localhost:8009

# Map the Tomcat examples webapp to the Web server uri space
[uri:/examples/*]
info=Map the whole webapp

DO NOT REPLY [Bug 16445] New: - JspC does not work without -dd option

2003-01-26 Thread bugzilla

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=16445.
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=16445

JspC does not work without -dd option

   Summary: JspC does not work without -dd option
   Product: Tomcat 4
   Version: 4.1.12
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Blocker
  Priority: Other
 Component: Jasper 2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Hi,

The jspc.bat/sh does not work when it is NOT used with -dd option. It expects 
the output directory as though it is a mandatory argument. This issue is 
reproduciable in Tomcat 4.1.18 also. The following message is displaying in 
the console:

C:\DRIVE_E\advent1\jakarta\tomcat4.x\jakarta-tomcat-4.1.12-LE-jdk14
\binjspc.bat  ..\webapps\app2\jsp\hello.jsp
error:2003-01-27 12:08:43 - ERROR-the file '\jsp\hello.jsp' generated the 
following general exception: java.lang.NullPointerxception
null

thanks,
saravanan

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

[GUMP] Build Failure - jakarta-tomcat-catalina

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

Re: cvs commit: jakarta-tomcat build.xml

Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/threads ThreadPool.java ThreadPoolMX.java

Re: [ANN] Security update: Apache Tomcat 3.3.1a released

RE: [ANN] Security update: Apache Tomcat 3.3.1a released

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

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

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

DO NOT REPLY [Bug 15845] - 4.1.19 Memory Leak when creating compilier for JSP pages

DO NOT REPLY [Bug 15845] - 4.1.19 Memory Leak when creating compilier for JSP pages

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

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace: FIXED?

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace: FASTER?

TC5 - Dependent on JDK1.4?

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace: FASTER?

DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace: FASTER?

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

using ajp (isapi_redirector2.dll) without tomcat

DO NOT REPLY [Bug 16445] New: - JspC does not work without -dd option

22 matches

Site Navigation

Mail list logo

Footer information