mod_jk 1.2.6 release - any showstopper ?
Fix the latest Bill fix on lb cookies it seems there is nothing which prevent us from releasing jk 1.2.6. So if nobody reports a show stopper today, I'll start the jk 1.2.6 release tomorrow morning CET. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk 1.2.6 release ? - session tracking cookie
- Original Message - From: Sandy McArthur [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, July 19, 2004 9:15 PM Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie On Jul 19, 2004, at 8:43 AM, Henri Gomez wrote: And since I couldn't delay the release to long, we need a quick reply, so thanks to take a look at it. We've setup a current CVS checkout of mod_jk at http://sp27en1.nerdc.ufl.edu/login.do which is load balancing to our webmail cluster. If you constantly reload the page you'll see it's setting a new JSESSIONID cookie on every request. Yup. Sending the cookie almost always fails to stick. Sending the jsessionid via URL-rewriting always sticks. So it does look like there is a bug with the lb cookie parsing. I can't see by looking at the code what it is however :(. I can probably find a machine that I can hook up with the HEAD code and lb to see what is going wrong, but I can't promise when. If you feel like putting more work into this, adding 'fprintf(stderr,...)' statements should go to the Apache error_log. For comparison https://webmail.ufl.edu/login.do is using mod_jk 1.2.5 load balancing to the same webmail cluster. Yup. This one will always stick with the cookie. Sandy McArthur 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.6 release ? - session tracking cookie
Bill Barker wrote: - Original Message - From: Sandy McArthur [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, July 19, 2004 9:15 PM Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie On Jul 19, 2004, at 8:43 AM, Henri Gomez wrote: And since I couldn't delay the release to long, we need a quick reply, so thanks to take a look at it. We've setup a current CVS checkout of mod_jk at http://sp27en1.nerdc.ufl.edu/login.do which is load balancing to our webmail cluster. If you constantly reload the page you'll see it's setting a new JSESSIONID cookie on every request. Could you send us you workers.properties ? Yup. Sending the cookie almost always fails to stick. Sending the jsessionid via URL-rewriting always sticks. So it does look like there is a bug with the lb cookie parsing. I can't see by looking at the code what it is however :(. I can probably find a machine that I can hook up with the HEAD code and lb to see what is going wrong, but I can't promise when. If you feel like putting more work into this, adding 'fprintf(stderr,...)' statements should go to the Apache error_log. I've got such settings here, with 2 TC 3.3.2. Where did you want me put fprint ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk 1.2.6 release ? - session tracking cookie
On Jul 20, 2004, at 5:27 AM, Henri Gomez wrote: Could you send us you workers.properties ? attached. workers.properties Description: Binary data If you feel like putting more work into this, adding 'fprintf(stderr,...)' statements should go to the Apache error_log. Where did you want me put fprint ? Let us know where you want them and we'll test that code too. Sandy McArthur smime.p7s Description: S/MIME cryptographic signature
Re: mod_jk 1.2.6 release ? - session tracking cookie
I was thinking something like attached. - Original Message - From: Sandy McArthur [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 7:04 AM Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie On Jul 20, 2004, at 5:27 AM, Henri Gomez wrote: Could you send us you workers.properties ? attached. If you feel like putting more work into this, adding 'fprintf(stderr,...)' statements should go to the Apache error_log. Where did you want me put fprint ? Let us know where you want them and we'll test that code too. Sandy McArthur 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.6 release ? - session tracking cookie
I see that attachments are still getting stripped from the list :).
The problem is yet-another-typo. The check for a comma cookie-delimiter
ends up re-setting the returned cookie value to NULL, so the lb thinks that
no cookie was sent. If this attachment comes through, it's the patch for
it. I'll commit it later (PST), if nobody else wants it.
- Original Message -
From: Bill Barker [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Tuesday, July 20, 2004 11:35 AM
Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie
I was thinking something like attached.
- Original Message -
From: Sandy McArthur [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Tuesday, July 20, 2004 7:04 AM
Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie
On Jul 20, 2004, at 5:27 AM, Henri Gomez wrote:
Could you send us you workers.properties ?
attached.
--
--
If
you feel like putting more work into this, adding
'fprintf(stderr,...)'
statements should go to the Apache error_log.
Where did you want me put fprint ?
Let us know where you want them and we'll test that code too.
Sandy McArthur
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]
*** jk_lb_worker.cvsTue Jul 20 11:02:38 2004
--- jk_lb_worker.c Tue Jul 20 12:09:57 2004
***
*** 139,145
if((id_end = strchr(id_start, ';')) != NULL) {
*id_end = '\0';
}
! if((id_start = strchr(id_start, ',')) != NULL) {
*id_end = '\0';
}
return id_start;
--- 139,145
if((id_end = strchr(id_start, ';')) != NULL) {
*id_end = '\0';
}
! if((id_end = strchr(id_start, ',')) != NULL) {
*id_end = '\0';
}
return id_start;
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.6 release ? - session tracking cookie
Bill, Much thanks! We've tested the fixed get_cookie back-ported to mod_jk 1.2.5 and it works well. We'll deploy that version into production tonight but I don't expect any problems. I'll let y'all know if there is. Sandy On Jul 20, 2004, at 3:17 PM, Bill Barker wrote: I see that attachments are still getting stripped from the list :). The problem is yet-another-typo. The check for a comma cookie-delimiter ends up re-setting the returned cookie value to NULL, so the lb thinks that no cookie was sent. If this attachment comes through, it's the patch for it. I'll commit it later (PST), if nobody else wants it. smime.p7s Description: S/MIME cryptographic signature
Re: mod_jk 1.2.6 release ? - session tracking cookie
Sandy McArthur wrote: Thinking on it more, I think I'm full of it and I was confusing the symptoms of two problems that were happening at the same time. Disregard my comments below until I can double check myself. Sandy On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote: On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote: Could you take the latest code in CVS and check to see if it solve your problem ? We took the new get_cookie() implementation from CVS and replaced the one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute of the JSESSIONID cookie weren't being respected and users coudn't do anything in our load balanced setup because they were getting new JSESSIONID cookies on each request. We reverted very quickly so I didn't get a good chance to debug it. Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem with the new get_cookie() in the 1.2.5 version. I've manually followed the new get_cookie() code and it looks right to me but I'm nervous about it for now. I'd like to know if anyone else has had success with the new get_cookie() in a load balanced setup. I'm waiting for your reply to tag and make jk 1.2.6 release. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk 1.2.6 release ? - session tracking cookie
On Jul 19, 2004, at 4:06 AM, Henri Gomez wrote: Sandy McArthur wrote: Thinking on it more, I think I'm full of it and I was confusing the symptoms of two problems that were happening at the same time. Disregard my comments below until I can double check myself. Sandy On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote: On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote: Could you take the latest code in CVS and check to see if it solve your problem ? We took the new get_cookie() implementation from CVS and replaced the one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute of the JSESSIONID cookie weren't being respected and users coudn't do anything in our load balanced setup because they were getting new JSESSIONID cookies on each request. We reverted very quickly so I didn't get a good chance to debug it. Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem with the new get_cookie() in the 1.2.5 version. I've manually followed the new get_cookie() code and it looks right to me but I'm nervous about it for now. I'd like to know if anyone else has had success with the new get_cookie() in a load balanced setup. I'm waiting for your reply to tag and make jk 1.2.6 release. I double checked our setup and our attempt to patch mod_jk 1.2.5 with the new get_cookie implementation and found that request were *not* being forward to the right clone based on the jvmroute part of the JSESSIONID cookie. I have not had time to test a current CVS checkout of mod_jk in a load balanced setup. Sandy McArthur smime.p7s Description: S/MIME cryptographic signature
Re: mod_jk 1.2.6 release ? - session tracking cookie
Sandy McArthur wrote: On Jul 19, 2004, at 4:06 AM, Henri Gomez wrote: Sandy McArthur wrote: Thinking on it more, I think I'm full of it and I was confusing the symptoms of two problems that were happening at the same time. Disregard my comments below until I can double check myself. Sandy On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote: On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote: Could you take the latest code in CVS and check to see if it solve your problem ? We took the new get_cookie() implementation from CVS and replaced the one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute of the JSESSIONID cookie weren't being respected and users coudn't do anything in our load balanced setup because they were getting new JSESSIONID cookies on each request. We reverted very quickly so I didn't get a good chance to debug it. Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem with the new get_cookie() in the 1.2.5 version. I've manually followed the new get_cookie() code and it looks right to me but I'm nervous about it for now. I'd like to know if anyone else has had success with the new get_cookie() in a load balanced setup. I'm waiting for your reply to tag and make jk 1.2.6 release. I double checked our setup and our attempt to patch mod_jk 1.2.5 with the new get_cookie implementation and found that request were *not* being forward to the right clone based on the jvmroute part of the JSESSIONID cookie. I have not had time to test a current CVS checkout of mod_jk in a load balanced setup. Well the patch was release to fix your problem and correct what could be a serious problem in jk 1.2.x and I'd like to know if it's fixed before making the 1.2.6 release. And since I couldn't delay the release to long, we need a quick reply, so thanks to take a look at it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk 1.2.6 release ? - session tracking cookie
- Original Message - From: Sandy McArthur [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, July 19, 2004 1:21 AM Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie On Jul 19, 2004, at 4:06 AM, Henri Gomez wrote: Sandy McArthur wrote: Thinking on it more, I think I'm full of it and I was confusing the symptoms of two problems that were happening at the same time. Disregard my comments below until I can double check myself. Sandy On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote: On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote: Could you take the latest code in CVS and check to see if it solve your problem ? We took the new get_cookie() implementation from CVS and replaced the one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute of the JSESSIONID cookie weren't being respected and users coudn't do anything in our load balanced setup because they were getting new JSESSIONID cookies on each request. We reverted very quickly so I didn't get a good chance to debug it. Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem with the new get_cookie() in the 1.2.5 version. I've manually followed the new get_cookie() code and it looks right to me but I'm nervous about it for now. I'd like to know if anyone else has had success with the new get_cookie() in a load balanced setup. I'm waiting for your reply to tag and make jk 1.2.6 release. I double checked our setup and our attempt to patch mod_jk 1.2.5 with the new get_cookie implementation and found that request were *not* being forward to the right clone based on the jvmroute part of the JSESSIONID cookie. If the UA is sending trailing white-space between the Cookie value and the ';', then the current patch will fail. I don't know of any UAs that do, which is why I didn't bother with stripping it (at least this close to a release date). I have not had time to test a current CVS checkout of mod_jk in a load balanced setup. Sandy McArthur smime.p7s Description: S/MIME cryptographic signature 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.6 release ? - session tracking cookie
On Jul 19, 2004, at 8:43 AM, Henri Gomez wrote: And since I couldn't delay the release to long, we need a quick reply, so thanks to take a look at it. We've setup a current CVS checkout of mod_jk at http://sp27en1.nerdc.ufl.edu/login.do which is load balancing to our webmail cluster. If you constantly reload the page you'll see it's setting a new JSESSIONID cookie on every request. For comparison https://webmail.ufl.edu/login.do is using mod_jk 1.2.5 load balancing to the same webmail cluster. Sandy McArthur smime.p7s Description: S/MIME cryptographic signature
Re: mod_jk 1.2.6 release ? - session tracking cookie
On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote: Could you take the latest code in CVS and check to see if it solve your problem ? We took the new get_cookie() implementation from CVS and replaced the one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute of the JSESSIONID cookie weren't being respected and users coudn't do anything in our load balanced setup because they were getting new JSESSIONID cookies on each request. We reverted very quickly so I didn't get a good chance to debug it. Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem with the new get_cookie() in the 1.2.5 version. I've manually followed the new get_cookie() code and it looks right to me but I'm nervous about it for now. I'd like to know if anyone else has had success with the new get_cookie() in a load balanced setup. Sandy smime.p7s Description: S/MIME cryptographic signature
Re: mod_jk 1.2.6 release ? - session tracking cookie
Thinking on it more, I think I'm full of it and I was confusing the symptoms of two problems that were happening at the same time. Disregard my comments below until I can double check myself. Sandy On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote: On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote: Could you take the latest code in CVS and check to see if it solve your problem ? We took the new get_cookie() implementation from CVS and replaced the one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute of the JSESSIONID cookie weren't being respected and users coudn't do anything in our load balanced setup because they were getting new JSESSIONID cookies on each request. We reverted very quickly so I didn't get a good chance to debug it. Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem with the new get_cookie() in the 1.2.5 version. I've manually followed the new get_cookie() code and it looks right to me but I'm nervous about it for now. I'd like to know if anyone else has had success with the new get_cookie() in a load balanced setup. Sandy smime.p7s Description: S/MIME cryptographic signature
Re: Ready for mod_jk 1.2.6 release?
Hi, I have 2 unresolved: snprintf and vsnprintf. With Apache-2.0 we should use apr_snprintf and apr_vsnprintf for Apache-1.3 should I add ersatz routines? yes; on NetWare we have also with Apache 1.3 another system lib which lacks support of those two; so would be cool if we could add jk_snprintf() and jk_vsnprintf(); and perhaps also use these consequently with all 1.3 compilations, and not only those platforms which dont have these in the OS... do you have already code to implement them? Guenter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
Günter Knauf wrote: Hi, I have 2 unresolved: snprintf and vsnprintf. With Apache-2.0 we should use apr_snprintf and apr_vsnprintf for Apache-1.3 should I add ersatz routines? yes; on NetWare we have also with Apache 1.3 another system lib which lacks support of those two; so would be cool if we could add jk_snprintf() and jk_vsnprintf(); and perhaps also use these consequently with all 1.3 compilations, and not only those platforms which dont have these in the OS... do you have already code to implement them? Sure see in apr/build/jlibtool.c ;-) But we need a little in the configure to check for snprintf and vsnprintf. Guenter. - 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: Ready for mod_jk 1.2.6 release?
Hi, Sure see in apr/build/jlibtool.c ;-) But we need a little in the configure to check for snprintf and vsnprintf. why? just make it mandatory for 1.3, this avoids all the hassle, plus has the benefit that we have a implementation we can trust; f.e. what if config detects the functions in the os, and then they turn out broken just do a if APACHE2 use_apr else use_ourown end Guenter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
Rainer Jung wrote: Hi, the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. The 1.2 branch is still the preferred branch for combination with apache 1.3. Is there any volunteer to make an official 1.2.6 release? I do hope so ;-) I could works on it if nobody else has time to act as release manager. Feedback welcome of course, especially on possible blocking bugs... Another good argument: The documentation of the new features is already there (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/workershowto.html), so no additional work and furthermore, the documentation up to now does not mention, that all these features are still not available, because 1.2.6 has never been released. Many thanks to whoever wrote that document. I worked with a cvs build under solaris for some weeks without problems, but for production purposes people need an official release. The last changes in the native jk code is more then 6 weeks old and there is no code change activity at the moment. So this might be a good point in time to release mod_jk 1.2.6. Looking forward for positive feedback Rainer Jung - 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: Ready for mod_jk 1.2.6 release?
Service Client Fnac.com wrote: Chère Cliente, Cher Client, Merci de nous avoir contactés. Vous venez d'envoyer un message à une adresse ne permettant pas de recevoir d'e-mail. Pour trouver les réponses à vos questions sur vos commandes, sur les produits, sur le site, consultez nos pages d'aide en ligne en cliquant sur : http://www.fnac.com/Help/A01.asp Vous pouvez également suivre en direct l'évolution de vos commandes en cours, en consultant la rubrique Vos Commandes en un clin d'oeil en cliquant sur : https://www.fnac.com/Account/Profil/default.asp Nous espérons que ces pages vous apporteront toutes les informations nécessaires. Dans le cas contraire, vous pouvez nous contacter par e-mail en cliquant sur le lien : http://www.fnac.com/Service_Client/FnacSUGG.asp Merci de votre fidélité a www.fnac.com Très cordialement, Well I don't see why the Client Support of Fnac is subscribed here, so I strongly suggest mailing list manager to remove it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Ready for mod_jk 1.2.6 release?
Chère Cliente, Cher Client, Merci de nous avoir contactés. Vous venez d'envoyer un message à une adresse ne permettant pas de recevoir d'e-mail. Pour trouver les réponses à vos questions sur vos commandes, sur les produits, sur le site, consultez nos pages d'aide en ligne en cliquant sur : http://www.fnac.com/Help/A01.asp Vous pouvez également suivre en direct l'évolution de vos commandes en cours, en consultant la rubrique Vos Commandes en un clin d'oeil en cliquant sur : https://www.fnac.com/Account/Profil/default.asp Nous espérons que ces pages vous apporteront toutes les informations nécessaires. Dans le cas contraire, vous pouvez nous contacter par e-mail en cliquant sur le lien : http://www.fnac.com/Service_Client/FnacSUGG.asp Merci de votre fidélité a www.fnac.com Très cordialement, L'équipe Fnac.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Ready for mod_jk 1.2.6 release?
Hi, a mod_jk 1.2.6 release would be highly welcome. We are using cvs head in production for a couple of month now without problems. thanks, Hans -Ursprungliche Nachricht- Von: Henri Gomez [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 8. Juli 2004 10:01 An: Tomcat Developers List Betreff: Re: Ready for mod_jk 1.2.6 release? Rainer Jung wrote: Hi, the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. The 1.2 branch is still the preferred branch for combination with apache 1.3. Is there any volunteer to make an official 1.2.6 release? I do hope so ;-) I could works on it if nobody else has time to act as release manager. Feedback welcome of course, especially on possible blocking bugs... Another good argument: The documentation of the new features is already there (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/workershow to.html), so no additional work and furthermore, the documentation up to now does not mention, that all these features are still not available, because 1.2.6 has never been released. Many thanks to whoever wrote that document. I worked with a cvs build under solaris for some weeks without problems, but for production purposes people need an official release. The last changes in the native jk code is more then 6 weeks old and there is no code change activity at the moment. So this might be a good point in time to release mod_jk 1.2.6. Looking forward for positive feedback Rainer Jung - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
Henri Gomez wrote: Well I don't see why the Client Support of Fnac is subscribed here, so I strongly suggest mailing list manager to remove it. I'm on a modem this week :/ Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
Henri Gomez wrote: Rainer Jung wrote: Hi, the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. The 1.2 branch is still the preferred branch for combination with apache 1.3. Is there any volunteer to make an official 1.2.6 release? I do hope so ;-) I could works on it if nobody else has time to act as release manager. Feedback welcome of course, especially on possible blocking bugs... Make a build on latest from CVS, and it works on both Linux Fedora Core 2 and iSeries (AS/400) V5R2. Could someone works on an Windows version for Apache 2 ? Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
Henri Gomez wrote: Rainer Jung wrote: Hi, the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. The 1.2 branch is still the preferred branch for combination with apache 1.3. Is there any volunteer to make an official 1.2.6 release? I do hope so ;-) I could works on it if nobody else has time to act as release manager. Feedback welcome of course, especially on possible blocking bugs... I am porting it to my favorite EBCDIC mainframe and I still need sometime to get it working. Another good argument: The documentation of the new features is already there (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/workershowto.html), so no additional work and furthermore, the documentation up to now does not mention, that all these features are still not available, because 1.2.6 has never been released. Many thanks to whoever wrote that document. I worked with a cvs build under solaris for some weeks without problems, but for production purposes people need an official release. The last changes in the native jk code is more then 6 weeks old and there is no code change activity at the moment. So this might be a good point in time to release mod_jk 1.2.6. Looking forward for positive feedback Rainer Jung - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
Ditto. I started just using CVS-latest for mod_jk and mod_jk2 some time back as the gap between new, stable feature/fix content and release labels was just too great. Overall CVS-latest has been more stable than the last labels for some time now David Rees wrote: Rainer Jung wrote: the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. I would like to see one. I am already using CVS to get the new features and bug fixes, but an official release would be nice. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
jean-frederic clere wrote: Henri Gomez wrote: Rainer Jung wrote: Hi, the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. The 1.2 branch is still the preferred branch for combination with apache 1.3. Is there any volunteer to make an official 1.2.6 release? I do hope so ;-) I could works on it if nobody else has time to act as release manager. Feedback welcome of course, especially on possible blocking bugs... I am porting it to my favorite EBCDIC mainframe and I still need sometime to get it working. I have 2 unresolved: snprintf and vsnprintf. With Apache-2.0 we should use apr_snprintf and apr_vsnprintf for Apache-1.3 should I add ersatz routines? Another good argument: The documentation of the new features is already there (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/workershowto.html), so no additional work and furthermore, the documentation up to now does not mention, that all these features are still not available, because 1.2.6 has never been released. Many thanks to whoever wrote that document. I worked with a cvs build under solaris for some weeks without problems, but for production purposes people need an official release. The last changes in the native jk code is more then 6 weeks old and there is no code change activity at the moment. So this might be a good point in time to release mod_jk 1.2.6. Looking forward for positive feedback Rainer Jung - 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] - 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]
Ready for mod_jk 1.2.6 release?
Hi, the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. The 1.2 branch is still the preferred branch for combination with apache 1.3. Is there any volunteer to make an official 1.2.6 release? I do hope so ;-) Another good argument: The documentation of the new features is already there (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/workershowto.html), so no additional work and furthermore, the documentation up to now does not mention, that all these features are still not available, because 1.2.6 has never been released. Many thanks to whoever wrote that document. I worked with a cvs build under solaris for some weeks without problems, but for production purposes people need an official release. The last changes in the native jk code is more then 6 weeks old and there is no code change activity at the moment. So this might be a good point in time to release mod_jk 1.2.6. Looking forward for positive feedback Rainer Jung - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. +1 for releasing as son as possible; we missed already the last service pack on NetWare and had to ship cvs code... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ready for mod_jk 1.2.6 release?
+1 important features to help customers to have a stable loadbalancer... At Linux Suse 9.0 it works fine. regards Peter Rainer Jung schrieb: Hi, the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. The 1.2 branch is still the preferred branch for combination with apache 1.3. Is there any volunteer to make an official 1.2.6 release? I do hope so ;-) Another good argument: The documentation of the new features is already there (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/workershowto.html), so no additional work and furthermore, the documentation up to now does not mention, that all these features are still not available, because 1.2.6 has never been released. Many thanks to whoever wrote that document. I worked with a cvs build under solaris for some weeks without problems, but for production purposes people need an official release. The last changes in the native jk code is more then 6 weeks old and there is no code change activity at the moment. So this might be a good point in time to release mod_jk 1.2.6. Looking forward for positive feedback Rainer Jung - 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: Ready for mod_jk 1.2.6 release?
Rainer Jung wrote: the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. Since then there have been important improvements (CPing/CPong and recovery_options). Especially recovery_options is very useful in transparent administration (start/stop) of cluster nodes. I would like to see one. I am already using CVS to get the new features and bug fixes, but an official release would be nice. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk 1.2.6 release
On Sat, Feb 14, 2004 at 07:18:54PM +0100, Henri Gomez wrote: Mike Anderson wrote: I'd like to see this since Henri's timeout fixes really help some issues that we've seen with apps that hang Tomcat threads. It might be good to wait until the POST data issues are resolved (see threads titled POST recovery in JK and JK2 HEAD and Mod_JK2 - Default Worker) Glenn, you could works on the 1.2.6 release, since 2.0.4 will be released next week, what about the week after ? Sure, if its ready. I would like to see the bug fix for that POST bug finalized before doing a release. You have my +0 for RM ;-) Thanks, I think. ;-) -- 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: mod_jk 1.2.6 release
Mike Anderson wrote: I'd like to see this since Henri's timeout fixes really help some issues that we've seen with apps that hang Tomcat threads. It might be good to wait until the POST data issues are resolved (see threads titled POST recovery in JK and JK2 HEAD and Mod_JK2 - Default Worker) Glenn, you could works on the 1.2.6 release, since 2.0.4 will be released next week, what about the week after ? You have my +0 for RM ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mod_jk 1.2.6 release
I have noticed a number of bug fixes and patches to mod_jk 1.2. Whenever you think it is ready I can act as the release manager for a mod_jk 1.2.6 if you want me to. Regards, Glenn -- 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: mod_jk 1.2.6 release
I'd like to see this since Henri's timeout fixes really help some issues that we've seen with apps that hang Tomcat threads. It might be good to wait until the POST data issues are resolved (see threads titled POST recovery in JK and JK2 HEAD and Mod_JK2 - Default Worker) Mike Anderson [EMAIL PROTECTED] 2/13/2004 2:13:03 PM I have noticed a number of bug fixes and patches to mod_jk 1.2. Whenever you think it is ready I can act as the release manager for a mod_jk 1.2.6 if you want me to. Regards, Glenn -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
