Re: Rejecting connections: empty http header if maxProcessors reached

2003-12-27 Thread Remy Maucherat
Bernd Bartke wrote:
I sent posted this message into the tomcat-user list two days ago, but 
got no respond so far - so maybe it's a question to the developers :-)

Hi,

what is the desired behaviour if tomcat 4.1.29 rejects incoming requests 
because of maxProcessors reached?
Should tomcat return an empty http header?
Tomcat will just reject the TCP connection (actually, it's the OS TCP 
stack which will).

Rémy

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


DO NOT REPLY [Bug 10040] - SingleSignOn valve unbounded memory use

2003-12-27 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=10040.
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=10040

SingleSignOn valve unbounded memory use

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-12-27 16:21 ---
The patch provided in bug 23881 has been applied to TC4 and TC5 and will be 
included in the next release.

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



DO NOT REPLY [Bug 9077] - SingleSignOn and session invalidate

2003-12-27 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=9077.
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=9077

SingleSignOn and session invalidate

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-12-27 16:44 ---
Brian ported his TC5 patch to TC4 (see bug 23881) which has now been applied 
and addresses the issues in this bug report.

The fixes will be included in the next releases of TC4/TC5.

Thanks to both Brian and Luke.

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



DO NOT REPLY [Bug 25774] New: - Documentation change needed for making unix daemon

2003-12-27 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=25774.
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=25774

Documentation change needed for making unix daemon

   Summary: Documentation change needed for making unix daemon
   Product: Tomcat 5
   Version: Unknown
  Platform: PC
   URL: http://jakarta.apache.org/tomcat/tomcat-5.0-
doc/setup.html
OS/Version: FreeBSD
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Unknown
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The documentation tells users to run make for bulding the unix daemon, connectors, and 
other C/
C++ code throughout the tomcat project.

It would be helpful to point out that they must run the gnu make (gmake) command to 
get the 
compile to work instead of the native bsd make on freebsd systems.

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



cvs commit: jakarta-tomcat-5 tomcat.nsi

2003-12-27 Thread remm
remm2003/12/27 09:32:23

  Modified:.tomcat.nsi
  Log:
  - Add some metadata to the .exe.
  
  Revision  ChangesPath
  1.40  +14 -3 jakarta-tomcat-5/tomcat.nsi
  
  Index: tomcat.nsi
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/tomcat.nsi,v
  retrieving revision 1.39
  retrieving revision 1.40
  diff -u -r1.39 -r1.40
  --- tomcat.nsi26 Dec 2003 17:31:54 -  1.39
  +++ tomcat.nsi27 Dec 2003 17:32:23 -  1.40
  @@ -8,9 +8,20 @@
 SetCompressor lzma
 SetDatablockOptimize on
   
  -!include MUI.nsh
  +  Name Apache Tomcat
  +
  +  ;Product information
  +  VIAddVersionKey ProductName Apache Tomcat
  +  VIAddVersionKey CompanyName Apache Software Foundation
  +  VIAddVersionKey LegalCopyright Copyright (c) 1999-2004 The Apache Software 
Foundation
  +  VIAddVersionKey FileDescription Apache Tomcat Installer
  +  VIAddVersionKey FileVersion 2.0
  +  VIAddVersionKey ProductVersion @VERSION@
  +  VIAddVersionKey Comments jakarta.apache.org/tomcat
  +  VIAddVersionKey InternalName [EMAIL PROTECTED]@.exe
  +  VIProductVersion @[EMAIL PROTECTED]
   
  -Name Apache Tomcat
  +!include MUI.nsh
   
   ;
   ;Configuration
  
  
  

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



[PATCH - Proposed] Bug 10526

2003-12-27 Thread Mark Thomas
All,

Looking at bug 10526 (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10526) 
the patch below is proposed as the fix. Is there any reason not to apply it? I 
had a look at the spec for both sessions and authentication and couldn't see 
anything that would prevent it.

Thanks in advance for any advice,

Mark

Index: 
catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java
===
RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/aut  
henticator/AuthenticatorBase.java,v
retrieving revision 1.15
diff -u -r1.15 AuthenticatorBase.java
--- 
catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java 11 
Dec 2003 05:50:39 - 1.15
+++ 
catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java 27 
Dec 2003 19:09:42 -
@@ -864,7 +864,7 @@
 request.setAuthType(authType);
 request.setUserPrincipal(principal);

-Session session = getSession(request, false);
+Session session = getSession(request, true);
 // Cache the authentication information in our session, if any
 if (cache) {
 if (session != null) {


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



DO NOT REPLY [Bug 10330] - Unable to compile JSPs in XML syntax on Linux 7.2

2003-12-27 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=10330.
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=10330

Unable to compile JSPs in XML syntax on Linux 7.2

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-12-27 19:54 ---
Not sure if this is a bug or not but I am closing this as WONTFIX as:
- Remy couldn't reproduce it
- RPMs are now maintained by JPackage (www.jpackage.org)

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



cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core StandardContext.java

2003-12-27 Thread markt
markt   2003/12/27 12:37:58

  Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
  Log:
  - Fix bug 10656. If session-timeout is zero or less, session should not timeout.
  - Ported from TC5 patch by luehe.
  
  Revision  ChangesPath
  1.122 +10 -5 
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java
  
  Index: StandardContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
  retrieving revision 1.121
  retrieving revision 1.122
  diff -u -r1.121 -r1.122
  --- StandardContext.java  21 Oct 2003 00:22:57 -  1.121
  +++ StandardContext.java  27 Dec 2003 20:37:58 -  1.122
  @@ -1085,7 +1085,12 @@
   public void setSessionTimeout(int timeout) {
   
   int oldSessionTimeout = this.sessionTimeout;
  -this.sessionTimeout = timeout;
  +/*
  + * SRV.13.3 (Deployment Descriptor):
  + * If the timeout is 0 or less, the container ensures the default
  + * behaviour of sessions is never to time out.
  + */
  +this.sessionTimeout = (timeout == 0) ? -1 : timeout;
   support.firePropertyChange(sessionTimeout,
  new Integer(oldSessionTimeout),
  new Integer(this.sessionTimeout));
  
  
  

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



DO NOT REPLY [Bug 10656] - Session Timeout incorrect for 0 in web.xml

2003-12-27 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=10656.
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=10656

Session Timeout incorrect for 0 in web.xml

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-12-27 20:40 ---
This has been fixed (in o.a.c.core.StandardContext) by porting the fix from 
TC5.

The fix will be included in the next TC4 release.

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



Re: [PATCH - Proposed] Bug 10526

2003-12-27 Thread Remy Maucherat
Mark Thomas wrote:
All,

Looking at bug 10526 (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10526) 
the patch below is proposed as the fix. Is there any reason not to apply it? I 
had a look at the spec for both sessions and authentication and couldn't see 
anything that would prevent it.
This could have some benefits in some situations, but I don't like the 
fact that there will be one session per authenticated user, regardless 
of what the application does.

Rémy



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


DO NOT REPLY [Bug 10909] - Problem calling anonymous classes in servlet destroy() method

2003-12-27 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=10909.
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=10909

Problem calling anonymous classes in servlet destroy() method

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-12-27 20:53 ---
Since Alex added a comment that this has been fixed in Tomcat 4.1.x (version 
not specified) I am closing this bug as fixed.

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



DO NOT REPLY [Bug 10972] - Realm without className in server.xml produces NullPointerException

2003-12-27 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=10972.
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=10972

Realm without className in server.xml produces NullPointerException

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Minor   |Enhancement



--- Additional Comments From [EMAIL PROTECTED]  2003-12-27 21:03 ---
Agreed, a more meaningful error message would be nice. However, this is an 
enhancement request.

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



Re: [PATCH - Proposed] Bug 10526

2003-12-27 Thread Bill Barker

- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Saturday, December 27, 2003 12:45 PM
Subject: Re: [PATCH - Proposed] Bug 10526


 Mark Thomas wrote:
  All,
 
  Looking at bug 10526
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10526)
  the patch below is proposed as the fix. Is there any reason not to apply
it? I
  had a look at the spec for both sessions and authentication and couldn't
see
  anything that would prevent it.

 This could have some benefits in some situations, but I don't like the
 fact that there will be one session per authenticated user, regardless
 of what the application does.


I agree with Remy on this.  However, if it was made to be a configurable
option, I'd move from -0 to +0.

 Rémy



 -
 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]