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

2003-07-05 Thread billbarker
billbarker2003/07/05 23:37:16

  Modified:.RELEASE-NOTES-4.1.txt
  Log:
  Document fix for bug #21219.
  
  Revision  ChangesPath
  1.74  +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.73
  retrieving revision 1.74
  diff -u -r1.73 -r1.74
  --- RELEASE-NOTES-4.1.txt 1 Jul 2003 05:42:00 -   1.73
  +++ RELEASE-NOTES-4.1.txt 6 Jul 2003 06:37:16 -   1.74
  @@ -926,6 +926,11 @@
   [4.1.25] PureTLS SSL:
Fix problems with getting the CLIENT-CERT.
   
  +[4.1.25] #21219
  + Http11Processor:
  + Drop the client connection (nicely, if possible, rudely if not) in the
  + event of a serious protocol error.
  + 
   
   Jasper Bug Fixes:
   
  
  
  

-
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 Http11Processor.java

2003-07-05 Thread billbarker
billbarker2003/07/05 23:23:40

  Modified:http11/src/java/org/apache/coyote/http11 Tag: coyote_10
Http11Processor.java
  Log:
  Port Patch for closing connections on bad requests.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.55.2.2  +26 -0 
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java
  
  Index: Http11Processor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java,v
  retrieving revision 1.55.2.1
  retrieving revision 1.55.2.2
  diff -u -r1.55.2.1 -r1.55.2.2
  --- Http11Processor.java  13 May 2003 22:47:00 -  1.55.2.1
  +++ Http11Processor.java  6 Jul 2003 06:23:40 -   1.55.2.2
  @@ -599,6 +599,15 @@
   if (!error) {
   try {
   adapter.service(request, response);
  +// Handle when the response was committed before a serious
  +// error occurred.  Throwing a ServletException should both
  +// set the status to 500 and set the errorException.
  +// If we fail here, then the response is likely already 
  +// committed, so we can't try and set headers.
  +if(keepAlive && !error) { // Avoid checking twice.
  +error = response.getErrorException() != null ||
  +statusDropsConnection(response.getStatus());
  +}
   } catch (InterruptedIOException e) {
   error = true;
   } catch (Throwable t) {
  @@ -1204,6 +1213,9 @@
   keepAlive = false;
   }
   
  +// If we know that the request is bad this early, add the
  +// Connection: close header.
  +keepAlive = keepAlive && statusDropsConnection(statusCode);
   if (!keepAlive) {
   response.addHeader("Connection", "close");
   } else if (!http11) {
  @@ -1302,5 +1314,19 @@
   
   }
   
  +/**
  + * Determine if we must drop the connection because of the HTTP status
  + * code.  Use the same list of codes as Apache/httpd.
  + */
  +protected boolean statusDropsConnection(int status) {
  +return status == 400 /* SC_BAD_REQUEST */ ||
  +   status == 408 /* SC_REQUEST_TIMEOUT */ ||
  +   status == 411 /* SC_LENGTH_REQUIRED */ ||
  +   status == 413 /* SC_REQUEST_ENTITY_TOO_LARGE */ ||
  +   status == 414 /* SC_REQUEST_URI_TOO_LARGE */ ||
  +   status == 500 /* SC_INTERNAL_SERVER_ERROR */ ||
  +   status == 503 /* SC_SERVICE_UNAVAILABLE */ ||
  +   status == 501 /* SC_NOT_IMPLEMENTED */;
  +}
   
   }
  
  
  

-
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 Http11Processor.java

2003-07-05 Thread billbarker
billbarker2003/07/05 23:16:00

  Modified:http11/src/java/org/apache/coyote/http11
Http11Processor.java
  Log:
  Re-activate dropping the connection on serious protocol errors.
  
  Also adding Remy's suggestion to check the exception, as well as checking the status 
code in the commit so that we can be nice enough to tell the client that we're not 
talking to them anymore if we discover the error soon enough.
  
  Revision  ChangesPath
  1.70  +13 -3 
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java
  
  Index: Http11Processor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java,v
  retrieving revision 1.69
  retrieving revision 1.70
  diff -u -r1.69 -r1.70
  --- Http11Processor.java  5 Jul 2003 01:39:42 -   1.69
  +++ Http11Processor.java  6 Jul 2003 06:16:00 -   1.70
  @@ -635,9 +635,16 @@
   thrA.setCurrentStage(threadPool, "service");
   rp.setStage(org.apache.coyote.Constants.STAGE_SERVICE);
   adapter.service(request, response);
  -  /* Mimic httpd (currently disabled)
  -error = statusDropsConnection(response.getStatus());
  -  */
  +// Handle when the response was committed before a serious
  +// error occurred.  Throwing a ServletException should both
  +// set the status to 500 and set the errorException.
  +// If we fail here, then the response is likely already 
  +// committed, so we can't try and set headers.
  +if(keepAlive && !error) { // Avoid checking twice.
  +error = response.getErrorException() != null ||
  +statusDropsConnection(response.getStatus());
  +}
  +
   } catch (InterruptedIOException e) {
   error = true;
   } catch (Throwable t) {
  @@ -1260,6 +1267,9 @@
   keepAlive = false;
   }
   
  +// If we know that the request is bad this early, add the
  +// Connection: close header.
  +keepAlive = keepAlive && statusDropsConnection(statusCode);
   if (!keepAlive) {
   response.addHeader("Connection", "close");
   } else if (!http11) {
  
  
  

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



Re: Duplicate sessions

2003-07-05 Thread r Reynolds
Hi, 

There is an ugly but very safe code for getting rid of
duplicates. That will be in 4.1.x, at least for now. 

Tomcat 4.1.24 Stable is the latest release.

Warm Regards,
Rahul Garg


--- srujana <[EMAIL PROTECTED]> wrote:
> Hi
> 
>   We are facing problems with duplicate session ids
> with Tomcat 4.x.
> 
>   Is there any patch available, or else is that
> managed in later versions?
> 
>   Pl suggest h'w to avoid duplicate sessions
> 
> Thanks & Regards
> Srujana
>   
> 
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



Duplicate sessions

2003-07-05 Thread srujana
Hi

We are facing problems with duplicate session ids with Tomcat 4.x.

Is there any patch available, or else is that managed in later versions?

Pl suggest h'w to avoid duplicate sessions

Thanks & Regards
Srujana



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



FW: Reg Tomcat 4.1.18 Tags

2003-07-05 Thread srujana


-Original Message-
From: srujana [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 05, 2003 5:06 PM
To: [EMAIL PROTECTED]
Subject: Reg Tomcat 4.1.18 Tags


Hi

Am getting problem with Tags/taglibs in Tomcat 4.1.x release.

I'm using a bean



and one tag(user defined)

<%@ taglib uri="http://prsnltags/tags";  prefix="tags" %>

where "http://prsnltags/tags"; is the uri specified in the tld file for the
classes/tagsspecified inthe tld file.

The problem am facing is i'm calling the bean 'PBN' from the tag class
'doStartTag'method. But this method is getting fired before using the tag
, but instead its being called at the time of declaration means at this
point

<%@ taglib uri="http://prsnltags/tags";  prefix="tags" %>

Which is supposed to be called at the point where this tag is used
say like




We didn't face this problem with Tomcat 4.0.4/3.x version

Read from the net that Tomcat 5.0 addresses/handles Taglibs more smoothly

Pl give your suggestion

Thanks & Regards
Srujana





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



[GUMP] Build timed out - jk

2003-07-05 Thread Craig McClanahan

This email is autogenerated from the output from:



Buildfile: build.xml

init:
 [echo] /home/rubys
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk
 [echo] linux=true solaris=${solaris} win32=${win32} hpux=${hpux} 
netware=${netware}

apache20:

apache13:

iis:

netscape:

jni:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk/jni
   [so] Compiling 4 out of 4
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native/common/jk_map.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native/common/jk_pool.c
/home/rubys/bin/timeout: timed out

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



[GUMP] Build Failure - jakarta-tomcat-5

2003-07-05 Thread bobh

This email is autogenerated from the output from:



Buildfile: build.xml

prepare-release:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-5/release
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-5/release/v5.0
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-5/release/v5.0/bin
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-5/release/v5.0/src

init:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-5/build
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-5/build/classes
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-5/build/server/lib
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-5/build/common/lib

deploy-static:
 [copy] Copying 1 file to /home/rubys/jakarta/jakarta-tomcat-5/build/common/lib
 [copy] Copying 1 file to /home/rubys/jakarta/jakarta-tomcat-5/build/common/lib
 [copy] Copying 1 file to /home/rubys/jakarta/jakarta-tomcat-5/build/common/lib
 [copy] Copying 1 file to /home/rubys/jakarta/jakarta-tomcat-5/build/common/lib
 [copy] Copying 1 file to /home/rubys/jakarta/jakarta-tomcat-5/build/common/lib
 [copy] Copying 1 file to /home/rubys/jakarta/jakarta-tomcat-5/build/common/lib
 [copy] Copying 1 file to /home/rubys/jakarta/jakarta-tomcat-5/build/server/lib
 [copy] Copying 1 file to /home/rubys/jakarta/jakarta-tomcat-5/build/server/lib

BUILD FAILED
/home/rubys/jakarta/jakarta-tomcat-5/build.xml:156: Warning: Could not find file 
/usr/local/commons-daemon/bin/jsvc.tar.gz to copy.

Total time: 4 seconds

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



DO NOT REPLY [Bug 20483] - Visualization of Query using JSTL

2003-07-05 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=20483

Visualization of Query using JSTL

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-07-05 10:00 ---
Marking as invalid unless original reporter can give more needed information.

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