Re: New repository org

[Bill Barker]

A big -1 to the reorg, since then it won't be possible to checkout Trunk 
without also checking out all of the branches as well.


- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, October 06, 2005 3:55 AM
Subject: New repository org


Hi,

Since the previous naming scheme has jakarta everywhere, I propose we
change it to (I'll do the updating of the build scripts):

http://svn.apache.org/repos/asf/tomcat/build/tc5.5.x - build
http://svn.apache.org/repos/asf/tomcat/connectors/trunk - connectors
http://svn.apache.org/repos/asf/tomcat/container/tc5.5.x - container
http://svn.apache.org/repos/asf/tomcat/jasper/trunk - jasper
http://svn.apache.org/repos/asf/tomcat/servletapi/servlet2.4-jsp2.0-tc5.x
- servletapi

If I misunderstood about how Subversion should be used and this is not a
good way to organize things, let me know ;)

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]

Re: New repository org

[Bill Barker]

- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, October 06, 2005 7:46 AM
Subject: Re: New repository org



Bill Barker wrote:
A big -1 to the reorg, since then it won't be possible to checkout Trunk 
without also checking out all of the branches as well.


I don't understand your answer.


If you move the contents of e.g. tomcat/connectors/trunk - 
tomcat/connectors, then doing:

 svn co http://s.a.o/repos/asf/tomcat/connectors
will also grab tomcat/connectors/branches.



Rémy





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: New repository org

[Bill Barker]

- Original Message -
From: Bill Barker [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, October 06, 2005 9:11 AM
Subject: Re: New repository org



- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, October 06, 2005 7:46 AM
Subject: Re: New repository org


Bill Barker wrote:
 A big -1 to the reorg, since then it won't be possible to checkout Trunk
 without also checking out all of the branches as well.

I don't understand your answer.

If you move the contents of e.g. tomcat/connectors/trunk -
tomcat/connectors, then doing:
  svn co http://s.a.o/repos/asf/tomcat/connectors
will also grab tomcat/connectors/branches.


It occurs to me that I may have misunderstood, and you were just talking
about setting up the svn:externals for tomcat/current.  If that's the case,
then +0 (I don't really care, but I'm glad that somebody does :).


Rémy



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: New repository org

[Bill Barker]

- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, October 06, 2005 2:04 PM
Subject: Re: New repository org


Bill Barker wrote:
 It occurs to me that I may have misunderstood, and you were just talking
 about setting up the svn:externals for tomcat/current.  If that's the
case,
 then +0 (I don't really care, but I'm glad that somebody does :).

svn:externals sounds like a cool feature, I guess I'll have to look it
up to know what it does.


You can also look at how Struts is organized.  There, if you do:
  svn co http://svn.apache.org/repos/asf/struts/current  struts

You get all of the little bits and pieces all checked out to one place.

Mark Thomas wrote:
  If by this you mean do a checkout of
  http://svn.apache.org/repos/asf/tomcat/build/tc5.5.x to a directory
  called build in the build scripts then +1. If it involves any form of
  svn move -1 since I don't understand what you are planning to move to
  where and I have concerns about complications that might be created for
  checkouts, future branches and future tags.

No, I don't want to do any change to the repository. The problem is that
svn isn't like CVS, so someone (like me, I tried it) which would
checkout http://svn.apache.org/repos/asf/tomcat would be in trouble. It
would be better to organize the developer environment. Right now, it
organizes things using jakarta-tomcat-5, and all the other jakarta folders.

CVS was simpler ...

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]

Re: bug 36867

[Bill Barker]

It's not clear from the report (at least to someone with my lack of Jasper 
experiance :) that the report isn't  against a problem with a JSP-Document 
(aka XML-format).  Unlikely, but it needs to be checked before setting as 
INVALID.


- Original Message - 
From: Leon Rosenberg [EMAIL PROTECTED]

To: tomcat-dev@jakarta.apache.org
Sent: Friday, September 30, 2005 8:04 AM
Subject: bug 36867


just wondering why noone has set bug 36867 to invalid yet, since the
poster obviously doesn't know the difference between jsp and html
comments.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36867

-
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: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup Catalina.java CatalinaProperties.java ContextConfig.java Embedded.java

[Bill Barker]

- Original Message - 
From: [EMAIL PROTECTED]

To: [EMAIL PROTECTED]
Sent: Wednesday, September 28, 2005 10:52 PM
Subject: cvs commit: 
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup 
Catalina.java CatalinaProperties.java ContextConfig.java Embedded.java




costin  2005/09/28 22:52:49

snip/

 + // That's fine - we have reasonable defaults.
 + properties=new Properties();
  }

  // Register the properties as system properties
 -Enumeration enumeration = properties.propertyNames();
 + Enumeration enumeration = properties.propertyNames();
  while (enumeration.hasMoreElements()) {
  String name = (String) enumeration.nextElement();
  String value = properties.getProperty(name);


The dreaded Tab-Police are actually pretty strict in the 5.5.x branch :-).



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: svn commit: r291334 - /tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt

[Bill Barker]

- Original Message - 
From: [EMAIL PROTECTED]

To: tomcat-dev@jakarta.apache.org
Sent: Saturday, September 24, 2005 1:42 PM
Subject: svn commit: r291334 - 
/tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt





+[4.1.32] Commons Daemon
+ Upgrade to 1.0
+


I hope you plan to upgrade to 1.0.1, since 1.0 is buggy ;-).



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]

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 11 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 32 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c -o 
jk_ajp12_worker.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_connect.c -o jk_connect.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_msg_buff.c -o jk_msg_buff.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_util.c -o jk_util.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13.c -o jk_ajp13.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_pool.c -o jk_pool.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_worker.c -o jk_worker.lo

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 11 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 32 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c -o 
jk_ajp12_worker.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_connect.c -o jk_connect.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_msg_buff.c -o jk_msg_buff.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_util.c -o jk_util.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13.c -o jk_ajp13.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_pool.c -o jk_pool.lo
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_worker.c -o jk_worker.lo

Re: [EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

- Original Message - 
From: William A. Rowe, Jr. [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Friday, September 16, 2005 8:26 AM
Subject: Re: [EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module 
jakarta-tomcat-connectors) failed




Question - is gump building against apache 2 trunk or against the
httpd/branches/2.0.x (or some other particular httpd snapshot/rev)?



It's building against the apache2 trunk.  That's the only branch that Graham 
has setup to build in Gump.



The failure below...


Making all in apache-2.0
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/apache-2.0'
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
 --mode=compile 
gcc -I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include 
 -g -O2 -DUSE_APACHE_MD5 -I ../common  -I /opt/jdk1.4/include -I 
/opt/jdk1.4/include/unix -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
 -g -O2 -pthread -DHAVE_APR  -I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
 -I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1  
-g -O2 -g -O2 -pthread -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
 -c mod_jk.c -o mod_jk.lo

mod_jk.c:85:28: #if with no expression


didn't jive with my expectations below, unless AP_NEED_SET_MUTEX_PERMS
was actually defined, and it shouldn't be defined on 2.0.x.  I'm going
to propose the patch today to define AP_NEED_SET_MUTEX_PERMS to 1, and
then move forward to define it 0 everywhere else on httpd 2.1.x and 
beyond.  I'll propose today so if we are fetching up 2.1+ to build

against, this problem should be resolved.  The code (the final #if was
the one which had 'no expression').

/* Yes; sorta sucks - with luck we will clean this up before httpd-2.2
 * ships, leaving AP_NEED_SET_MUTEX_PERMS def'd as 1 or 0 on all 
platforms.

 */
#ifdef AP_NEED_SET_MUTEX_PERMS
# define JK_NEED_SET_MUTEX_PERMS AP_NEED_SET_MUTEX_PERMS
#else
  /* A special case for httpd-2.0 */
# if !defined(OS2)  !defined(WIN32)  !defined(BEOS)  
!defined(NETWARE)

#  define JK_NEED_SET_MUTEX_PERMS 1
# else
#  define JK_NEED_SET_MUTEX_PERMS 0
# endif
#endif

#if JK_NEED_SET_MUTEX_PERMS
#include unixd.h  /* for unixd_set_global_mutex_perms */
#endif

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 7 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 30 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c -o 
jk_ajp12_worker.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_connect.c -o jk_connect.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_msg_buff.c -o jk_msg_buff.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_util.c -o jk_util.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13.c -o jk_ajp13.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_pool.c -o jk_pool.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_worker.c -o jk_worker.lo

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 7 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 30 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c -o 
jk_ajp12_worker.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_connect.c -o jk_connect.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_msg_buff.c -o jk_msg_buff.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_util.c -o jk_util.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13.c -o jk_ajp13.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_pool.c -o jk_pool.lo
/usr/local/gump/public/workspace/apr/dest-15092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_worker.c -o jk_worker.lo

Re: How strongly Tomcat 5.5.x will be committed to JDK 1.4.x in future..

[Bill Barker]

- Original Message -
From: Costin Manolache [EMAIL PROTECTED]
To: tomcat-dev@jakarta.apache.org
Sent: Wednesday, September 14, 2005 10:54 PM
Subject: Re: How strongly Tomcat 5.5.x will be committed to JDK 1.4.x in
future..


 The current servlet spec doesn't requires J2SE 5.0 - only the next one (
 another stupid forced, unjustified transition IMO ).

 I would assume JDK1.4 will be supported for a while, as long as the
 current version of the servlet spec is in use.
 Tomcat3.3, which supports JDK1.1, has been maintained for quite a while
 after switching to JDK1.3 and then JDK1.4. I don't see how anyone who
 has been around for past upgrades could expect a mass migration to the
 new servlet spec and JDK1.5.


Actually, TC 3.3.3-dev currently requires JDK1.2.  See BZ #28921.


 Costin

 Yoav Shapira wrote:
  Hi,
  Tomcat 5.5 will always allow JDK 1.4.  Tomcat 6.0, as required by the
J2EE 5
  specifications, will require J2SE 5.0.  I repeat, for emphasis, that
this is
  required by the J2EE 5 Specification itself, which Tomcat 6.0 will
support: it
  is not our decision to drop support for JDK 1.4.
 
  Yoav
 
  --- Girish Vasvani [EMAIL PROTECTED] wrote:
 
 
 Hi,
 
 We'r puzzled between tomcat 5.0.x and 5.5.x.
 Due to our product restrictions we can't use JDK 1.5. Looked at jakarta
web
 site, it seems that using tomcat 5.5.x seriese compated to 5.0.x is a
good
 idea and recommended.
 
 Before committing our product to tomcat 5.5.9, I want to know how much
tomcat
 dev team will be committed to supporting JDK 1.4.x going forward ?
 
 thanks in advance for your help,
 Girish
 
 
 
 -
 Yahoo! for Good
  Click here to donate to the Hurricane Katrina relief effort.


 -
 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: svn commit: r280906 - in /tomcat/site/trunk: docs/ docs/faq/ xdocs/

[Bill Barker]

- Original Message -
From: Mark Thomas [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, September 14, 2005 12:05 PM
Subject: Re: svn commit: r280906 - in /tomcat/site/trunk: docs/ docs/faq/
xdocs/


 The basic content for the TLP site is now done and can be reviewed at
 http://people.apache.org/~markt/tomcattlp/index.html

 Whilst I want to tidy it up (remove duplication, fix typos, etc) and
 someone who knows more about our history than me needs to write
 something for the heritage page, I don't see why we could not go live
 with this.

 I think the remaining steps to move to TLP are:

 1. SVN
a) Migrate TC3  TC4 - In progress as I type
b) Migrate TC5, Connectors and Jasper - will start once a) is done

 2. Website
a) Need tomcat.apache.org created

It's been there for a while now :).

b) Load content from SVN (trivial)

 3. Lists
a) [EMAIL PROTECTED]   - [EMAIL PROTECTED]
b) [EMAIL PROTECTED]- [EMAIL PROTECTED]
c) [EMAIL PROTECTED] - [EMAIL PROTECTED]
d) Create [EMAIL PROTECTED] (posts from pmc only)

 4. Gump
a) Change to use SVN


Already done for servletapi/*.  (e.g.
http://vmgump.apache.org/gump/public/jakarta-servletapi-5/gump_work/update_j
akarta-servletapi-5.html).  Just waiting on the SVN URLs for the rest.


 5. Downloads/Archives
a) Move from Jakarta to Tomcat

 6. Wiki
a) Do we want a Tomcat wiki?

 What have I missed?

 Mark



 -
 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: Why / 1000 * 1000

[Bill Barker]

HTTP headers only send times to the second, so yes, to drop off some 
precision.


- Original Message - 
From: Yaakov Chaikin [EMAIL PROTECTED]

To: tomcat-dev@jakarta.apache.org
Sent: Wednesday, September 14, 2005 8:37 PM
Subject: Why / 1000 * 1000


Hi,

While reading the Tomcat's source code, I noticed the following line
in the service method of the HttpServlet class:
if (ifModifiedSince  (lastModified / 1000 * 1000))

What's the point of / 1000 * 1000? To drop off some precision?

Thanks,
Yaakov.

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 31 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c -o 
jk_ajp12_worker.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_connect.c -o jk_connect.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_msg_buff.c -o jk_msg_buff.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_util.c -o jk_util.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13.c -o jk_ajp13.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_pool.c -o jk_pool.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_worker.c -o jk_worker.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 31 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c -o 
jk_ajp12_worker.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_connect.c -o jk_connect.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_msg_buff.c -o jk_msg_buff.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_util.c -o jk_util.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13.c -o jk_ajp13.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_pool.c -o jk_pool.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13092005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-13092005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_worker.c -o jk_worker.lo
/usr/local/gump/public/workspace/apr/dest-13092005/build-1/libtool --silent 
--mode=compile gcc 

Re: Small refactoring in Http11Processor

[Bill Barker]

- Original Message -
From: Costin Manolache [EMAIL PROTECTED]
To: tomcat-dev@jakarta.apache.org
Sent: Thursday, September 08, 2005 10:56 PM
Subject: Small refactoring in Http11Processor


 Hi,

 I have a small patch, spliting the JMX-dependent code in
 Http11Processor, i.e.  the few lines of code dealing with the
 registration of the thread pool and per thread data - and moving all
 non-jmx code in a separate base class.

 I know Tomcat5 is heavily dependent on JMX, but the connector can be
 used in other containers, or it can be used standalone. This small
 change won't affect any functionality on tomcat - all methods are used
 only for intialization anyway, not in the critical path.

 Please review and let me know if it's ok to commit the change.


It seems that the only thing this patch does is to allow you to exclude
jmx.jar, so it's usefulness seems very minimal :).  TC 3.3  4.1 already run
very happily with the current code without JMX enabled.

Something better would be a refactor that would remove the duplicated code
between Http11Processor and Http11AprProcessor (which one doesn't do :).

Of course, none of this is enough for me to veto your scratching an itch :).

 Also, I would like to add another directory under j-t-c, with a build
 file and few classes for a 'mini' experiment - i.e. using the connector
 standalone, as a minimal http server, and also a target to build a
 minimal servlet container as a single self-contained jar. We don't have
 a sandbox, and j-t-c seems closest to that :-)


I agree with Mladen that this would work better if you could wait a couple
of weeks until we are up on SVN.

 Costin




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: Subversion migration update

[Bill Barker]

- Original Message -
From: Henri Yandell [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Friday, August 19, 2005 5:37 PM
Subject: Re: Subversion migration update


On 8/17/05, Mark Thomas [EMAIL PROTECTED] wrote:

 Assuming everyone else is happy to move the remaining tomcat modules
 to SVN I would suggest the following stages (Watchdog was stage 1).
 I'll give people at least a week to comment on this proposal and
 assuming no -1's start the phase 2 towards the end of next week.

 2. j-t-service, j-t-site
 3. j-servletapi, j-servletapi-4, j-servletapi-5
 4. j-tomcat, j-tomcat-4.0
 5. j-t-catalina, j-t-5, j-t-jasper, j-t-connectors

 Any other comments/concerns?

I have jakarta-tools down as a Tomcat CVS module, though looking at it
seems to indicate that it is very dead, not edited for 5 years.

Yup, it's a dodo ;-).


Still, the tags are all TOMCAT_3_1 based, so I figure you guys get to
decide what to do with it:

* Somehow come over to SVN because Tomcat-3's tags will need it to
build(?).
* Put into the pot for archiving
(http://www.apache.org/dev/drafts/subversion-migration-plan.txt)


It's needed for Watchdog, but not Tomcat.  My vote is to archive it, since
it is extremely unlikely that it will ever come to life ever again.

Hen




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: inprocess Tomcat/apache via mod_jk

[Bill Barker]

Well, inprocess doesn't really work for any MPM on *nix systems (e.g. with
the prefork MPM, you end up with MaxChild copies of Tomcat running :).  As a
result, there just hasn't been that much interest in implementing (or even
back-porting) a feature that only works on Windows and NetWare.


- Original Message -
From: Christine Ho [EMAIL PROTECTED]
To: tomcat-dev@jakarta.apache.org
Sent: Tuesday, August 16, 2005 3:30 PM
Subject: inprocess Tomcat/apache via mod_jk


Hi,
   I have posted this email a month ago. I just wonder
if any developer on mod_jk can answer my question. I
would like to have inprocess Tomcat 5.5.9 running in
Apache 2.x if possible.

thanks again,
Christine


Hi,
   I tried to setup Tomcat 5.5.9 running inside the
apache server 2.x via the mod_jk on RHEL4. I got the
following error:
[debug] open_jvm2::jk_jni_worker.c (1055): JVM created
[emerg] get_bridge_object::jk_jni_worker.c (1097):
Can't find class
org/apache/tomcat/modules/server/JNIEndpoint

I looked at the mod_jk source codes and found out that
the mod_jk supports the TC32_BRIDGE_TYPE and
TC33_BRIDGE_TYPE. It doesnt support bridge type of
tomcat 4.x and up. Plus the tomcat 5.5.9 doesnt have
the JNIEndpoint.class.

However, it seems to me that the deprecated mod_jk2
supports bridge type of tomcat 4.x and up because it
tries to instantiate the class
org/apache/jk/apr/TomcatStarter.class which exists in
tomcat-ajp.jar.

I really dont understand why the mod_jk supports
tomcat 3.x only whereas the deprecated mod_jk2
supports tomcat 4.x and 5.x. Can somebody please tell
me why?

Also is it easy to have mod_jk to support
TC55_BRIDGE_TYPE? Based on the mod_jk source codes
jk_jni_worker.c, I think I just need to define the
TC55_JAVA_BRIDGE_CLASS_NAME to be
org/apache/jk/apr/TomcatStarter.class and then assign
it to the btype. Is it just that simple?

Another question is what the disadvantages of running
tomcat inside the apache are. I googled and it seems
to me that not too many people try to run inprocess
tomcat inside apache. I would be interested in adding
the 5.5 bridge type to the mod_jk.

thanks,
Christine


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

-
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: svn commit: r232600 - /tomcat/watchdog/branches/tc3.3.x/WARNING.txt

[Bill Barker]

- Original Message -
From: Mark Thomas [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Monday, August 15, 2005 11:00 AM
Subject: Re: svn commit: r232600 -
/tomcat/watchdog/branches/tc3.3.x/WARNING.txt


 Mark Thomas wrote:
  Bill Barker wrote:
 
  As a historical note, this really should be the tc3.2.x branch.  This
  particular watchdog has never worked well with any TC 3.3.x, since it
  has a lot of bugs related to specific implementation details of TC
  3.2.x (and, the Watchdog committers mostly moved on to TC 4.0.x during
  the Great Flame Wars, so it couldn't be fixed by TC 3.3.x committers
:).
 
 
  Thanks for the clarification. I'll change it. That's once of the nice
  things about subversion - renames (files or directories) are easy and
  you keep the history.

 Bill,

 I have taken another look at the repository. There is a separate
 tomcat_32 branch so I assumed that the old HEAD in CVS must have been
 for 3.3.x (even if not much was done with it). Is this assumption
 correct? If not, what is the correct interpretation?


Actually, I haven't been here that long  ;-).  Maybe Larry or Costin can
remember why Watchdog was branched.  It was pretty much dead by the time I
joined tomcat-dev.  All I know is that it needs quite a few patches to work
with TC 3.3.x.

 As part of the migration to a TLP we will need to put together our own
 version control and download pages (rather than use the Jakarta ones).
 I plan to include an explanation of the SVN structure in the version
 control page. I can include additional information such your note
 above in this explanation.

 Cheers,

 mark



 -
 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: svn commit: r232600 - /tomcat/watchdog/branches/tc3.3.x/WARNING.txt

[Bill Barker]

- Original Message - 
From: [EMAIL PROTECTED]

To: tomcat-dev@jakarta.apache.org
Sent: Sunday, August 14, 2005 4:48 AM
Subject: svn commit: r232600 - /tomcat/watchdog/branches/tc3.3.x/WARNING.txt

As a historical note, this really should be the tc3.2.x branch.  This 
particular watchdog has never worked well with any TC 3.3.x, since it has a 
lot of bugs related to specific implementation details of TC 3.2.x (and, the 
Watchdog committers mostly moved on to TC 4.0.x during the Great Flame Wars, 
so it couldn't be fixed by TC 3.3.x committers :). 




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: Support JSS in Tomcat

[Bill Barker]

- Original Message -
From: Christine Ho [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, August 10, 2005 10:44 AM
Subject: Re: Support JSS in Tomcat


Hi,
  I am working for Redhat and I dont think this is a
problem of contributing the codes to the ASF. What
kind of procedures I need to follow in order to submit
my codes?


And just after I WONTFIXed Joe's bug report :(.

It's likely that Redhat has a Corporate CLA on file with the ASF that would
cover this.  If so, then they just need to add your name to their
contributer list (if it's not already there).  It's likely that somebody at
Redhat knows the relationship with ASF better than I do.  All I know is that
[EMAIL PROTECTED] is very active with httpd.

Then all you have to do is to open an enhancement request at
  http://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%205
and add your code as one or more attachements.

thanks,
Christine




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: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 InternalAprOutputBuffer.java Http11AprProcessor.java

[Bill Barker]

- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 04, 2005 12:07 AM
Subject: cvs commit:
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11
InternalAprOutputBuffer.java Http11AprProcessor.java


 remm2005/08/04 00:07:57

   Modified:jk/java/org/apache/coyote/ajp AjpAprProcessor.java
http11/src/java/org/apache/coyote/http11
 InternalAprOutputBuffer.java
 Http11AprProcessor.java
   Log:
   - Remove useless HTTP/1.1 PAs (which seem to be only there for initial
 access to the util package).
   - Fix AJP APR when security is enabled (access to the util package was
failing).


It looks like you did the same thing I did with JK:  Remove the useless PAs,
and then don't bother to test on a clean build (so that SecurityClassLoad
can still find the removed classes and doesn't complain).  If you don't want
BZ 35894 re-opened, you also need to remove the reference to the removed PAs
in SecurityClassLoad ;-).



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: Problems with tomcat 3.3.2 and IBM JRE 1.3.0

[Bill Barker]

I didn't catch this one early enough :(.  JDK 1.3.0 doesn't handle indexes 
in jar files at all.  You need to remove them to run on 1.3.0.  Or, better, 
upgrade to at least 1.3.1.


- Original Message - 
From: Eduardo Piva [EMAIL PROTECTED]

To: tomcat-dev@jakarta.apache.org
Sent: Monday, August 01, 2005 4:36 AM
Subject: Problems with tomcat 3.3.2 and IBM JRE 1.3.0


Hello list,

I'm trying to use tomcat 3.3.2 with JDK 1.3.0. I'm developing an
application in Linux/Windows, using SUN JDK 1.3.0 and tomcat 3.3.2 to
test everything locally and everything is going fine. This application
will run on an AIX 4, and in this machine the only JRE the sysadmins
managed to install was IBM JRE 1.3.0:


$ java -version
java version 1.3.0
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build ca130-20010330 (JIT
enabled: jitc))


I don't know why, but tomcat 3.3.2 doesn't starts in this machine. I
need to run the tomcat in this machine, mainly because of internal
problems here in the company I'm working to.

The sysadmin installed tomcat 3.3.1a in this machine, which start's
correctly. With this version, my application refuses to start in the
AIX. In Linux with JDK 1.3.0, it start's correctly.

I have two questions:

1 - Why jakarta-tomcat 3.3.2 doesn't start's with IBM jdk 1.3.0? Does
anyone here managed to do that?
2 - Why my application doesn't start in jakarta-tomcat 3.3.1a in IBM jdk 
1.3.0?

3 - Does anyone here uses AIX 4 and knows another VM than the one
supplied by IBM for the AIX? AIX 4 is an old version and IBM does not
supply JRE 1.4 neither 1.5 for this version. If anyone know how to use
a newer version, please help me. :)

The logs for both problems 1 and 2 are supplied below:

For tomcat 3.3.2, here is the log (after this log, there is the log
for my application starting in tomcat 3.3.1a):
$ ./startup
Using classpath: ./../lib/tomcat.jar:./../lib/common/commons-logging-api.jar
Using JAVA_HOME: /usr/java130
Using TOMCAT_HOME: /home/aep022/jakarta-tomcat-3.3.2/
ERROR reading /home/aep022/jakarta-tomcat-3.3.2/conf/server.xml
At Line 209 /Server/ContextManager/Http10Connector/ port=8080
secure=false maxThreads=100 maxSpareThreads=50 minSpareThreads=10
java.util.MissingResourceException: Can't find bundle for base name
org.apache.tomcat.util.net.res.LocalStrings, locale en_US
   at 
java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java(Compiled

Code))
   at 
java.util.ResourceBundle.getBundleImpl(ResourceBundle.java(Compiled

Code))
   at java.util.ResourceBundle.getBundle(ResourceBundle.java:547)
   at 
org.apache.tomcat.util.res.StringManager.init(StringManager.java:78)
   at 
org.apache.tomcat.util.res.StringManager.init(StringManager.java:70)
   at 
org.apache.tomcat.util.res.StringManager.getManager(StringManager.java:249)
   at 
org.apache.tomcat.util.net.PoolTcpEndpoint.init(PoolTcpEndpoint.java:58)
   at 
org.apache.tomcat.modules.server.PoolTcpConnector.init(PoolTcpConnector.java:60)
   at 
org.apache.tomcat.modules.server.Http10Interceptor.init(Http10Interceptor.java:68)

   at java.lang.Class.newInstance0(Native Method)
   at java.lang.Class.newInstance(Class.java:254)
   at org.apache.tomcat.util.xml.ObjectCreate.start(XmlMapper.java:797)
   at 
org.apache.tomcat.util.xml.XmlMapper.matchStart(XmlMapper.java:516)
   at 
org.apache.tomcat.util.xml.XmlMapper.startElement(XmlMapper.java:114)
   at 
org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java(Compiled

Code))
   at 
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java(Compiled

Code))
   at 
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java(Compiled

Code))
   at 
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java(Compiled

Code))
   at 
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:380)

   at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908)
   at org.apache.tomcat.util.xml.XmlMapper.readXml(XmlMapper.java:334)
   at 
org.apache.tomcat.modules.config.ServerXmlReader.loadConfigFile(ServerXmlReader.java:137)
   at 
org.apache.tomcat.modules.config.ServerXmlReader.addInterceptor(ServerXmlReader.java:113)
   at 
org.apache.tomcat.core.ContextManager.addInterceptor(ContextManager.java:393)
   at 
org.apache.tomcat.startup.EmbededTomcat.initContextManager(EmbededTomcat.java:613)
   at 
org.apache.tomcat.startup.EmbededTomcat.execute1(EmbededTomcat.java:791)
   at 
org.apache.tomcat.startup.EmbededTomcat$1.run(EmbededTomcat.java:775)
   at 
org.apache.tomcat.util.compat.Jdk12Support$PrivilegedProxy.run(Jdk12Support.java:166)

   at java.security.AccessController.doPrivileged(Native Method)
   at 
org.apache.tomcat.util.compat.Jdk12Support.doPrivileged(Jdk12Support.java:76)
   at 

[EMAIL PROTECTED]: Project jakarta-tomcat-http11 (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-http11 has an issue affecting its community integration.
This issue affects 67 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cocoon :  Java XML Framework
- cocoon-block-apples :  Java XML Framework
- cocoon-block-asciiart :  Java XML Framework
- cocoon-block-authentication-fw :  Java XML Framework
- cocoon-block-axis :  Java XML Framework
- cocoon-block-batik :  Java XML Framework
- cocoon-block-bsf :  Java XML Framework
- cocoon-block-chaperon :  Java XML Framework
- cocoon-block-cron :  Java XML Framework
- cocoon-block-databases :  Java XML Framework
- cocoon-block-deli :  Java XML Framework
- cocoon-block-eventcache :  Java XML Framework
- cocoon-block-faces :  Java XML Framework
- cocoon-block-fop :  Java XML Framework
- cocoon-block-forms :  Java XML Framework
- cocoon-block-hsqldb :  Java XML Framework
- cocoon-block-html :  Java XML Framework
- cocoon-block-itext :  Java XML Framework
- cocoon-block-javaflow :  Java XML Framework
- cocoon-block-jcr :  A jcr: protocol for Cocoon
- cocoon-block-jfor :  Java XML Framework
- cocoon-block-jms :  Java XML Framework
- cocoon-block-jsp :  Java XML Framework
- cocoon-block-linkrewriter :  Java XML Framework
- cocoon-block-lucene :  Java XML Framework
- cocoon-block-mail :  Java XML Framework
- cocoon-block-midi :  Java XML Framework
- cocoon-block-naming :  Java XML Framework
- cocoon-block-paranoid :  Java XML Framework
- cocoon-block-petstore :  Java XML Framework
- cocoon-block-portal :  Java XML Framework
- cocoon-block-profiler :  Java XML Framework
- cocoon-block-proxy :  Java XML Framework
- cocoon-block-python :  Java XML Framework
- cocoon-block-qdox :  Java XML Framework
- cocoon-block-repository :  Java XML Framework
- cocoon-block-scratchpad :  Java XML Framework
- cocoon-block-serializers :  Java XML Framework
- cocoon-block-session-fw :  Java XML Framework
- cocoon-block-slop :  Java XML Framework
- cocoon-block-spring-app :  A demo for Spring and Cocoon
- cocoon-block-stx :  Java XML Framework
- cocoon-block-taglib :  Java XML Framework
- cocoon-block-template :  Java XML Framework
- cocoon-block-tour :  Java XML Framework
- cocoon-block-velocity :  Java XML Framework
- cocoon-block-web3 :  Java XML Framework
- cocoon-block-xmldb :  Java XML Framework
- cocoon-block-xsp :  Java XML Framework
- db-torque :  Persistence Layer
- forrest :  Apache Forrest is an XML standards-oriented documentation fr...
- forrest-test :  Apache Forrest is an XML standards-oriented documentation 
fr...
- fulcrum-intake :  Services Framework
- fulcrum-security-adapter-turbine :  Services Framework
- jakarta-cactus-documentation :  Cactus Documentation
- jakarta-cactus-release-12 :  Unit test framework for server-side java code
- jakarta-cactus-release-13 :  Unit test framework for server-side java code
- jakarta-cactus-sample-servlet-12 :  Cactus Servlet Sample (J2EE 1.2)
- jakarta-jetspeed :  Enterprise Information Portal
- jakarta-tomcat :  Servlet 2.2 and JSP 1.1 Reference Implementation
- jakarta-tomcat-coyote-tomcat3 :  Connectors to various web servers
- jakarta-tomcat-http11 :  Connectors to various web servers
- jakarta-turbine-2 :  A servlet based framework.
- jakarta-turbine-3 :  A servlet based framework.
- jakarta-turbine-jcs :  Cache
- lenya :  Content Management System
- scarab :  Issue Tracking Built for the Ages


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-http11.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-http11.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-http11 (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-modeler.jar=/usr/local/gump/public/workspace/jakarta-commons/modeler/dist/commons-modeler-30072005.jar
 

[EMAIL PROTECTED]: Project jakarta-tomcat-http11 (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-http11 has an issue affecting its community integration.
This issue affects 67 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cocoon :  Java XML Framework
- cocoon-block-apples :  Java XML Framework
- cocoon-block-asciiart :  Java XML Framework
- cocoon-block-authentication-fw :  Java XML Framework
- cocoon-block-axis :  Java XML Framework
- cocoon-block-batik :  Java XML Framework
- cocoon-block-bsf :  Java XML Framework
- cocoon-block-chaperon :  Java XML Framework
- cocoon-block-cron :  Java XML Framework
- cocoon-block-databases :  Java XML Framework
- cocoon-block-deli :  Java XML Framework
- cocoon-block-eventcache :  Java XML Framework
- cocoon-block-faces :  Java XML Framework
- cocoon-block-fop :  Java XML Framework
- cocoon-block-forms :  Java XML Framework
- cocoon-block-hsqldb :  Java XML Framework
- cocoon-block-html :  Java XML Framework
- cocoon-block-itext :  Java XML Framework
- cocoon-block-javaflow :  Java XML Framework
- cocoon-block-jcr :  A jcr: protocol for Cocoon
- cocoon-block-jfor :  Java XML Framework
- cocoon-block-jms :  Java XML Framework
- cocoon-block-jsp :  Java XML Framework
- cocoon-block-linkrewriter :  Java XML Framework
- cocoon-block-lucene :  Java XML Framework
- cocoon-block-mail :  Java XML Framework
- cocoon-block-midi :  Java XML Framework
- cocoon-block-naming :  Java XML Framework
- cocoon-block-paranoid :  Java XML Framework
- cocoon-block-petstore :  Java XML Framework
- cocoon-block-portal :  Java XML Framework
- cocoon-block-profiler :  Java XML Framework
- cocoon-block-proxy :  Java XML Framework
- cocoon-block-python :  Java XML Framework
- cocoon-block-qdox :  Java XML Framework
- cocoon-block-repository :  Java XML Framework
- cocoon-block-scratchpad :  Java XML Framework
- cocoon-block-serializers :  Java XML Framework
- cocoon-block-session-fw :  Java XML Framework
- cocoon-block-slop :  Java XML Framework
- cocoon-block-spring-app :  A demo for Spring and Cocoon
- cocoon-block-stx :  Java XML Framework
- cocoon-block-taglib :  Java XML Framework
- cocoon-block-template :  Java XML Framework
- cocoon-block-tour :  Java XML Framework
- cocoon-block-velocity :  Java XML Framework
- cocoon-block-web3 :  Java XML Framework
- cocoon-block-xmldb :  Java XML Framework
- cocoon-block-xsp :  Java XML Framework
- db-torque :  Persistence Layer
- forrest :  Apache Forrest is an XML standards-oriented documentation fr...
- forrest-test :  Apache Forrest is an XML standards-oriented documentation 
fr...
- fulcrum-intake :  Services Framework
- fulcrum-security-adapter-turbine :  Services Framework
- jakarta-cactus-documentation :  Cactus Documentation
- jakarta-cactus-release-12 :  Unit test framework for server-side java code
- jakarta-cactus-release-13 :  Unit test framework for server-side java code
- jakarta-cactus-sample-servlet-12 :  Cactus Servlet Sample (J2EE 1.2)
- jakarta-jetspeed :  Enterprise Information Portal
- jakarta-tomcat :  Servlet 2.2 and JSP 1.1 Reference Implementation
- jakarta-tomcat-coyote-tomcat3 :  Connectors to various web servers
- jakarta-tomcat-http11 :  Connectors to various web servers
- jakarta-turbine-2 :  A servlet based framework.
- jakarta-turbine-3 :  A servlet based framework.
- jakarta-turbine-jcs :  Cache
- lenya :  Content Management System
- scarab :  Issue Tracking Built for the Ages


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-http11.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-http11.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-http11 (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-modeler.jar=/usr/local/gump/public/workspace/jakarta-commons/modeler/dist/commons-modeler-30072005.jar
 

Re: Migration to Subversion

[Bill Barker]

- Original Message -
From: Mark Thomas [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Friday, July 29, 2005 3:30 PM
Subject: Re: Migration to Subversion


 Yoav Shapira wrote:
 
 Any and all comments appreciated. In particular:
 a. Should more 3.x.x versions should be included in 4  5 above?
 b. I have assumed that all releases before 5.5.x will use the 5.0 branch
 of the connectors. Is this assumption valid?
 
  I don't think so.  Some Tomcat 3.x versions, for example, already use
the
  latest connectors that are also used by Tomcat 5.5.

 That is fine as long as you build and run on a 1.4+ JDK but when checking
for
 1.3 compatibility the Coyote/HTTP connector fails. The root cause is the
use
 of the 1.4 regexp API in o.a.coyote.http11.Http11Processor
 (http://marc.theaimsgroup.com/?l=tomcat-devm=109403344007532w=2).


This is true.  However in TC 3.3 the Coyote connectors have always been
optional.  That's why I've kept it using j-t-c HEAD even with the 1.4
dependancy.  Of course, it's pretty mote until it's time to do a 3.3.3
release ;-).

 Possible solutions:
 1. Use the 5.0 branch
 2. Revert the patch and go back to using jakarta-regexp
 3. Introduce an o.a.coyote.http11.tomcat4 package and place a copy of
 Http11Processor in it that uses jakarta-regexp.

 Pros/Cons
 1. Would mean an awful lot of porting.
 2. Quick but adds an unnecessary library to TC5 and leaves TC5 using two
 different regexp libs
 3. Relatively quick but would need some build.xml tweaking for TC5

 Unless anyone has a better idea, I'll crack on with 3 over the weekend.


I've thought that it should be possible to do this with an Ant filter (so
that you don't have to maintain a separate copy of the file).  I've always
been too lazy to actually sit down and write it however. :).

 On the Subversion front, I have TC4 building with
jakarta-tomcat-connectors
 HEAD and will commit it once I have finished testing the various connector
and
 JVM combinations (I don't plan to provide APR support in TC4). Once I have
got
 this out of the way, I'll work with Henri on the test Watchdog migration.

 Mark


 -
 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: How Test the experimental NIO Socket

[Bill Barker]

The simplest is with:
Connector protocol=AJP/1.3 port=0
  channelNioSocket.port=8009
  channelNioSocket.maxThreads=250
  channelNioSocket.maxSpareThreads=50
  channelNioSocket.minSpareThreads=25
  channelNioSocket.bufferSize=16384  /

(of course, tune the values for your system).  You can also configure this
in jk2.properties via:
   Connector protocol=AJP/1.3 propertiesFile=conf/jk2.properties /

All of this assumes that libtcnative.so isn't on your java.library.path.
Otherwise, you need to set the protocol in the examples above to
protocol=org.apache.jk.server.JkCoyoteHandler.

- Original Message -
From: Mauricio Nuñez [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, July 27, 2005 1:51 PM
Subject: How Test the experimental NIO Socket


Hi developers!

I want to test the NIO Socket, but i'm only getting that via jconsole
(JMX), updating the property file of the JkMain MBean. Initially, that
is null, then don't read the jk2.properties.

There are another approach  ?

( editing server.xml , for example )

Thanks

Mauricio Nuñez

[EMAIL PROTECTED]




-
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: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml

[Bill Barker]

- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 26, 2005 5:45 AM
Subject: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml


 remm2005/07/26 05:45:22

   Modified:catalina/src/share/org/apache/catalina/valves
ValveBase.java
 ErrorReportValve.java mbeans-descriptors.xml
catalina build.xml
webapps/docs changelog.xml
   Added:   catalina/src/share/org/apache/catalina/valves
 SemaphoreValve.java
   Log:
   - Add a simple valve for concurrency control, with a conditional
compilation
 flag.
   - At the moment, this will not be shipped in the release (needs Java 5).
   - Update changelog.
snip/
   /**
* Create a new StandardHost component with the default basic Valve.
*/
   public SemaphoreValve() {
   semaphore = new Semaphore(concurrency, fairness);
   }


This happens before the setters get called (so only the default values are
possible).  You probably want to implement Lifecycle and create the
Semaphore in a Lifecycle method.




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: [ANN] Apache Jakarta Tomcat v5.5.10-alpha Released

[Bill Barker]

- Original Message - 

From: Yoav Shapira [EMAIL PROTECTED]
To: Tomcat-dev tomcat-dev@jakarta.apache.org; Tomcat-user 
tomcat-[EMAIL PROTECTED]; jakarta-pmc [EMAIL PROTECTED]; 
[EMAIL PROTECTED]; community@apache.org

Sent: Sunday, July 24, 2005 9:59 AM
Subject: [ANN] Apache Jakarta Tomcat v5.5.10-alpha Released



The Apache Jakarta Tomcat team is proud to announce the immediate 
availability

of Tomcat 5.5.10-alpha. This build contains 110 improvements, including bug
fixes, enhancements, and documentation updates.  There are several 
interesting
new features, such as Apache Portable Runtime (APR)-based HTTP/1.1 and 
AJP/1.3
protocol handlers with SSL support, an experimental NIO-Socket channel for 
the

AJP/1.3 connector, improved support for Java 5 using the Eclipse 3.1 JDT,
clustering support at the Engine and Host levels, and more.

The Release notes are available at
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/RELEASE-NOTES

Please refer to the change log for the list of changes:
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/changelog.html

Downloads: Binaries: http://jakarta.apache.org/site/binindex.cgi#tomcat-5.5
Sources: http://jakarta.apache.org/site/sourceindex.cgi#tomcat-5.5

The Apache Jakarta Tomcat Team



We're not Jakarta Tomcat anymore :). 




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: Support JSS in Tomcat

[Bill Barker]

- Original Message -
From: Christine Ho [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org;
[EMAIL PROTECTED]
Sent: Friday, July 22, 2005 10:22 AM
Subject: Re: Support JSS in Tomcat



--- Bill Barker [EMAIL PROTECTED] wrote:

 I don't think that anybody is proposing bundling
 jss34.jar with Tomcat.  It
 would be an optional dependency much like PureTLS is
 now.  Anybody that
 wanted to use it would have to download it from
 mozilla.org and install it.
 And as Remy pointed out, Christine would have to
 agree to donate her code to
 the ASF, at which point it would be licensed under
 ASFL.


I have no problem to donate the codes to the ASF. I
just need the approval from my manager because the
code is owned by the company.

Since the code is owned by the company, you should probably take a look at
http://www.apache.org/licenses/#grants.  I'm not trying to be a hard-ass,
it's just that I have an irrational fear of lawyers ;-).

Besides jss.jar, people also need to download two
shared libraries, nspr and nss from mozilla.org
because JSS is not pure JAVA implementation.

Christine

 My reading of MPL-1.1 (again IANAL) is that:
   import org.mozilla.some.package.SomeClass;

 isn't viral, so that there isn't any problem with
 having
 o.a.t.u.net.jss.JSSServerSocketFactory with an ASF
 license.









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: Support JSS in Tomcat

[Bill Barker]

- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, July 21, 2005 3:03 AM
Subject: Re: Support JSS in Tomcat


Christine Ho wrote:
 Thanks. It works.

 JSS can be used under either Mozilla Public License
 (MPL) or LGPL. Is MPL or LGPL compatible with ASF
 license? The good thing about JSS is that it is
 FIPS-140 compliant.

First, the Tomcat portion of the code needs to be donated to the ASF.
The code cannot import LGPL packages, but I don't know about MPL (I'd
say it's ok).


MPL is listed as ok on http://wiki.apache.org/jakarta/LicenceIssues.

Rémy





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: Support JSS in Tomcat

[Bill Barker]

- Original Message -
From: Jean-frederic Clere [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, July 21, 2005 11:33 AM
Subject: Re: Support JSS in Tomcat


Bill Barker wrote:

- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, July 21, 2005 3:03 AM
Subject: Re: Support JSS in Tomcat




Christine Ho wrote:


Thanks. It works.

JSS can be used under either Mozilla Public License
(MPL) or LGPL. Is MPL or LGPL compatible with ASF
license? The good thing about JSS is that it is
FIPS-140 compliant.


First, the Tomcat portion of the code needs to be donated to the ASF.
The code cannot import LGPL packages, but I don't know about MPL (I'd
say it's ok).




MPL is listed as ok on http://wiki.apache.org/jakarta/LicenceIssues.


But it says in comments:

(confirm. 1.0, 1.1 different?)


IANAL, but the relevant parts of 1.0  1.1 look the same.  Of course, it's
up to the Tomcat PMC to decide the policy on importing MPLed classes :).



Rémy








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: Support JSS in Tomcat

[Bill Barker]

- Original Message -
From: Jean-frederic Clere [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, July 21, 2005 2:53 PM
Subject: Re: Support JSS in Tomcat


Bill Barker wrote:

- Original Message -
From: Jean-frederic Clere [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, July 21, 2005 11:33 AM
Subject: Re: Support JSS in Tomcat




Bill Barker wrote:



- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, July 21, 2005 3:03 AM
Subject: Re: Support JSS in Tomcat






Christine Ho wrote:




Thanks. It works.

JSS can be used under either Mozilla Public License
(MPL) or LGPL. Is MPL or LGPL compatible with ASF
license? The good thing about JSS is that it is
FIPS-140 compliant.




First, the Tomcat portion of the code needs to be donated to the ASF.
The code cannot import LGPL packages, but I don't know about MPL (I'd
say it's ok).





MPL is listed as ok on http://wiki.apache.org/jakarta/LicenceIssues.




But it says in comments:

(confirm. 1.0, 1.1 different?)




IANAL, but the relevant parts of 1.0  1.1 look the same.  Of course, it's
up to the Tomcat PMC to decide the policy on importing MPLed classes :).


The following worried me a little:
http://mail-archives.apache.org/mod_mbox/jakarta-jmeter-dev/200403.mbox/%3C
[EMAIL PROTECTED]


I don't think that anybody is proposing bundling jss34.jar with Tomcat.  It
would be an optional dependency much like PureTLS is now.  Anybody that
wanted to use it would have to download it from mozilla.org and install it.
And as Remy pointed out, Christine would have to agree to donate her code to
the ASF, at which point it would be licensed under ASFL.

My reading of MPL-1.1 (again IANAL) is that:
  import org.mozilla.some.package.SomeClass;

isn't viral, so that there isn't any problem with having
o.a.t.u.net.jss.JSSServerSocketFactory with an ASF license.





Rémy













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: cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java

[Bill Barker]

- Original Message - 
From: Jan Luehe [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, July 21, 2005 6:24 PM
Subject: Re: cvs commit: 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler 
Generator.java




Bill,

[EMAIL PROTECTED] wrote:

billbarker2005/07/20 20:59:10

  Modified:jasper2/src/share/org/apache/jasper/compiler 
Generator.java

  Log:
  Make certain that release is called for custom tags when tag-pooling is 
disabled.


  Fix for Bug #35696

  Revision  ChangesPath
  1.241 +9 -2 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java


  Index: Generator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v

  retrieving revision 1.240
  retrieving revision 1.241
  diff -u -r1.240 -r1.241
  --- Generator.java 5 Apr 2005 23:14:43 - 1.240
  +++ Generator.java 21 Jul 2005 03:59:10 - 1.241
  @@ -2278,15 +2278,19 @@
   out.printin(if ();
   out.print(tagHandlerVar);
   out.println(
  -.doEndTag() == 
javax.servlet.jsp.tagext.Tag.SKIP_PAGE));
  +.doEndTag() == 
javax.servlet.jsp.tagext.Tag.SKIP_PAGE) {);

   out.pushIndent();
  +if(!n.implementsTryCatchFinally()) {
  +out.printin(tagHandlerVar);
  +out.println(.release(););
  +}


I believe the above 4 added lines need to be replaced with this:



Yeah, but but the previous code was simply throwing the tag away on 
SKIP_PAGE (at least for non-TCF tags), and I didn't want to dig to find out 
if it was doing it for a reason (especially since SKIP_PAGE happens almost 
never :).  I figured that if we're going to throw it away, we should at 
least call release on it first :).



   +if (!n.implementsTryCatchFinally()) {
   +
   +if (isPoolingEnabled) {
   +out.printin(n.getTagHandlerPoolName());
   +out.print(.reuse();
   +out.print(tagHandlerVar);
   +out.println(););
   +} else {
   +out.printin(tagHandlerVar);
   +out.println(.release(););
   +}
   +}


Jan



   if (isTagFile || isFragment) {
   out.printil(throw new SkipPageException(););
   } else {
   out.printil((methodNesting  0) ? return true; : 
return;);

   }
   out.popIndent();
  -
  +out.printil(});
   // Synchronize AT_BEGIN scripting variables
   syncScriptingVars(n, VariableInfo.AT_BEGIN);

  @@ -2317,6 +2321,9 @@
   out.print(.reuse();
   out.print(tagHandlerVar);
   out.println(););
  +} else {
  +out.printin(tagHandlerVar);
  +out.println(.release(););
   }

   if (n.implementsTryCatchFinally()) {




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







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: New tag ?

[Bill Barker]

- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, July 20, 2005 3:42 AM
Subject: New tag ?


Hi,

I think the APR capabilities that we added are now sufficiently stable
to warrant testing. If the other areas that saw changes recently
(clustering, JK) are ok too, then it could be a good idea to release a
new build.


JK should be fine.  I've been pretty careful with the changes.

It would be nice to fix BZ 35696 (since it's a spec issue).  I'll see if I
can get some time to look at it.

Rémy





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: New tag ?

[Bill Barker]

- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, July 20, 2005 2:47 PM
Subject: Re: New tag ?


Bill Barker wrote:
Hi,

I think the APR capabilities that we added are now sufficiently stable
to warrant testing. If the other areas that saw changes recently
(clustering, JK) are ok too, then it could be a good idea to release a
new build.

 JK should be fine.  I've been pretty careful with the changes.

I was referring to the NIO channel which is marked as experimental in
the changelog.

Well, it's still flakey on Windows ;-).  AFAIK the NIO channel only works
well on one (obsolete :) O/S.  I think experimental is still a good
description for it.  Since it needs to be explicitly enabled, it won't
affect the stability of JK for users that don't want to try it, and there is
no good reason to hold up a release just for it.


 It would be nice to fix BZ 35696 (since it's a spec issue).  I'll see if
I
 can get some time to look at it.

Ok.

Rémy




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: Support JSS in Tomcat

[Bill Barker]

The Factory element is deprecated in TC 5.x.  In particular, you can't use
it to specify a SocketFactory.

You pass the FQN of your SSLImplementation to the Connector with something
like:
  Connector protocol=HTTP/1.1 port=8443 secure=true scheme=https
sslProtocol=SSL

sSLImplementation=org.apache.tomcat.util.net.jss.JSSImplementationClass /

I'd be happy to review your implementation (assuming that the licensing is
compatible with ASF) if you want to submit it.  The easiest way is to open a
BZ enhancement request and attach your code to that.

- Original Message -
From: Christine Ho [EMAIL PROTECTED]
To: tomcat-dev@jakarta.apache.org
Sent: Wednesday, July 20, 2005 4:54 PM
Subject: Support JSS in Tomcat


Hi,
  Tomcat 5.5.x supports JSSE only. I am working on web
application which uses JSS
(http://www.mozilla.org/projects/security/pki/jss/javadoc/)
I need to run the web application on Tomcat 5.x. I
implemented the JSSSocketFactory.java, JSSSupport.java
etc in the new package called
org.apache.tomcat.util.net.jss. I tried to specify the
SocketFactory class in server.xml but it doesnt work.
I thought we can do something like that:

Connector
className=org.apache.catalina.connector.http.HttpConnector
   port=8443 minProcessors=5
maxProcessors=75
   enableLookups=true
   acceptCount=10 debug=0 scheme=https
secure=true
  Factory
className=org.apache.tomcat.util.net.jss.JSSServerSocketFactory
   clientAuth=false protocol=SSL/
/Connector

It doesnt work at all. I looked at the source code and
found out that SSLImplementationName is always null.
Currently, I have to change the implementations array
in SSLImplementation.java to include my implementation
class which is JSSImplementationClass. Then recompiled
the tomcat and it works. I just wonder if I overlook
some of the configuration parameters in server.xml. If
the server.xml in tomcat 5.5 does not support the
Factory parameter, then I would like to modify the
codes to support this feature. Therefore i dont need
to recompile the tomcat to include my
SSLServerSocketFactory implementation. Also I would
like to contribute my codes for the JSS
ServerSocketFactory implementation if you are
interested.

Christine




Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs


-
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: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow

[Bill Barker]

Collin McClendon [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 I've enabled the logging per your suggestions, and not having heard back 
 in a bit, I was hoping someone could clue in to why I get plenty of FINE 
 messages for org.apache.jk.common.MsgAjp,  but no  longer get SEVERE 
 messages.  I'm also trying consistently crash mod_jk, but not having much 
 luck, OpenCMS is the webapp invovled here, I haven't gotten any feed back 
 from their dev list.

You get plenty of FINE messages, since those are primarily for developers 
trying to understand the protocol traffic ;-).  You haven't gotten SEVERE 
messages for the simple reason that none of them have been triggered.  (as 
an aside, MsgAjp only currently logs at either SEVERE or FINE).

As Remy mentions below, the most likely problems are with a 'Set-Cookie' 
header (with a ridiculously big cookie), or with a 'Location' header (from a 
sendRedirect with a ridiculously big query-string).  Personally, I'm betting 
on the second (since the Response body was less than 8K).  In any case, this 
is starting to border on [OT] for this list, and may be better continued on 
[EMAIL PROTECTED]  Don't worry, both Remy an me lurk there 
;-).

 Thanks,
 Collin


 Remy Maucherat wrote:

 Bill Barker wrote:

 The message is simply that you have a header value that is too big for 
 the
 AJP/1.3 protocol to handle.  If you enable DEBUG logging for
 org.apache.jk.common.MsgAjp, you should get a dump of the partial data 
 that
 should include the name of the bad header.


 Given the line, it could be a monster header value, possibly a cookie 
 (the size is 18KB, which is way over the AJP/1.3 capabilities).

 Rémy (with the neophyte AJP developer hat on)

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


 -- 
 Collin McClendon
 Sr. Microsoft Systems Engineer
 Digicon Corporation
 [EMAIL PROTECTED] 




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

Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow (logging)

[Bill Barker]

That's for log4j.   For Juli, you want FINE (or FINEST).

- Original Message -
From: Collin McClendon [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, July 13, 2005 8:15 AM
Subject: Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow (logging)


Bill,
Thanks again for this tip. After reading the document to my best
ability, I added this line to the end of
/usr/local/tomcat/common/classes/logging.propeties :
org.apache.jk.common.MsgAjp = ALL
I got as a result what seemed like no logging at all for this class.
I am setting it to DEBUG now to see what happens, but am I doing this
correctly at all?
Thanks for your help,
Collin


Bill Barker wrote:

http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html

- Original Message -
From: Collin McClendon [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Tuesday, July 12, 2005 10:57 AM
Subject: Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow


Thanks so much for replying! I can understand that concept. Given that
we are using mod_jk to connect the Apache frontend to Tomcat running
OpenCMS on the backend, perhaps the way that the application is working
that is giving us this result?  Also in response to Bill, where can one
turn on
DEBUG logging for a specific class such as

org.apache.jk.common.MsgAjp


?

I'm thinking that would be in one of the xml config files and I will do
more research on that, but if you had a quick answer, I'd be happy to
hear it.
On the suggestion of Mladen Turk, I did upgrade to mod_jk 1.2.14, I hope
to see some difference there.
Thanks again,
Collin

Remy Maucherat wrote:



Bill Barker wrote:



The message is simply that you have a header value that is too big
for the
AJP/1.3 protocol to handle.  If you enable DEBUG logging for
org.apache.jk.common.MsgAjp, you should get a dump of the partial
data that
should include the name of the bad header.


Given the line, it could be a monster header value, possibly a cookie
(the size is 18KB, which is way over the AJP/1.3 capabilities).

Rémy (with the neophyte AJP developer hat on)

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




--
Collin McClendon
Sr. Microsoft Systems Engineer
Digicon, Inc.
[EMAIL PROTECTED]


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




--
Collin McClendon
Sr. Microsoft Systems Engineer
Digicon Corporation
[EMAIL PROTECTED]


-
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: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow

[Bill Barker]

The message is simply that you have a header value that is too big for the
AJP/1.3 protocol to handle.  If you enable DEBUG logging for
org.apache.jk.common.MsgAjp, you should get a dump of the partial data that
should include the name of the bad header.

- Original Message -
From: Collin McClendon [EMAIL PROTECTED]
To: tomcat-dev@jakarta.apache.org
Sent: Tuesday, July 12, 2005 9:38 AM
Subject: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow


 Hello all,
 I was kindly redirected to this list by Mr. Turk, the author of mod_jk.
 He suggested that someone here might be able to determine
 why when using mod_jk and tomcat and apache, I am getting buffer
 overflow messages in the catalina.out logfile.  This tends to
 happen after 8 hours or so, and after users have been visiting the
 website, not when idle. I have the relevant portion of the log here:
 My mod_jk as stated is 1.2.10, tomcat is 5.5.9, and apache is 2.0.52-12
 (RedHat 4.0ES build).

 SEVERE: Buffer overflow: buffer.len=8192 pos=70 data=18568
 Jun 28, 2005 6:16:21 PM org.apache.jk.common.MsgAjp cpBytes
 SEVERE: Overflow
 java.lang.Throwable
 at org.apache.jk.common.MsgAjp.cpBytes(MsgAjp.java:172)
 at org.apache.jk.common.MsgAjp.appendByteChunk(MsgAjp.java:146)
 at org.apache.jk.common.MsgAjp.appendBytes(MsgAjp.java:132)
 at
 org.apache.jk.server.JkCoyoteHandler.appendHead(JkCoyoteHandler.java:407)
 at
 org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:425)
 at org.apache.coyote.Response.action(Response.java:182)
 at org.apache.coyote.Response.sendHeaders(Response.java:374)
 at
 org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:317)
 at
 org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278)
 at
 org.apache.catalina.connector.Response.finishResponse(Response.java:473)
 at

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
 at
 org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307)
 at
 org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385)
 at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)
 at

org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)
 at
 org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)
 at

org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
 at java.lang.Thread.run(Thread.java:595)

 I'd appreciate any help you can offer,
 Thank you,
 Collin McClendon

 --
 Collin McClendon
 Sr. Microsoft Systems Engineer
 Digicon, Inc.
 [EMAIL PROTECTED]


 -
 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: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow

[Bill Barker]

http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html

- Original Message -
From: Collin McClendon [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Tuesday, July 12, 2005 10:57 AM
Subject: Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow


Thanks so much for replying! I can understand that concept. Given that
we are using mod_jk to connect the Apache frontend to Tomcat running
OpenCMS on the backend, perhaps the way that the application is working
that is giving us this result?  Also in response to Bill, where can one
turn on
DEBUG logging for a specific class such as

org.apache.jk.common.MsgAjp


?

I'm thinking that would be in one of the xml config files and I will do
more research on that, but if you had a quick answer, I'd be happy to
hear it.
On the suggestion of Mladen Turk, I did upgrade to mod_jk 1.2.14, I hope
to see some difference there.
Thanks again,
Collin

Remy Maucherat wrote:

 Bill Barker wrote:

 The message is simply that you have a header value that is too big
 for the
 AJP/1.3 protocol to handle.  If you enable DEBUG logging for
 org.apache.jk.common.MsgAjp, you should get a dump of the partial
 data that
 should include the name of the bad header.


 Given the line, it could be a monster header value, possibly a cookie
 (the size is 18KB, which is way over the AJP/1.3 capabilities).

 Rémy (with the neophyte AJP developer hat on)

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


--
Collin McClendon
Sr. Microsoft Systems Engineer
Digicon, Inc.
[EMAIL PROTECTED]


-
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: JK 1.2.14 core dump oddity

[Bill Barker]

- Original Message -
From: William A. Rowe, Jr. [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Tuesday, July 12, 2005 12:52 PM
Subject: JK 1.2.14 core dump oddity


 Something's not quite right in mod_jk-land.  The pertinent httpd.conf is;

 ErrorDocument 404 /examplestomcat/error.jsp

 Alias /examplestomcat /local0/test/webapps/examplestomcat

 JkMount /examplestomcat/*.jsp ajp13

 when the 404 causes error.jsp to be returned, the response code
 is unset from 404 to 200-ok.  This behavior is not a regression,
 seems it's been that way for a long (1.2.8 or earlier) time.


It goes back at least to 1.1.x.

 Line 1971 of jk/native/apache-2.0/mod_jk.c says...

 return OK;  /* NOT r-status, even if it has changed. */

 This goes back to version 1.1 of the module; the question is; WHY?


You're the httpd expert, not me ;-).

As I understand it, it is to have httpd return the Tomcat response code
(which won't be 404 unless error.jsp explictly sets it to that).

 Bill

 Bill


 -
 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: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkMain.java

[Bill Barker]

- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, June 30, 2005 3:39 AM
Subject: Re: cvs commit: 
jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkMain.java




[EMAIL PROTECTED] wrote:

billbarker2005/06/29 19:49:38

With a 16K bufferSize, the APR connector is no longer the clear
winner in performance.  For BC, it's currently disabled by default,
but it's easy enough to change that after some more testing.


Yes, I can see performance is better too. It's also possible that taking 
the APR code, and rewriting it with regular Java IO would also yield 
slightly better results (regular HTTP is still a little faster than APR 
HTTP - some VMs make the difference very small, but the VM I use for 
testing is definitely not the best for JNI).


Actually, on Solaris the big winner is ChannelNioSocket.  It wins the 
performance race easily now.  Too bad that NIO on Windows s*cks.  I guess 
that JFA was right, and non-blocking sockets is the way to go.




Now that I've looked at it a lot, however, I dislike the Java AJP impl, as 
it's way overengineered in comparison to what it required by the current 
Tomcat.


Hey, I like the overengineering ;-).  Yeah, Costin got a little ambitious 
here before deciding to just use Coyote.  On the other hand, when Mladen 
wants you to implement unix sockets for AJP/APR, ChannelUn is going to start 
to look good ;-).




Rémy





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: Tomcat native WIN32 binaries

[Bill Barker]

It looks like people.apache.org is still hosted in the US, so providing 
ssleay32.dll from there is likely to put the ASF in trouble with US crypto 
export restrictions.

Mladen Turk [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 Hi,

 If someone wishes to test the bleeding edge Tomcat Native,
 the WIN32 binaries can be found at:

 http://people.apache.org/~mturk/native/

 I'll try to keep those up to date until we figure out the
 binary distribution mode.

 Regards,
 Mladen. 




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

Re: HEAD build failed

[Bill Barker]

- Original Message - 
From: Mladen Turk [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Saturday, June 18, 2005 3:41 AM
Subject: HEAD build failed



Anyone has any idea why I'm getting the following error when doing:
'ant download'



You're using a broken version of Ant.  You need to upgrade (or downgrade) to 
a version that works.




build-tomcat-dbcp:

-build-tomcat-dbcp:

BUILD FAILED
C:\W\projects\tomcat\jakarta-tomcat-5\build.xml:1895: The following error 
occurred while executing this line:
C:\W\projects\tomcat\jakarta-tomcat-5\build.xml:671: The following error 
occurred while executing this line:
C:\W\projects\tomcat\jakarta-tomcat-5\build.xml:683: The following error 
occurred while executing this line:
C:\W\projects\tomcat\jakarta-tomcat-5\build.xml:718: Cannot replace 
directory 
C:\W\projects\tomcat\repository\tomcat-deps\src\java\org\apache\tomcat\dbcp 
with directory 
C:\W\projects\tomcat\repository\tomcat-deps\src\java\org\apache\commons



Any clues.

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 6 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 48 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/common'
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_connect.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_msg_buff.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_util.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_pool.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_worker.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13_worker.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 6 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 48 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/common'
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_connect.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_msg_buff.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_util.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_pool.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_worker.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp13_worker.c 
mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15062005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15062005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-15062005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 

Re: [EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

- Original Message -
From: jean-frederic clere [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, June 15, 2005 5:05 AM
Subject: Re: [EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module
jakarta-tomcat-connectors) failed


 Bill Barker wrote:
  To whom it may engage...
 

 I think I have fixed this one in rules.mk


Doesn't seem to have worked.  The error is still the same.

 -
 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: [EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

- Original Message -
From: Bill Barker [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, June 15, 2005 10:17 AM
Subject: Re: [EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module
jakarta-tomcat-connectors) failed



 - Original Message -
 From: jean-frederic clere [EMAIL PROTECTED]
 To: Tomcat Developers List tomcat-dev@jakarta.apache.org
 Sent: Wednesday, June 15, 2005 5:05 AM
 Subject: Re: [EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module
 jakarta-tomcat-connectors) failed


  Bill Barker wrote:
   To whom it may engage...
  
 
  I think I have fixed this one in rules.mk
 

 Doesn't seem to have worked.  The error is still the same.


Ok, it seems that `apxs -q LIBTOOL` is broken again over in httpd land :(.

I guess I'll have to reopen BZ #32787, attach this patch, and wait another
another six months to get the patch applied.

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




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.

*** config_vars.sh.in.orig  Wed Jun 15 15:35:10 2005
--- config_vars.sh.in   Wed Jun 15 15:35:41 2005
***
*** 60,64 
  /^UTIL_LDFLAGS/d
  /^APR_INCLUDEDIR.*$/s,.*,APR_INCLUDEDIR = ${APR_INCLUDEDIR},
  /^APU_INCLUDEDIR.*$/s,.*,APU_INCLUDEDIR = ${APU_INCLUDEDIR},
! /^LIBTOOL.*$/s,/[^ ]*/libtool \(.*\),${APR_LIBTOOL} \$(LTFLAGS),
  
--- 60,64 
  /^UTIL_LDFLAGS/d
  /^APR_INCLUDEDIR.*$/s,.*,APR_INCLUDEDIR = ${APR_INCLUDEDIR},
  /^APU_INCLUDEDIR.*$/s,.*,APU_INCLUDEDIR = ${APU_INCLUDEDIR},
! /^LIBTOOL.*$/s,/[^ ]*/libtool \(.*\),${APR_LIBTOOL} @LTFLAGS@,
  

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

Re: AJP using APR

[Bill Barker]

- Original Message - 
From: Costin Manolache [EMAIL PROTECTED]

To: tomcat-dev@jakarta.apache.org
Sent: Sunday, June 12, 2005 5:31 PM
Subject: Re: AJP using APR



Bill Barker wrote:
Costin Manolache [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]



Bill Barker wrote:

If I understand you correctly, you want MsgAjp to use ByteBuffer instead 
of byte [].  At the cost of never supporting JDK 1.3 ever again, this 
would probably actually improve the performance of ChannelSocket (after 
changing it to use a blocking SocketChannel).


The biggest difference will be if it's a 'direct' buffer, i.e. zero copy. 
Classpath ( gcj, kaffe, etc ) also has byte buffer support - so it should 
be ok, if anyone needs jdk1.3, they can use the old code.





Yes, the idea was that it would be a direct buffer.



But where is the code ?




It's on my hard-drive.  Unlike Remy's APR stuff, o.a.jk is supposed to be 
a pretty stable package(s) at this point.  I can't just check in stuff 
like this without a lot of testing to make sure that it doesn't break 
anything more than JDK 1.3 compatibility ;-).


That's why C has conditional compilation - and java has some 
options-controlled ugly 'if' code :-) It doesn't break anything if the 
option/def is not selected ( just makes the code a bit uglier ). This way 
even JDK1.3 will be happy.




Yeah, well, I hate ugly ;-).  Using NIO will be switchable (and off by 
default for BC for now).  Mark says he doesn't want to use j-t-c HEAD for 
4.1.x, and if there is ever another 3.3 release, I'll just add a comment 
that using the Coyote-JK connector requires JDK 1.4 (similar to the one for 
the HTTP/1.1 connector).  The old AJP connector works well enough in 3.3.


I've been spending the weekend fighting with APR-1, that doesn't want to use 
the OpenSSL .a files.  At this point, I'm probably just going to admit 
defeat.  It's a test box, so I can simply install a test-version of the 
OpenSSL .so files and link against that.  It's sad that the libtool from 
httpd-2.0.50 works fine with the .a files :(, but APR-1 doesn't.




The biggest problem in JNI ( and probably - in Java playing nice with other 
languages and the rest of the platform ) is the objects and buffers moving 
around almost randomly. Yes, it may improve a bit the garbage collection 
speed - so people can create millions of garbage objects without thinking 
about it, unlike most other languages that require you to think when 
allocating objects - but it is the kind of optimization that has disastrous 
consequences on the rest of the systems. Luckily gcj and kaffe and mono 
don't do this crazy thing.

Direct buffers is one band-aid that should be used whenever possible.



Fortunately, this is Remy's problem ;-).


Costin





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]

Building question

[Bill Barker]

I just tried to build a fresh copy of j-t-c/jni/native on my Solaris7 box, 
and it fails miserably ;-).  It looks like it needs to include -fpic, but I 
can't see how to do it (CFLAGS doesn't work).


The OpenSSL libraries are libssl.a and libcrypto.a.  With the pathetic 
security performance of OpenSSL, I wouldn't trust it any other way ;-). 




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: AJP using APR

[Bill Barker]

Costin Manolache [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 Bill Barker wrote:

 If I understand you correctly, you want MsgAjp to use ByteBuffer instead 
 of byte [].  At the cost of never supporting JDK 1.3 ever again, this 
 would probably actually improve the performance of ChannelSocket (after 
 changing it to use a blocking SocketChannel).

 The biggest difference will be if it's a 'direct' buffer, i.e. zero copy. 
 Classpath ( gcj, kaffe, etc ) also has byte buffer support - so it should 
 be ok, if anyone needs jdk1.3, they can use the old code.


Yes, the idea was that it would be a direct buffer.


 But where is the code ?


It's on my hard-drive.  Unlike Remy's APR stuff, o.a.jk is supposed to be a 
pretty stable package(s) at this point.  I can't just check in stuff like 
this without a lot of testing to make sure that it doesn't break anything 
more than JDK 1.3 compatibility ;-).

 Costin




 Rémy




 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] 




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

Re: cvs commit: jakarta-tomcat-connectors/jni/native/src ssl.c sslcontext.c

[Bill Barker]

- Original Message - 
From: jean-frederic clere [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, June 09, 2005 12:20 AM
Subject: Re: cvs commit: jakarta-tomcat-connectors/jni/native/src ssl.c 
sslcontext.c




[EMAIL PROTECTED] wrote:

jfclere 2005/06/08 09:52:58

  Modified:jni/examples/org/apache/tomcat/jni SSLServer.java
   jni/java/org/apache/tomcat/jni BIOCallback.java SSL.java
SSLContext.java
   jni/native/src ssl.c sslcontext.c
  Log:
  Change the BIOCallback interface to use write(byte[] buf) and
  read(byte[] buf);
  Add SSL_accept to do the client handshake.
  Arrange the corresponding example.



+++ CUT +++

Hi,

I am not 100% happy with the code. Mladen already asked me to rollback the 
changes. I think the worst thing is setSock() I have added to BIOCallback.
My idea is/was to use BIOCallback or a similar interface to be able to 
openssl either with normal JAVA sockets or APR native ones.


Comments?



It looked OK to me.  Basically it's the APR implementation of SSLEngine. 
Don't really see a problem.


Of course, I don't really care about the APR-SSL Connector one way or the 
other.  Since the config is the same as for mod_ssl, there is absolutely no 
reason to not simply use mod_ssl instead.  If I just wanted the native-code 
optimizations, I'd use PureTLS instead.



Cheers

Jean-Frederic

-
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: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/coyote/ajp AjpAprProcessor.java Constants.java LocalStrings.properties AjpAprProtocol.java AjpMessage.java

[Bill Barker]

- Original Message - 
From: [EMAIL PROTECTED]

To: [EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 9:14 AM
Subject: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/coyote/ajp 
AjpAprProcessor.java Constants.java LocalStrings.properties 
AjpAprProtocol.java AjpMessage.java




remm2005/06/09 09:14:51

 Added:   jk/java/org/apache/coyote/ajp AjpAprProcessor.java
   Constants.java LocalStrings.properties
   AjpAprProtocol.java AjpMessage.java
 Log:
 - Add my WIP AJP implementation using APR. Performance sucks right now,
   and I think it has lots of bugs ;)
 - It won't be compiled in or used for now.



Yeah, it has a few bugs ;).  Would it mess you up if I were to fix some of 
the more glaring ones in the CVS copy?  I'm thinking mostly of the double 
call to endRequest, and the failure to clean up the Request body parameters. 
The handling of remote/localHost/Port is also wrong, but relatively 
harmless.  Also the lack of C2B handling on the Response headers is going to 
bite you someday, but for initial testing on a iso-8859-1 machine it's 
alright.





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: AJP using APR

[Bill Barker]

- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Tuesday, June 07, 2005 8:42 AM
Subject: AJP using APR



Hi,

I'd like to add my WIP code for AJP based on APR. It's not done yet, but it 
would be convinient to have the code there, just in case. It won't be 
compiled in or used (even if APR is available) for now, to avoid possible 
problems.




So, where is it already?  Some of use want to see how you can beat Costin 
;-).


I used the package org.apache.coyote.ajp for it, and it reuses most of the 
message code, parsing and composition from regular AJP. One of the issues 
I'm facing, however, is that the usage of JNI will make the current code 
subpar, where it would be a lot better to do message reading and writing 
(this means composition of the messages to avoid useless bytes copying) 
using direct buffers. So there's a lot of work left, and it will remain 
experimental for a little while.




If I understand you correctly, you want MsgAjp to use ByteBuffer instead of 
byte [].  At the cost of never supporting JDK 1.3 ever again, this would 
probably actually improve the performance of ChannelSocket (after changing 
it to use a blocking SocketChannel).



Rémy




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]

[EMAIL PROTECTED]: Project jakarta-tomcat-jni (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jni has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jni :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-native-07062005.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Circular Dependency with ant.
 -ERROR- Circular Dependency with commons-logging.
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #21.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jni (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jni has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jni :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-native-07062005.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Circular Dependency with ant.
 -ERROR- Circular Dependency with commons-logging.
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #21.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-util (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-util has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-util :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-util/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-util.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Circular Dependency with ant.
 -ERROR- Circular Dependency with xml-xerces.
 -ERROR- Circular Dependency with xml-apis.
 -ERROR- Circular Dependency with jsse.
 -ERROR- Circular Dependency with jmx.
 -ERROR- Circular Dependency with commons-logging.
 -DEBUG- Dependency on jmx exists, no need to add for property jmx.home.
 -DEBUG- Dependency on jsse exists, no need to add for property jsse.home.
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-util/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-util/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #50.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-util (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-util has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-util :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-util/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-util.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Circular Dependency with ant.
 -ERROR- Circular Dependency with xml-xerces.
 -ERROR- Circular Dependency with xml-apis.
 -ERROR- Circular Dependency with jsse.
 -ERROR- Circular Dependency with jmx.
 -ERROR- Circular Dependency with commons-logging.
 -DEBUG- Dependency on jmx exists, no need to add for property jmx.home.
 -DEBUG- Dependency on jsse exists, no need to add for property jsse.home.
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-util/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-util/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #50.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-coyote (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-coyote has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-coyote :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-coyote.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Circular Dependency with ant.
 -ERROR- Circular Dependency with jakarta-tomcat-util.
 -ERROR- Circular Dependency with commons-logging.
 -ERROR- Circular Dependency with jmx.
 -ERROR- Circular Dependency with jmx.
 -DEBUG- Dependency on jakarta-tomcat-util exists, no need to add for property 
util.home.
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #65.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-coyote (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-coyote has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-coyote :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-coyote.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Circular Dependency with ant.
 -ERROR- Circular Dependency with jakarta-tomcat-util.
 -ERROR- Circular Dependency with commons-logging.
 -ERROR- Circular Dependency with jmx.
 -ERROR- Circular Dependency with jmx.
 -DEBUG- Dependency on jakarta-tomcat-util exists, no need to add for property 
util.home.
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #65.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-coyote-tomcat4 (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-coyote-tomcat4 has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-coyote-tomcat4 :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote-tomcat4/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat4-coyote.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Circular Dependency with ant.
 -ERROR- Circular Dependency with jmx.
 -ERROR- Circular Dependency with commons-modeler.
 -ERROR- Circular Dependency with commons-logging.
 -ERROR- Circular Dependency with jakarta-tomcat-util.
 -ERROR- Circular Dependency with jakarta-servletapi-4.
 -DEBUG- Dependency on tomcat-catalina exists, no need to add for property 
catalina.home.
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote-tomcat4/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote-tomcat4/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #110.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-coyote-tomcat4 (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-coyote-tomcat4 has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-coyote-tomcat4 :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote-tomcat4/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat4-coyote.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Circular Dependency with ant.
 -ERROR- Circular Dependency with jmx.
 -ERROR- Circular Dependency with commons-modeler.
 -ERROR- Circular Dependency with commons-logging.
 -ERROR- Circular Dependency with jakarta-tomcat-util.
 -ERROR- Circular Dependency with jakarta-servletapi-4.
 -DEBUG- Dependency on tomcat-catalina exists, no need to add for property 
catalina.home.
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote-tomcat4/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-coyote-tomcat4/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #110.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-http11 (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-http11 has an issue affecting its community integration.
This issue affects 3 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat :  Servlet 2.2 and JSP 1.1 Reference Implementation
- jakarta-tomcat-coyote-tomcat3 :  Connectors to various web servers
- jakarta-tomcat-http11 :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-http11.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-http11.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-http11 (Type: Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-modeler.jar=/usr/local/gump/public/workspace/jakarta-commons/modeler/dist/commons-modeler-07062005.jar
 -Djmx.jar=/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar 
-Dtomcat-jni.jar=/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jni/dist/tomcat-native-07062005.jar
 
-Dtomcat-coyote.jar=/usr/local/gump/public/workspace/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar
 
-Dtomcat-util.jar=/usr/local/gump/public/workspace/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar
 
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar
 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/http11]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:ant-jmf-gump-31052005.jar:ant-swing-gump-31052005.jar:ant-apache-resolver-gump-31052005.jar:ant-trax-gump-31052005.jar:ant-junit-gump-31052005.jar:ant-launcher-gump-31052005.jar:ant-nodeps-gump-31052005.jar:ant-gump-31052005.jar:junit-gump-31052005.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar:commons-modeler-gump-31052005.jar:jakarta-tomcat-coyote-gump-31052005.jar:jakarta-tomcat-util-gump-31052005.jar:commons-logging-api-gump-31052005.jar:jakarta-tomcat-jni-gump-31052005.jar
-
Exception in thread main java.lang.NoClassDefFoundError: 
org/apache/tools/ant/Main
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #186.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-http11 (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-http11 has an issue affecting its community integration.
This issue affects 3 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat :  Servlet 2.2 and JSP 1.1 Reference Implementation
- jakarta-tomcat-coyote-tomcat3 :  Connectors to various web servers
- jakarta-tomcat-http11 :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-http11.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-http11.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-http11 (Type: Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-modeler.jar=/usr/local/gump/public/workspace/jakarta-commons/modeler/dist/commons-modeler-07062005.jar
 -Djmx.jar=/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar 
-Dtomcat-jni.jar=/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jni/dist/tomcat-native-07062005.jar
 
-Dtomcat-coyote.jar=/usr/local/gump/public/workspace/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar
 
-Dtomcat-util.jar=/usr/local/gump/public/workspace/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar
 
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar
 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/http11]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:ant-jmf-gump-31052005.jar:ant-swing-gump-31052005.jar:ant-apache-resolver-gump-31052005.jar:ant-trax-gump-31052005.jar:ant-junit-gump-31052005.jar:ant-launcher-gump-31052005.jar:ant-nodeps-gump-31052005.jar:ant-gump-31052005.jar:junit-gump-31052005.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar:commons-modeler-gump-31052005.jar:jakarta-tomcat-coyote-gump-31052005.jar:jakarta-tomcat-util-gump-31052005.jar:commons-logging-api-gump-31052005.jar:jakarta-tomcat-jni-gump-31052005.jar
-
Exception in thread main java.lang.NoClassDefFoundError: 
org/apache/tools/ant/Main
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-http11/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 35331107062005, vmgump.apache.org:vmgump-public:35331107062005
Gump E-mail Identifier (unique within run) #186.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper HostMap.java Mapper.java

[Bill Barker]

- Original Message - 
From: George Sexton [EMAIL PROTECTED]

To: 'Tomcat Developers List' tomcat-dev@jakarta.apache.org
Sent: Sunday, June 05, 2005 8:53 AM
Subject: RE: cvs commit: 
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper 
HostMap.java Mapper.java








-Original Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 04, 2005 1:27 PM
To: Tomcat Developers List
Subject: Re: cvs commit:
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/htt
p/mapper HostMap.java Mapper.java


- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Saturday, June 04, 2005 10:29 AM
Subject: Re: cvs commit:
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/htt
p/mapper
HostMap.java Mapper.java


Peter Rossbach wrote:
 Hey Remy,

 For usefull feature I don't give up :-)

Fine, I'll just revert your patch then ;)

 The default of host alias matching is off. The current
implementation is
 little bit fast
 then the old one. (Great) Every user of this feature can limit the
 dynamic host addition with
 Connector port=8080 allowedAliasMatches=10 /

The issue is that this mechanism is bad, period.

I have to agree with Remy on this.  The issue is that the
code is just plain
bad :(.  So I'm going to add my -1 to the patch until the


There's no justification here. Explain why you think the code is bad 
it's

actually a hell of a lot cleaner and easier to follow than the original
code, and it's 15% faster. What exactly are your criteria for measuring
goodness.



Well, the gratuitous cloning of the HostMap is bad for one.  It looks like 
an attempt to avoid a sync in a non-critial path, but of course it can't 
possibly work.


Before I could move to +1, the code would have to be (like Remy says) a lot 
more generic.  Especially with pre-compiled JSPs, there are a lot of cases 
where you'd get a lot more bang doing this type of optimization for 
servlet-mappings than for Hosts.





mechanism is
cleaned up.  In fact, I'd have -1ed it just for the import
com.sun.
line alone.



I don't know what you are looking at. My submission had NO com.sun.xxx 
class

imports.



I'm looking at the commit message, obviously.  That's what we are voting on 
;-).



Perhaps you missed the thread where I said I rewrote it?

http://www.mhsoftware.com/~gsexton/HostMap.java
http://www.mhsoftware.com/~gsexton/Mapper.java

If you are going to -1 some code, you should at least look at it.


George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585


-
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: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper HostMap.java Mapper.java

[Bill Barker]

- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Saturday, June 04, 2005 10:29 AM
Subject: Re: cvs commit: 
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper 
HostMap.java Mapper.java




Peter Rossbach wrote:

Hey Remy,

For usefull feature I don't give up :-)


Fine, I'll just revert your patch then ;)

The default of host alias matching is off. The current implementation is 
little bit fast
then the old one. (Great) Every user of this feature can limit the 
dynamic host addition with

Connector port=8080 allowedAliasMatches=10 /


The issue is that this mechanism is bad, period.


I have to agree with Remy on this.  The issue is that the code is just plain 
bad :(.  So I'm going to add my -1 to the patch until the mechanism is 
cleaned up.  In fact, I'd have -1ed it just for the import com.sun. 
line alone.




The wild card alias usage is very useful for tomcat hoster. Now the 
customer can use
a new host subdomain without change the server.xml. Very nice and the 
admin must do nothing.


And the usefulness of that is non existent as well. What's the purpose of 
adding hosts if they are all the same ?



simple add first time Alias*.mydomain.net/Alias  to your host.

+1 vote for this feature.


-1 vote for this feature.

Rémy






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: WebappLoader and Auto-Detection of Class Changes

[Bill Barker]

- Original Message -
From: Scott Dudley [EMAIL PROTECTED]
To: tomcat-dev@jakarta.apache.org
Sent: Friday, June 03, 2005 12:46 PM
Subject: WebappLoader and Auto-Detection of Class Changes



 I extended WebappLoader.java to create a custom classloader to allow me
 to append an alternate set of class folders.  The loader works as
 intended but I noted that it doesn't detect any changes to these
 resources and call Context.reload() as is the case with WEB-INF/classes,
 lib, and any WatchedResource entries.  What am I missing.  Looking at
 WebappLoader.java and I fail to notice the mechanism which provides said
 functionality.

 Can someone point me in the right direction?


Look at WebappLoader.modified.  That determines if the app should be
reloaded.

 Many thanks.

 --

 Regards,

 Scott Dudley


 -
 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: Initial apr results

[Bill Barker]

You might also want to dig up Peter's JMeter test plan.  This one is the 
opposite of the 'ab' test, in that it tests the ability to handle a lot of 
socket connections without necessarily much throughput.


As Remy said, the 'ab -k' tests should be close unless either your JVM 
vendor or your APR implementation s*cks.  Both connectors do much the same 
thing with this test execpt for sendfile (and 'tomcat.gif' is too small to 
for Tomcat to use sendfile by default).


- Original Message - 
From: Tim Funk [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, June 02, 2005 3:41 AM
Subject: Re: Initial apr results


Excellent. In my future tests, I'll keep the concurrency lower and the 
hits higher. I'll also use different size files. I am only able to use a 
1.4.2 JVM. I might be able to get 1.5 on - but its highly doubtful.


-Tim

Remy Maucherat wrote:

Tim Funk wrote:


My test box was an HP-UX 9000/800/L1000-44 - Dual CPU (440 MHz)

On my initial tests with the APR connector - the APR connector seemed 
slower the old http connector. But the difference is mild and my 
initial numbers are flaky. On the same hardware - I am running 6 other 
instances (of different versions) of tomcat at the same time which may 
be throwing my numbers off.


During some slow time - I might be able to take most of them down and 
run some more tests to try to ensure I am hogging all the resources to 
the box and not sharing them.


For those curious - for /tomcat.gif - my requests per second range 
anywhere from 1200+ to 5000+ - Due to such a large range - I have no 
confidence in my numbers so far to reach any conclusion.


I was using the command:
 /usr/local/httpd/bin/ab -n 1000 -c 100 -k 
http://myserver:8090/tomcat.gif


With keepalive off - I was still easily over 1000 requests per second 
for tomcat.gif.



I can't assert yet that there are no bugs at the moment (performance or 
otherwise). So far, performance seems good on Windows, and Linux. To give 
a comparison on Windows with this test, APR HTTP is within 5% of regular 
HTTP, and gets closer depending on the JVM (I suppose if it's better at 
JNI - I've noticed slightly better results with Sun JDK 1.5 Server 
compared to 1.4.2 client).


I think you should use -n 2 at least: if the test duration is too 
small, ab is going to produce random results. In this test, increasing 
concurrency isn't particularly useful either.


Obviously, the results of this kind of testing are not really important 
as long as the results stay relatively close (for example, I think 
the -25% result I got when using polling exclusively was really good).




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

[EMAIL PROTECTED]: Project jakarta-tomcat-jni (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jni has an issue affecting its community integration.
This issue affects 36 projects,
 and has been outstanding for 19 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- avalon-http-context :  Avalon SVN
- avalon-http-demo :  Avalon SVN
- avalon-http-examples :  Avalon SVN
- avalon-http-impl :  Avalon SVN
- avalon-http-server :  Avalon SVN
- avalon-http-servlet :  Avalon SVN
- avalon-http-static :  Avalon SVN
- avalon-http-test :  Avalon SVN
- avalon-planet-facilities :  Avalon SVN
- cargo :  Cargo provides a Java API to manipulate Java Containers
- jakarta-cactus-documentation :  Cactus Documentation
- jakarta-cactus-integration-ant-12 :  Cactus Ant Integration (J2EE 1.2)
- jakarta-cactus-integration-ant-13 :  Cactus Ant Integration (J2EE 1.3)
- jakarta-cactus-release-12 :  Unit test framework for server-side java code
- jakarta-cactus-release-13 :  Unit test framework for server-side java code
- jakarta-cactus-sample-jetty-13 :  Cactus Jetty Sample (J2EE 1.3)
- jakarta-cactus-sample-servlet-12 :  Cactus Servlet Sample (J2EE 1.2)
- jakarta-cactus-sample-servlet-13 :  Cactus Servlet Sample (J2EE 1.3)
- jakarta-tomcat :  Servlet 2.2 and JSP 1.1 Reference Implementation
- jakarta-tomcat-4.0 :  Servlet 2.3 and JSP 1.2 Reference Implementation
- jakarta-tomcat-5 :  Servlet 2.4 and JSP 2.0 Reference Implementation
- jakarta-tomcat-catalina :  Servlet 2.4 Reference Implementation
- jakarta-tomcat-coyote :  Connectors to various web servers
- jakarta-tomcat-coyote-tomcat3 :  Connectors to various web servers
- jakarta-tomcat-coyote-tomcat4 :  Connectors to various web servers
- jakarta-tomcat-http11 :  Connectors to various web servers
- jakarta-tomcat-jk :  Connectors to various web servers
- jakarta-tomcat-jni :  Connectors to various web servers
- jakarta-tomcat-util :  Connectors to various web servers
- jakarta-turbine-jcs :  Cache
- metro-reflector-blocks-complete :  Avalon SVN
- struts-sslext :  The Struts SSL Extension for HTTP/HTTPS switching
- struts-taglib :  Model 2 Model-View-Controller framework for Servlets and 
JSP
- struts-taglib-from-packages :  Model 2 Model-View-Controller framework 
for Servlets and JSP
- strutstestcase :  An extension of the standard JUnit TestCase class that 
provi...
- tomcat-catalina :  Servlet 2.3 and JSP 1.2 Reference Implementation


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-native-01062005.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jni.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jni (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar
 -Dversion=01062005 jar 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jni]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jni/dist/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar
-
Buildfile: build.xml

env:
 [echo] java.home = /x1/opt/__versions__/j2sdk1.4.2_08/jre
 [echo] user.home = /home/gump
 [echo] tc.library.path = 
/x1/gump/public/workspace/jakarta-tomcat-connectors/jni/native/.libs


prepare:
 

[EMAIL PROTECTED]: Project jakarta-tomcat-jni (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jni has an issue affecting its community integration.
This issue affects 36 projects,
 and has been outstanding for 19 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- avalon-http-context :  Avalon SVN
- avalon-http-demo :  Avalon SVN
- avalon-http-examples :  Avalon SVN
- avalon-http-impl :  Avalon SVN
- avalon-http-server :  Avalon SVN
- avalon-http-servlet :  Avalon SVN
- avalon-http-static :  Avalon SVN
- avalon-http-test :  Avalon SVN
- avalon-planet-facilities :  Avalon SVN
- cargo :  Cargo provides a Java API to manipulate Java Containers
- jakarta-cactus-documentation :  Cactus Documentation
- jakarta-cactus-integration-ant-12 :  Cactus Ant Integration (J2EE 1.2)
- jakarta-cactus-integration-ant-13 :  Cactus Ant Integration (J2EE 1.3)
- jakarta-cactus-release-12 :  Unit test framework for server-side java code
- jakarta-cactus-release-13 :  Unit test framework for server-side java code
- jakarta-cactus-sample-jetty-13 :  Cactus Jetty Sample (J2EE 1.3)
- jakarta-cactus-sample-servlet-12 :  Cactus Servlet Sample (J2EE 1.2)
- jakarta-cactus-sample-servlet-13 :  Cactus Servlet Sample (J2EE 1.3)
- jakarta-tomcat :  Servlet 2.2 and JSP 1.1 Reference Implementation
- jakarta-tomcat-4.0 :  Servlet 2.3 and JSP 1.2 Reference Implementation
- jakarta-tomcat-5 :  Servlet 2.4 and JSP 2.0 Reference Implementation
- jakarta-tomcat-catalina :  Servlet 2.4 Reference Implementation
- jakarta-tomcat-coyote :  Connectors to various web servers
- jakarta-tomcat-coyote-tomcat3 :  Connectors to various web servers
- jakarta-tomcat-coyote-tomcat4 :  Connectors to various web servers
- jakarta-tomcat-http11 :  Connectors to various web servers
- jakarta-tomcat-jk :  Connectors to various web servers
- jakarta-tomcat-jni :  Connectors to various web servers
- jakarta-tomcat-util :  Connectors to various web servers
- jakarta-turbine-jcs :  Cache
- metro-reflector-blocks-complete :  Avalon SVN
- struts-sslext :  The Struts SSL Extension for HTTP/HTTPS switching
- struts-taglib :  Model 2 Model-View-Controller framework for Servlets and 
JSP
- struts-taglib-from-packages :  Model 2 Model-View-Controller framework 
for Servlets and JSP
- strutstestcase :  An extension of the standard JUnit TestCase class that 
provi...
- tomcat-catalina :  Servlet 2.3 and JSP 1.2 Reference Implementation


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-native-01062005.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jni/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jni.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jni (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar
 -Dversion=01062005 jar 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jni]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jni/dist/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar
-
Buildfile: build.xml

env:
 [echo] java.home = /x1/opt/__versions__/j2sdk1.4.2_08/jre
 [echo] user.home = /home/gump
 [echo] tc.library.path = 
/x1/gump/public/workspace/jakarta-tomcat-connectors/jni/native/.libs


prepare:
 

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 31 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2670: error: dereferencing pointer to incomplete type
mod_jk.c:2680: error: dereferencing pointer to incomplete type
mod_jk.c:2684: error: dereferencing pointer to incomplete type
mod_jk.c:2689: error: dereferencing pointer to incomplete type
mod_jk.c:2689: error: dereferencing pointer to incomplete type
mod_jk.c:2693: error: dereferencing pointer to incomplete type
mod_jk.c:2693: error: dereferencing pointer to incomplete type
mod_jk.c:2694: error: dereferencing pointer to incomplete type
mod_jk.c:2697: error: dereferencing pointer to incomplete type
mod_jk.c:2698: error: dereferencing pointer to incomplete type
mod_jk.c:2704: error: dereferencing pointer to incomplete type
mod_jk.c:2707: error: dereferencing pointer to incomplete type
mod_jk.c:2707: error: dereferencing pointer to incomplete type
mod_jk.c:2710: error: dereferencing pointer to incomplete type
mod_jk.c:2710: error: dereferencing pointer to incomplete type
mod_jk.c:2711: error: dereferencing pointer to incomplete type
mod_jk.c:2712: error: dereferencing pointer to incomplete type
mod_jk.c:2720: error: dereferencing pointer to incomplete type
mod_jk.c:2721: error: dereferencing pointer to incomplete type
mod_jk.c:2721: error: dereferencing pointer to incomplete type
mod_jk.c:2723: error: dereferencing pointer to incomplete type
mod_jk.c:2729: error: dereferencing pointer to incomplete type
mod_jk.c:2729: error: dereferencing pointer to incomplete type
mod_jk.c:2729: error: dereferencing pointer to incomplete type
mod_jk.c: In function `jk_register_hooks':
mod_jk.c:2740: error: `APR_HOOK_MIDDLE' undeclared (first use in this function)
mod_jk.c:2740: error: (Each undeclared identifier is reported only once
mod_jk.c:2740: error: for each function it appears in.)
make[1]: *** [mod_jk.lo] Error 1
make[1]: Leaving directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/apache-2.0'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 17001831052005, vmgump.apache.org:vmgump-public:17001831052005
Gump E-mail Identifier (unique within run) #4.

--

What to do now

[Bill Barker]

Now that we are officially a TLP (and, by the way, congrats Remy :), what is 
the migration strategy?


I'm assuming that we'll need to do a new 'ci' on all of what once was 
jakarta-tomcat*, but did jakarta-servletapi* and jakarta-watchdog* follow 
us?





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: What to do now

[Bill Barker]

- Original Message - 
From: Bill Barker [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Friday, May 27, 2005 6:43 PM
Subject: What to do now


Now that we are officially a TLP (and, by the way, congrats Remy :), what 
is

the migration strategy?

I'm assuming that we'll need to do a new 'ci' on all of what once was
jakarta-tomcat*, but did jakarta-servletapi* and jakarta-watchdog* follow
us?



s/ci/co/





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] 




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: Tomcat build question

[Bill Barker]

This is a known bug with Ant 1.6.4.  See:
http://issues.apache.org/bugzilla/show_bug.cgi?id=31031
  and
http://issues.apache.org/bugzilla/show_bug.cgi?id=35061

The solution is to use a different version of Ant.

- Original Message -
From: [EMAIL PROTECTED]
To: tomcat-dev@jakarta.apache.org
Sent: Thursday, May 26, 2005 1:06 PM
Subject: Tomcat build question


 I am new to this list. I download the main build.xml script from
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/building.html and try to use
ant to buld it. I got an error:

 build.xml:717: Cannot replace directory
\usr\share\java\tomcat-deps\src\java\org\apache\tomcat\dbcp with directory
\usr\share\java\tomcat-deps\src\java\org\apache\commons

 Do I need modify this main build script?

 When I click UML sequence diagram of request process, I get errors in PDF
file too.

 Can anyone tell me what's wrong?

 Thank you

 James

 -
 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: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/connector Connector.java Response.java

[Bill Barker]

- Original Message - 
From: Mladen Turk [EMAIL PROTECTED]

To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Wednesday, May 25, 2005 9:41 AM
Subject: Re: cvs commit: 
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/connector 
Connector.java Response.java




jean-frederic clere wrote:

Mladen Turk wrote:


INFO: Pausing Coyote HTTP/1.1 on http-8080
May 25, 2005 4:46:53 PM 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught exception (java.lang.NoSuchMethodError: 
org.apache.jk.core.MsgContext.getRequest()Ljava/lang/Object;) executing 
[EMAIL PROTECTED], terminating thread

May 25, 2005 4:46:54 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina


Any ideas why?


Why do you think the changes in Connector and Response cause the problem?



If I would have an idea I wouldn't ask 'Any ideas why?' :).

Anyhow seems the problem with MsgContext.java when Bill
changed the :
-public final  Object getRequest()
+public final Request getRequest()

Think that down the classtree getRequest() is still considered to
return the Ljava/lang/Object.



Doing a clean build of j-t-c/jk/java should fix it.  MsgContext isn't 
referenced outside of there.


This is actually changed as part of Mark's Form-auth POST-replay, not the 
Connector/Response buffering.




Regards,
Mladen.

-
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: Hybrid (NIO+Multithread, SSL enabled) architecture for Coyote

[Bill Barker]

- Original Message - 
From: Jeanfrancois Arcand [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Friday, May 20, 2005 6:56 AM
Subject: Re: Hybrid (NIO+Multithread, SSL enabled) architecture for Coyote



Mladen Turk wrote:
Vicenc Beltran Querol wrote:
Hi guys,
I'm not trying to be a Tomcat developer. I'm working on my PhD on web 
performance and just decided to share with you the experimental code 
I've developed after studying the performance obtained ;).

I've done some serious testings with HTTP server and NIO.
The results were always bad for NIO.
Blocking I/O is minimum 25% faster then NIO.
Faster in what? Throughput and/or scalability?
I disagree ;-) I would like to see your implementation, because from what 
I'm seeing/measuring, it is completely the inverse. I would be interested 
to see how you did implement your NIO connector. The problem

with HTTP is not NIO, but the strategy to use for predicting if you have 
read all the bytes or not. Falling to implement a good strategy will ends 
up parsing the bytes many times, calling the Selector.wakeup() too often, 
thus poor performance. The way you register your SelectionKey is also very 
important.

Yeah, the speed improvement with NIO is the only thing that makes 
ChannelNioSocket not a total PoC.  It's really depressing that any JVM 
vendor would allow such a huge performance difference between 
Socket.getOutputStream().write and SocketChannel.write.


Also, blocking IO required 1 thread per connection, which doesn't scale 
very well. That's why I think the new APR connector is interesting, since 
it fix that problem. But even if with APR, you did workaround the JNI 
bottleneck by using direct byte buffer, I suspect a pure NIO 
implementation will perform better than APR (except for static resource) 
just because of the C-Java overhead. But I don't have yet numbers to 
show...come to my session at JavaOne, I will :-)

You may tray that simply by using demo HTTP servers
Blocking/Blocking Pool/NIO single thread/NIO multiple threads
that comes with new Java6 (see java.net for sources).
Right. This is actually a good example not to follow ;-).
BTW the big patch use NIO blocking, which may improve scalability, but 
will impact throughput. The patch should be improved to use NIO 
non-blocking. And then we can compare ;-)

-- Jeanfrancois

OTOH, I'm sure you must have some performance results :)
Simply run the 'ab -n 10 -c 100 -k host:8080/tomcat.gif'
with your patch and standard Tomcat5.5.9.

Anyway, it's OK. I'll work on the new patch and resubmit it.

Great.
Regards,
Mladen.
-
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]


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: AJP/Java connector issues

[Bill Barker]

- Original Message -
From: jean-frederic clere [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Friday, May 20, 2005 9:02 AM
Subject: Re: AJP/Java connector issues


 Mladen Turk wrote:
  Hi,
 
  Just noticed a strange behavior in the Java part of the
  JK dealing with large (over 8184 bytes) data transfers.
 
  Since with 8192 bytes AJP packet size, the maximum
  transferred size per each packet is 8184 bytes one
  would expect that for 2 bytes file the packets
  would be in a form of:
  1:8184,2:8184,3:3632 thus total of 2 bytes.
 
  But in fact the behavior is rely weird:
  1:8184,2:8,3:8184,4:8,5:3616.
 
  Instead only three, the five! packets are transferred.
 
  Seems that algorithm is breaking 8192 bytes of data to
  two packets (8184 and 8 bytes).

 I have an ugly patch for that. Find it attached (that just for gettting
comments).


If we move the protocol check into Response.setConnector, the patch isn't
even that ugly ;-).

 Cheers

 Jean-Frederic

 
  Bill,
  Any idea how to solve this, because it's way too
  inefficient.
  What's makes the things even worse is that for each
  packet Apache2 creates a transient bucket thus
  rising the memory usage.
 
 
  Regards,
  Mladen.
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 








 Index: Response.java
 ===
 RCS file:
/home/cvspublic/jakarta-tomcat-catalina/catalina/src/share/org/apache/catali
na/connector/Response.java,v
 retrieving revision 1.12
 diff -u -r1.12 Response.java
 --- Response.java 25 Apr 2005 22:06:30 - 1.12
 +++ Response.java 20 May 2005 15:56:25 -
 @@ -68,6 +68,16 @@


  public Response() {
 +outputBuffer = new OutputBuffer();
 +outputStream = new CoyoteOutputStream(outputBuffer);
 +writer = new CoyoteWriter(outputBuffer);
 +urlEncoder.addSafeCharacter('/');
 +}
 +
 +public Response(int size) {
 +outputBuffer = new OutputBuffer(size);
 +outputStream = new CoyoteOutputStream(outputBuffer);
 +writer = new CoyoteWriter(outputBuffer);
  urlEncoder.addSafeCharacter('/');
  }

 @@ -174,20 +184,19 @@
  /**
   * The associated output buffer.
   */
 -protected OutputBuffer outputBuffer = new OutputBuffer();
 +protected OutputBuffer outputBuffer;


  /**
   * The associated output stream.
   */
 -protected CoyoteOutputStream outputStream =
 -new CoyoteOutputStream(outputBuffer);
 +protected CoyoteOutputStream outputStream;


  /**
   * The associated writer.
   */
 -protected CoyoteWriter writer = new CoyoteWriter(outputBuffer);
 +protected CoyoteWriter writer;


  /**
 Index: Connector.java
 ===
 RCS file:
/home/cvspublic/jakarta-tomcat-catalina/catalina/src/share/org/apache/catali
na/connector/Connector.java,v
 retrieving revision 1.18
 diff -u -r1.18 Connector.java
 --- Connector.java 30 Apr 2005 03:32:43 - 1.18
 +++ Connector.java 20 May 2005 15:56:42 -
 @@ -897,7 +897,12 @@
   */
  public Response createResponse() {

 -Response response = new Response();
 +System.out.println(Connector: createResponse: getProtocol:  +
getProtocol());
 +Response response = null;
 +if (AJP/1.3.equals(getProtocol()))
 +response = new Response(8184);
 +else
 +response = new Response();
  response.setConnector(this);
  return (response);









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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 161 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-19052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-19052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-19052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-19052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-19052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2519052005, brutus:brutus-public:2519052005
Gump E-mail Identifier (unique within run) #19.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 161 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-19052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-19052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-19052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-19052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-19052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2519052005, brutus:brutus-public:2519052005
Gump E-mail Identifier (unique within run) #19.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

Re: AJP/Java connector issues

[Bill Barker]

- Original Message - 
From: Mladen Turk [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Cc: Bill Barker [EMAIL PROTECTED]
Sent: Wednesday, May 18, 2005 11:44 PM
Subject: AJP/Java connector issues


Hi,
Just noticed a strange behavior in the Java part of the
JK dealing with large (over 8184 bytes) data transfers.
Since with 8192 bytes AJP packet size, the maximum
transferred size per each packet is 8184 bytes one
would expect that for 2 bytes file the packets
would be in a form of:
1:8184,2:8184,3:3632 thus total of 2 bytes.
But in fact the behavior is rely weird:
1:8184,2:8,3:8184,4:8,5:3616.
Instead only three, the five! packets are transferred.
Seems that algorithm is breaking 8192 bytes of data to
two packets (8184 and 8 bytes).
Bill,
Any idea how to solve this, because it's way too
inefficient.
What's makes the things even worse is that for each
packet Apache2 creates a transient bucket thus
rising the memory usage.
It's probably Nagle (which is off by default).  Try tcpNoDelay=false.
Regards,
Mladen.
-
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: AJP/Java connector issues

[Bill Barker]

- Original Message - 
From: Mladen Turk [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Cc: Bill Barker [EMAIL PROTECTED]
Sent: Wednesday, May 18, 2005 11:44 PM
Subject: AJP/Java connector issues


Hi,
Just noticed a strange behavior in the Java part of the
JK dealing with large (over 8184 bytes) data transfers.
Since with 8192 bytes AJP packet size, the maximum
transferred size per each packet is 8184 bytes one
would expect that for 2 bytes file the packets
would be in a form of:
1:8184,2:8184,3:3632 thus total of 2 bytes.
But in fact the behavior is rely weird:
1:8184,2:8,3:8184,4:8,5:3616.
Instead only three, the five! packets are transferred.
Seems that algorithm is breaking 8192 bytes of data to
two packets (8184 and 8 bytes).
Bill,
Any idea how to solve this, because it's way too
inefficient.
What's makes the things even worse is that for each
packet Apache2 creates a transient bucket thus
rising the memory usage.
I see what this is now:  The default Connector OutputBuffer size is 8K, so 
it's sending the output to JkInputStream in 8K chunks.  JkInputStream sends 
all of the 8K to Apache in two chunks.

As a Coyote OutputBuffer, it's not really JkInputStream's job to do 
additional buffering.  It's probably better to do 
response.setBufferSize(2); so that the Connector will send the whole 
thing to JkInputStream as one chunk.

Regards,
Mladen.
-
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: AJP/Java connector issues

[Bill Barker]

- Original Message -
From: Mladen Turk [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, May 19, 2005 2:19 PM
Subject: Re: AJP/Java connector issues


 Bill Barker wrote:
 
 
  I see what this is now:  The default Connector OutputBuffer size is 8K,
  so it's sending the output to JkInputStream in 8K chunks.  JkInputStream
  sends all of the 8K to Apache in two chunks.
 
  As a Coyote OutputBuffer, it's not really JkInputStream's job to do
  additional buffering.  It's probably better to do
  response.setBufferSize(2); so that the Connector will send the whole
  thing to JkInputStream as one chunk.
 


 Sure that seems to be the problem, but it's hard to convince the users
 to write the applications having AJP packet size in mind ;)
 The best would be that instead default 8192 bytes, when AJP connector
 is loaded that response size is either set to 8184 or 16386 bytes
 (one or two packets) by default.

 Is something like that possible?


It would be really easy to default to 8184 for all Connectors (just change
the value in o.a.c.connector.OutputBuffer).  I'm not so sure how happy that
would make Remy.

It wouldn't be too hard to have Connector.createResponse check the protocol,
and if it's AJP/1.3 then set the buffer size to 16386 (currently it's not
possible to decrease the buffer size).

It wouldn't be that hard to add buffering to JkInputStream so that it always
tries to write out a 8184 packet.  This would also prevent fracturing in the
event that the webapp programmer decides to call response.setBufferSize
herself.  The downside would be an extra arraycopy when writing (and, of
course, an extra 8184*numThreads bytes of memory used :).

 Regards,
 Mladen.

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 159 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-18052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-18052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-18052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-18052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-18052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2418052005, brutus:brutus-public:2418052005
Gump E-mail Identifier (unique within run) #20.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 159 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-18052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-18052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-18052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-18052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-18052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2418052005, brutus:brutus-public:2418052005
Gump E-mail Identifier (unique within run) #20.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 155 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-16052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-16052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-16052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2316052005, brutus:brutus-public:2316052005
Gump E-mail Identifier (unique within run) #16.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 155 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-16052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-16052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-16052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2316052005, brutus:brutus-public:2316052005
Gump E-mail Identifier (unique within run) #16.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 153 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-15052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-15052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-15052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2715052005, brutus:brutus-public:2715052005
Gump E-mail Identifier (unique within run) #19.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 153 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-15052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-15052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-15052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-15052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-15052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2715052005, brutus:brutus-public:2715052005
Gump E-mail Identifier (unique within run) #19.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

Re: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml

[Bill Barker]

- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Sunday, May 15, 2005 6:57 PM
Subject: Re: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml


[EMAIL PROTECTED] wrote:
markt   2005/05/11 14:39:41
  Modified:catalina/src/share/org/apache/catalina/authenticator
FormAuthenticator.java SavedRequest.java
   webapps/docs changelog.xml
  Log:
  Include request body in saved request when using FORM authentication.
   - Fixes problem with saved request assuming platform default encoding 
for POSTed
parameters.
   - Improves restoration of request by using CoyoteRequest
Can you revert this commit ? I see no other solution right now, as:
- it will not work with AJP
- it depends on HTTP/1.1 connector internal classes, so it breaks a clean 
build
Urm, we are nowhere close to doing another release (and Mark has already 
promised to revert it before then, if not fixed).  Also, it doesn't really 
take much more to fix it from here.  If you can't see any other solution 
right now, then you are truely brain-dead.

Thanks,
Rémy


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: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml

[Bill Barker]

- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Sunday, May 15, 2005 8:20 PM
Subject: Re: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml


Bill Barker wrote:
Urm, we are nowhere close to doing another release (and Mark has already 
promised to revert it before then, if not fixed).  Also, it doesn't 
really take much more to fix it from here.  If you can't see any other 
solution right now, then you are truely brain-dead.
I missed the part about reverting, all I saw about this was adding limits.
Besides, I am mostly complaining because it seems to break the build, which 
is never acceptable (even if no release is planned immediately).
Gump has been nagging about this for, like, almost a week now.  You're a 
week late to be b*tching about this.

I want to allow the committers that don't check email over the weekend a 
chance to review my Jk-Coyote patch for this particular issue, and then if 
Mark doesn't patch it first, I promise that Gump will get a clean build.  At 
this point, all it takes is anybody with half a brain and Karma to finish 
the patch.

Rémy


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]

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 151 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-14052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-14052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-14052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-14052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-14052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 3314052005, brutus:brutus-public:3314052005
Gump E-mail Identifier (unique within run) #20.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 151 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-14052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-14052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-14052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-14052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-14052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 3314052005, brutus:brutus-public:3314052005
Gump E-mail Identifier (unique within run) #20.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 InternalAprOutputBuffer.java

[Bill Barker]

- Original Message - 
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, May 14, 2005 1:41 PM
Subject: cvs commit: 
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 
InternalAprOutputBuffer.java


remm2005/05/14 13:41:26
 Modified:http11/src/java/org/apache/coyote/http11
   InternalAprOutputBuffer.java
 Log:
 - Optimize a little using a direct byte buffer to replace the socket 
buffer.
 - I'll experiment with doing the same optimization for reads, but I don't 
expect it to do anything
   (other than waste memory) as copying bytes will be needed.

Cool.  I had been thinking that the savings with NIO were all do to the fact 
that SocketChannel.write would allocate and copy to another ByteBuffer 
instance if I didn't use direct ByteBuffers.


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]

[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 149 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-13052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-13052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-13052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2413052005, brutus:brutus-public:2413052005
Gump E-mail Identifier (unique within run) #19.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[GUMP@brutus]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 149 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-13052005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-13052005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-13052005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-13052005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-13052005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2413052005, brutus:brutus-public:2413052005
Gump E-mail Identifier (unique within run) #19.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11AprProcessor.java

[Bill Barker]

- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 11, 2005 4:23 AM
Subject: cvs commit:
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11
Http11AprProcessor.java


 remm2005/05/11 04:23:26

   Modified:util/java/org/apache/tomcat/util/net AprEndpoint.java
http11/src/java/org/apache/coyote/http11
 Http11AprProcessor.java
   Log:
   - Should fix thread safety issue reported by Bill (needs testing).

Peter's test case does finish with this on my Solaris box.  I'll see if I
can do more testing next week.



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: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11AprProcessor.java

[Bill Barker]

- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Friday, May 13, 2005 9:29 PM
Subject: Re: cvs commit: 
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 
Http11AprProcessor.java


Bill Barker wrote:
remm2005/05/11 04:23:26
 Modified:util/java/org/apache/tomcat/util/net AprEndpoint.java
  http11/src/java/org/apache/coyote/http11
   Http11AprProcessor.java
 Log:
 - Should fix thread safety issue reported by Bill (needs testing).
Peter's test case does finish with this on my Solaris box.  I'll see if I
can do more testing next week.
Mladen told me that the sync was badly done, and that I should be using a 
queue instead (too bad, it took one week).
Peter's test was stressing my poor little box a lot (which it really 
shouldn't, since it is a high-concurrency/low-traffic test).  It was one of 
the things I wanted to look into when I had time to run more tests.

Also, I've been running the test with sendfile disabled.  It seems that 
Solaris7 doesn't have this particular feature :(It was added to Solaris8). 
With sendfile enabled, I get a nice core-dump (since there is no 
apr_socket_sendfile in my libapr.so :).  I'm guessing that a for production 
release we need something like this in AprEndpoint.init:
  if(useSendfile  !Apr.hasFeature(Apr.SENDFILE)) {
log.warn(disabling sendfile, since your apr version doesn't 
support it);
useSendfile = false;
  }

He still needs to remove some syncs in the native code, apparently (= the 
hacks he added on top of APR, but which didn't quite work).

It seems I need to look for a few more patches before I can usefully test.
Rémy

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]