[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed
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 142 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-09052005/build/libtool --silent --mode=compile gcc -I/usr/local/gump/public/workspace/apache-httpd/dest-09052005/include -g -O2 -g -O2 -pthread -DHAVE_APR -I/usr/local/gump/public/workspace/apr/dest-09052005/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-09052005/build/libtool: /usr/local/gump/public/workspace/apache-httpd/dest-09052005/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 2409052005, brutus:brutus-public:2409052005 Gump E-mail Identifier (unique within run) #24. -- 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
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 142 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-09052005/build/libtool --silent --mode=compile gcc -I/usr/local/gump/public/workspace/apache-httpd/dest-09052005/include -g -O2 -g -O2 -pthread -DHAVE_APR -I/usr/local/gump/public/workspace/apr/dest-09052005/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-09052005/build/libtool: /usr/local/gump/public/workspace/apache-httpd/dest-09052005/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 2409052005, brutus:brutus-public:2409052005 Gump E-mail Identifier (unique within run) #24. -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
NSIS installer for JK/IIS
Hi ZIP file attachments don't seem to work. I try a different format: tar/bzip2. Martin -Original Message- From: Martin Goldhahn Sent: Monday, May 09, 2005 10:56 AM To: 'tomcat-dev@jakarta.apache.org' Subject: NSIS installer for JK/IIS Hi, I have written an installer for the NSIS. Today, only an InstallShield installer for the tomcat connector exists. I don't have InstallShield. And besides, Tomcat itself uses NSIS. I would like to donate the code to the ASF. The file attached to this mail contains all necessary files. They can be extracted to TOMCAT_SOURCE\jakarta-tomcat-connectors\jk\native\iis\installe r_nsi, i.e. parallel to the existing InstallShield installer. Regards Martin Goldhahn [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NSIS installer for JK/IIS
Martin Goldhahn wrote: Hi ZIP file attachments don't seem to work. I try a different format: tar/bzip2. Yes, paranoid list setting ;) Open a bugzilla entry as enhancement for Tomcat5-Native:JK And add the attachment there. http://issues.apache.org/bugzilla/enter_bug.cgi Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
TIFF headers seem to have wrong sizes
My initial work seems to indicate that the headers of TIFF images being served have the size of the images more than twice what they should be. Is that possible or likely? Thanks -- You can lead a horse to water but you cannot make it float on its back. ~Dakota Jack~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34814] New: - NSIS installer for ISAPI redirector
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34814. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34814 Summary: NSIS installer for ISAPI redirector Product: Tomcat 5 Version: Unknown Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Native:JK AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I have written an installer for the NSIS. Today, only an InstallShield installer for the tomcat connector exists. I don't have InstallShield. And besides, Tomcat itself uses NSIS. I would like to donate the code to the ASF. The file attached to this mail contains all necessary files. They can be extracted to TOMCAT_SOURCE\jakarta-tomcat-connectors\jk\native\iis\installer_nsi, i.e. parallel to the existing InstallShield installer. Regards Martin Goldhahn [EMAIL PROTECTED] -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34814] - NSIS installer for ISAPI redirector
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34814. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34814 --- Additional Comments From [EMAIL PROTECTED] 2005-05-09 13:55 --- Created an attachment (id=14970) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14970action=view) NSIS script and related files extract the files to TC_SRC/jakarta-tomcat-connectors/jk/native/iis/installer_nsi You need NSIS 2.x from http://nsis.sf.net to create an installer with these scripts -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat performance patch (in development) to reduce concurrency...
Scott Marlow wrote:
Anyway, my point is that this could be a worthwhile enhancement for
applications that run on Tomcat. What I don't understand yet is whether
the same functionality is already in Tomcat.
I should point out that some applications shouldn't limit the max number
of concurrent requests (long running requests won't benefit but maybe
those applications shouldn't run on the web tier anyway :-)
I agree with the intent, but this is not implemented properly. I think
the idea is to restrict concurrency in the application layer, rather at
the low level (where, AFIK, concurrency isn't that expensive, and is
better addressed using a little non blocking IO). The performance
benefits for certain types of applications will be the same, but without
introducing any unwanted limitations or incorrect behavior at the
connector level.
I think you should write a ConcurrencyValve instead, which would do
something like:
boolean shouldRelease = false;
try {
concurrencySemaphore.acquire();
shouldRelease = true;
getNext().invoke(request, response);
} finally {
if (shouldRelease)
concurrencySemaphore.release();
}
As it is a valve, you can set it globally, on a host, or on an
individual webapp, allowing to control concurrency in a fine grained
way. In theory, you can also add it on individual servlets, but it
requires some hacking. Since it's optional and independent, I think it
is acceptable to use Java 5 for it.
As you pointed out, some applications may run horribly with this (slow
upload is the most glaring example).
Rmy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34397] - loglevel 'emerg' is handled as loglevel 'error'
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34397. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34397 [EMAIL PROTECTED] changed: What|Removed |Added Component|Connector:Coyote|Native:JK -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34724] - Domain for single sign-on cookie
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34724. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34724 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #14918|0 |1 is obsolete|| -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34724] - Domain for single sign-on cookie
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34724. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34724 --- Additional Comments From [EMAIL PROTECTED] 2005-05-09 16:19 --- Created an attachment (id=14971) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14971action=view) AuthenticatorBase.java patch -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34724] - Domain for single sign-on cookie
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34724. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34724 --- Additional Comments From [EMAIL PROTECTED] 2005-05-09 16:19 --- Created an attachment (id=14972) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14972action=view) SingleSignOn.java patch -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34724] - Domain for single sign-on cookie
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34724. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34724 --- Additional Comments From [EMAIL PROTECTED] 2005-05-09 16:20 --- Created an attachment (id=14973) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14973action=view) mbeans-descriptors.xml patch -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34724] - Domain for single sign-on cookie
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34724. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34724 --- Additional Comments From [EMAIL PROTECTED] 2005-05-09 16:24 --- I aggree that an optional attribute on the SingleSingOn valve is the more elegant way to specify a domain name for the sso cookie. I modified the implementation in the suggested way (see the three new patches attachted) so the cookie domain can be set on the valve like Valve className=org.apache.catalina.authenticator.SingleSignOn cookieDomain=.mydomain.xa/ -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - 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/servlets DefaultServlet.java
Remy Maucherat wrote: jean-frederic clere wrote: I will try to solve the problem with a filter. You can simply call response.getWriter() in your filter if you determine the file needs to use fileEncoding. I have used a filter with two wrappers one for GET the other for PUT, Now Tomcat runs correcly on the BS2000 Mainframe. Rémy - 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]
DO NOT REPLY [Bug 34818] New: - Request alternating color scheme for html manager
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34818. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34818 Summary: Request alternating color scheme for html manager Product: Tomcat 5 Version: 5.5.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Webapps:Manager AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When undeploying applications, it is easy to accidently click on the wrong button, thus unloading the wrong application (causes stress when multiple people are using the system at the same time). Propose to add alternating background color to the table. patches and example: http://review.gis.msu.edu/patches/ Thanks -Jeff Domeyer Geographic Information System Michigan State University -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN/VOTE] JK 1.2.12 Released
Builds and runs on both Solaris 7 8 with Apache 2.0.54. Glenn On Sat, May 07, 2005 at 06:23:38PM +0200, Mladen Turk wrote: Hi, JK 1.2.12 has been released. This is mostly a bug fix release over JK 1.2.10 and fixes wc_close bug found in 1.2.11. Please see the: http://jakarta.apache.org/tomcat/connectors-doc/changelog.html for a full list of changes. Sources can be found at: http://www.apache.org/dist/jakarta/tomcat-connectors/jk/source/jk-1.2.12/ Binaries can be found at: http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/ For now there is a set of win32 binaries: http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/win32/jk-1.2.12/ and some linux binaries: http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/linux/jk-1.2.12/ Feel free to add any other binaries for your favorite platform :) I would also like to make a stability VOTE at once (to keep the email noise at minimum). The vote will run for a week. [ ] Stable -- good build [ ] Alpha -- something serious is wrong: what is it? Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
Build and run on NetWare with apache 2.0.54. JJ [EMAIL PROTECTED] 5/6/2005 6:31 AM Hi, It's been a week since 1.2.11 has been tagged and released. Because of bug in wc_close, and sice no other bugs have been reported for a week, I plan to tag the 1.2.12 tomorrow morning, 10:00 GMT. Any objections? Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
At 02:30 PM 5/9/2005, Jean-Jacques Clar wrote: Build and run on NetWare with apache 2.0.54. Woot! And thank you for the example, Jean-Jacques, of exactly why we need more than a few days before we declare 'stable' releases ;-) But I do think it's wonderful that the NetWare issues are gone. What about 1.3.33? What about 2.1-dev? What about other servers? And you mention it runs, but against which Tomcat, 5(.5)? I hope you see my point, there is an incredible set of combinations which are quite useful and legitimate in tomcat-connectors. I keep hearing the refrain Lets deprecate all this stuff I don't test. Rather than deprecate, what about simply allowing enough time for dust to settle, and reports to roll in. 3 +1's that all looks like it's good, and then let the community (with all their goofy combinations of OS's, connectors, and backends) chime in with complaints. [Yes - I mean complaints, few ever give us the good news when all is well :-] Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
- Original Message - From: William A. Rowe, Jr. [EMAIL PROTECTED] To: Tomcat Developers List tomcat-dev@jakarta.apache.org Cc: tomcat-dev@jakarta.apache.org Sent: Monday, May 09, 2005 1:28 PM Subject: Re: Tagging 1.2.12 At 02:30 PM 5/9/2005, Jean-Jacques Clar wrote: Build and run on NetWare with apache 2.0.54. Woot! And thank you for the example, Jean-Jacques, of exactly why we need more than a few days before we declare 'stable' releases ;-) But I do think it's wonderful that the NetWare issues are gone. What about 1.3.33? What about 2.1-dev? What about other servers? And you mention it runs, but against which Tomcat, 5(.5)? According to Gump, it still doesn't want to build against 2.1-dev ;-). Of course, this is because of a httpd bug, so it shouldn't effect the stability vote of mod_jk one way or the other. I hope you see my point, there is an incredible set of combinations which are quite useful and legitimate in tomcat-connectors. I keep hearing the refrain Lets deprecate all this stuff I don't test. Rather than deprecate, what about simply allowing enough time for dust to settle, and reports to roll in. 3 +1's that all looks like it's good, and then let the community (with all their goofy combinations of OS's, connectors, and backends) chime in with complaints. [Yes - I mean complaints, few ever give us the good news when all is well :-] 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: Tagging 1.2.12
William A. Rowe, Jr. wrote: I keep hearing the refrain Lets deprecate all this stuff I don't test. I really can not tell what echoes on you mind ;), but if you follow both bugzilla and tomcat-dev@ as well as tomcat-user@, you will find out that there where no bug reports neither questions related to domino connector, isapi or nt_service for years. So where is the 'refrain' in that? Either nobody uses them or the existing implementations are so good that no further development is needed. Rather than deprecate, what about simply allowing enough time for dust to settle, and reports to roll in. Did you follow the bugzilla issues for the last two months, and the things we fixed from the latest stable release? 3 +1's that all looks like it's good, and then let the community (with all their goofy combinations of OS's, connectors, and backends) chime in with complaints. If we would think like that, no software release would be ever made. Should we ask every user in the world, if it's OK to release? Again, if you have some doubts, or tests that shows the release is broken or faulty, please report that, or even better fix it, and commit. Please let's keep the politics, bureaucracy and formalism out of j-t-c. There are so many ASF projects that are suffering from that, and j-t-c was one of the few that had a pretty tolerant developer community ;). Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34643] - document how to use certificate-based clientAuth on a per user or per session basis also with self-signed/expired client certs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34643. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34643 [EMAIL PROTECTED] changed: What|Removed |Added Summary|document how to use |document how to use |certificate-based |certificate-based |clientAuth on a per user |clientAuth on a per user |or per session basis|or per session basis also ||with self-signed/expired ||client certs --- Additional Comments From [EMAIL PROTECTED] 2005-05-09 23:49 --- it appears that if the client certificate shall not be asked from all users and not upon the first contact with the given connector, the clientAuth attribute isn't it, irrespective of whether set to true or want. The approach appears to be rather to direct the user to a protected jsp/struts action at the point in time you want the client cert auth to happen with security-constraint web-resource-collection web-resource-nameClient Certificate Auth/web-resource-name url-pattern/certBasedAuth.do/url-pattern /web-resource-collection auth-constraint / /security-constraint login-config auth-methodCLIENT-CERT/auth-method /login-config Being flexible with respect to the used certificate remains tricky: 1) if already knowing the certificate to be expected e.g. by virtue of it being in a LDAP truststore, it appears to be impossible to allow for mismatches of the certs[0].getSubjectDN().getName() without replacing the current org.apache.catalina.authenticator.SSLAuthenticator - one might for example rather use the SHA1 fingerprint to match? 2) similarly, if you want to be more tolerant on certificate expiration/not-yet-valid, I haven't figured how to get the validate=false for org.apache.catalina.realm.RealmBase.authenticate(X509Certificate[] certs) from a config file without altering sources. 3) As for self-signed certificates, I see two approaches a) be able to create a mini-trust-store on the fly before the ssl-handshake occurs in org.apache.tomcat.util.net.jsse.JSSESupport.handShake() - I have no clue how late in an SSLSocket's life its truststore can be altered? A nice example how this can be done a per thread basis (albeit before creating the socket and not when it's already in operation) is Oleg's org.apache.commons.httpclient.contrib.ssl.AuthSSLProtocolSocketFactory (see Bug 34391) - I guess this implies that the web-app programmer in some way (by means of an enhanced LoginConfig or an extra parameter of the method or a session attribute?) might tell org.apache.catalina.authenticator.SSLAuthenticator.authenticate() the self-signed cert it should expect when that method starts b) alternatively, a less rigid TrustManager might be used in org.apache.tomcat.util.net.jsse.JSSE15SocketFactory.getTrustManagers(String keystoreType, String algorithm) - some ideas are in http://forum.java.sun.com/thread.jspa?forumID=2threadID=411937 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
Bill, I have been stress-testing JK for four days in my lab, since the wc_close() bug has been fixed.I have 58 clients, each using 10 threads, doing JSPs and servlets requests to 2 different servers (from the examples set) : emt64, dual proc with ht enable, and Compaq proliant 8 CPUS.The new mod_jk was twice tested by our set of automations in addition to spent 2 days being tortured by one of our system test engineer. I built and tried mod_jk against 2.0.52 and 2.1-dev. However, in these two cases it was not tested as for 2.0.54. Stress tests were done against Tomcat 4.1.30, validation against 4.1.31. For 1.3.33, I am sorry to admit that I did not build JK and is not currently planning to do it.I currently have access to these resources. What else do you want me to do? I will not and could never be able to cover this incredible set of combinations.Next time I will put more details in my report, but I was reporting a fact not more, not less.But from what I could do, 1.2.12 is good. --JJ [EMAIL PROTECTED] 5/9/2005 2:28 PM At 02:30 PM 5/9/2005, Jean-Jacques Clar wrote: Build and run on NetWare with apache 2.0.54. Woot! And thank you for the example, Jean-Jacques, of exactly why we need more than a few days before we declare 'stable' releases ;-) But I do think it's wonderful that the NetWare issues are gone. What about 1.3.33? What about 2.1-dev? What about other servers? And you mention it runs, but against which Tomcat, 5(.5)? I hope you see my point, there is an incredible set of combinations which are quite useful and legitimate in tomcat-connectors. I keep hearing the refrain Lets deprecate all this stuff I don't test. Rather than deprecate, what about simply allowing enough time for dust to settle, and reports to roll in. 3 +1's that all looks like it's good, and then let the community (with all their goofy combinations of OS's, connectors, and backends) chime in with complaints. [Yes - I mean complaints, few ever give us the good news when all is well :-] Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34829] New: - IOException in InputBuffer when reading xml from post
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34829. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34829 Summary: IOException in InputBuffer when reading xml from post Product: Tomcat 5 Version: 5.5.9 Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priority: P2 Component: Connector:Coyote AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When reading xml from a post, the following exception occurred: java.io.IOException at org.apache.catalina.connector.InputBuffer.reset(InputBuffer.java:439) at org.apache.catalina.connector.CoyoteReader.reset(CoyoteReader.java:121) at org.apache.catalina.connector.CoyoteReader.readLine(CoyoteReader.java:178) More detailed log information will be attached. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34829] - IOException in InputBuffer when reading xml from post
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34829. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34829 --- Additional Comments From [EMAIL PROTECTED] 2005-05-10 00:36 --- Created an attachment (id=14978) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14978action=view) Tomcat log -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34829] - IOException in InputBuffer when reading xml from post
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34829. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34829 --- Additional Comments From [EMAIL PROTECTED] 2005-05-10 00:46 --- I recommend you modify your code to not use readLine, which is extremely inefficient. Unfortunately, I cannot help you fix or investigate this problem. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Michael Bünermann/HBF/Minden/kampa/DE ist außer Haus.
Ich werde ab 10.05.2005 nicht im Büro sein. Ich kehre zurück am 12.05.2005. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. In dringenden Fällen wenden Sie sich bitte Herrn Bagehorn ([EMAIL PROTECTED]). Herr Bagehorn hat die Rufnummer 0571/93425-80) Am Montag und Dienstag, den 02.05- 03.05.2005 erreichen Sie mich auch über die Funk-Rufnummer: 0171/99 33 525.
Re: Tagging 1.2.12
At 05:08 PM 5/9/2005, Jean-Jacques Clar wrote: I built and tried mod_jk against 2.0.52 and 2.1-dev. However, in these two cases it was not tested as for 2.0.54. Stress tests were done against Tomcat 4.1.30, validation against 4.1.31. For 1.3.33, I am sorry to admit that I did not build JK and is not currently planning to do it.I currently have access to these resources. What else do you want me to do? I will not and could never be able to cover this incredible set of combinations.Next time I will put more details in my report, but I was reporting a fact not more, not less.But from what I could do, 1.2.12 is good. Thank you Jean-Jacques - narrows down the scope of what I need to test. Of course the handful here will never test with any of the breadth of options available, it was my point :) I'm in a good position to have my staff beat on jk .12 / Apache 1.3 tomcat 4.1 and 5.0. I'll focus on that since the Apache2 side seems well covered. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32141] - Memory leak in Jk connector, ChannelSocket.registerRequest
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32141. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32141 --- Additional Comments From [EMAIL PROTECTED] 2005-05-10 05:17 --- For those who can't wait for this to be fixed in 5.0.x, look at this URL for instructions on replacing jmx.jar https://sourceforge.net/tracker/?func=detailatid=450647aid=1068766group_id=47745 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
