Re: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java
Het adres [EMAIL PROTECTED] is voorlopig niet meer in gebruik vanwege grote hoeveelheden virusmails die daarop binnenkomen. Gebruik het nieuwe adres dat op de website staat (linksonder). Excuses voor het ongemak! - 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 JkCoyoteHandler.java JkMain.java
[EMAIL PROTECTED] wrote: billbarker2004/01/26 22:43:18 Modified:jk/java/org/apache/jk/common ChannelSocket.java JniHandler.java jk/java/org/apache/jk/core JkHandler.java jk/java/org/apache/jk/server JkCoyoteHandler.java JkMain.java Log: Adding support for the new pause/resume protocol. You beat me to it. Thanks :) Rémy - 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 JkCoyoteHandler.java
[EMAIL PROTECTED] wrote: billbarker2004/01/15 19:14:11 Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java Log: Fix JMX self-registration when loading the normal way. I don't understand why, but two thread pools are registeres (and I have only one connector): Catalina:type=ThreadPool,name=jk8009 Catalina:type=ThreadPool,name=jk8010 ? The good part is that this is automagically picked up by the status servlet :) I don't know if the scoreboard will work, but it's a start. I remember some people who wanted to get status info about JK. Rémy - 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 JkCoyoteHandler.java
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Friday, January 16, 2004 2:15 AM Subject: Re: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java [EMAIL PROTECTED] wrote: billbarker2004/01/15 19:14:11 Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java Log: Fix JMX self-registration when loading the normal way. I don't understand why, but two thread pools are registeres (and I have only one connector): Catalina:type=ThreadPool,name=jk8009 Catalina:type=ThreadPool,name=jk8010 ? It seems that having the JMX registration broken was hiding all sorts of bugs in Jk. It seems that all the Handlers are now added to the WorkerEnv twice (once by JkMain and once during JMX registration). I'm going to have to think about this one, since I don't really want to have to JMX register the connectors in 3.3.2. The good part is that this is automagically picked up by the status servlet :) I don't know if the scoreboard will work, but it's a start. I remember some people who wanted to get status info about JK. 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: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java
- Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 9:32 PM Subject: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java billbarker2004/01/06 21:32:44 Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java Log: Adding the required PAs to allow the Coyote-Jk connector to play in the sandbox. I'm not really happy with how this turned out. The C2BC issue could actually get solved by moving the check for 'null', but it just didn't seem worth it (since it is a re-used component, the PA is invoked rarely). However, invoking a PA for the status line bothers me. My suggestion is to change o.a.t.u.http.HttpMessages to make 'getMessage' an instance (instead of the current static) method, and make everyone that wants to use it create an instance (at a point where they know the call-stack is clean). Excess memory usage should be pretty small, and you avoid a big hit with the PA. As always, I'm volunteering to do the code-monkey (copy; Pier) part of the project for TC 3.3.x-5.x. 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 JkCoyoteHandler.java
Forgot to include: the patch was submited by Stefan Proels. Costin [EMAIL PROTECTED] wrote: costin 2003/03/13 16:03:03 Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java Log: Extra fix - avoids the need for a change in Response PR: 14292 Revision ChangesPath 1.38 +3 -1 jakarta-tomcat-connectors/jk/java/org/apache/jk/server/JkCoyoteHandler.java Index: JkCoyoteHandler.java === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/server/JkCoyoteHandler.java,v retrieving revision 1.37 retrieving revision 1.38 diff -u -r1.37 -r1.38 --- JkCoyoteHandler.java14 Mar 2003 00:00:21 - 1.37 +++ JkCoyoteHandler.java14 Mar 2003 00:03:03 - 1.38 @@ -304,7 +304,9 @@ mb=new MessageBytes(); ep.setNote( tmpMessageBytesNote, mb ); } -mb.setString( res.getMessage()); +String message=res.getMessage(); +if( message==null ) message=OK; +mb.setString( message ); c2b.convert( mb ); msg.appendBytes(mb); - 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 JkCoyoteHandler.java
- Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 22, 2002 10:34 PM Subject: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server JkCoyoteHandler.java hgomez 2002/11/22 22:34:48 Modified:jk/java/org/apache/jk/common HandlerRequest.java jk/java/org/apache/jk/server JkCoyoteHandler.java Log: Fix null getRemoteHost. Lasy extraction of ssl certs to speed up jk/ajp13 when under SSL Revision ChangesPath 1.18 +6 -24 jakarta-tomcat-connectors/jk/java/org/apache/jk/common/HandlerRequest.java Index: HandlerRequest.java + // SSL certificate extraction is costy, moved to JkCoyoteHandler +req.setAttribute(SSLSupport.CERTIFICATE_KEY, certString); break; As much as I very much like the switch to constants, this is still wrong. As far back as the Servlet 2.2 spec (aka Tomat 3.3) this is required to be a java.security.cert.X509Certificate []. I'll have to -1 this section of the patch because of this, but the rest looks really good! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
