DO NOT REPLY [Bug 40855] - JK 1.2.19 letter case problem in uriworkermap

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] - JK 1.2.19 on IIS6: Worker reference doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40716] New: - JK 1.2.19 on IIS6: Worker reference doesn't work

gzilla/show_bug.cgi?id=40716 Summary: JK 1.2.19 on IIS6: Worker reference doesn't work Product: Tomcat 5 Version: Unknown Platform: PC OS/Version: Windows Server 2003 Status: NEW Severity: normal Priority: P2

Re: Releasing JK 1.2.19

On 9/14/06, Rainer Jung <[EMAIL PROTECTED]> wrote: David Rees wrote: OK. I would propose that adding a new feature that allows you to map all requests matching .*;jsessionid=.* to mod_jk would be a worthy feature. I am willing to work on a patch if no mod_jk developers are interested. Should I o

Re: Releasing JK 1.2.19

Build works on i5/OS v5R3, I'm waiting now for its activation by my IT team. Regards 2006/9/15, Henri Gomez <[EMAIL PROTECTED]>: No problem for me on Linux Suse SLES 9 and Power PC. Checking iSeries build now >2006/9/14, Rainer Jung <[EMAIL PROTECTED]>: > Please open a Bugzilla for an enhance

Re: Releasing JK 1.2.19

No problem for me on Linux Suse SLES 9 and Power PC. Checking iSeries build now 2006/9/14, Rainer Jung <[EMAIL PROTECTED]>: Please open a Bugzilla for an enhancement request. Thanks for pointing it out. David Rees wrote: > On 9/14/06, Mladen Turk <[EMAIL PROTECTED]> wrote: >> > So what do you

Re: Releasing JK 1.2.19

Please open a Bugzilla for an enhancement request. Thanks for pointing it out. David Rees wrote: On 9/14/06, Mladen Turk <[EMAIL PROTECTED]> wrote: > So what do you do when you have multiple virtualhosts mapped to > different workers? Please don't split hair :) In that case use the JkMount/J

Re: Releasing JK 1.2.19

On 9/14/06, Mladen Turk <[EMAIL PROTECTED]> wrote: > So what do you do when you have multiple virtualhosts mapped to > different workers? Please don't split hair :) In that case use the JkMount/JkUnMount combinations to separate the resources served by Httpd. Less than ideal, but this whole i

Re: Releasing JK 1.2.19

David Rees wrote: Have you tried? SetHandler jakarta-servlet The worker used will be the first one in worker.list if you explicitly set the handler. So what do you do when you have multiple virtualhosts mapped to different workers? Please don't split hair :) In that case use the JkM

Re: Releasing JK 1.2.19

On 9/13/06, Mladen Turk <[EMAIL PROTECTED]> wrote: David Rees wrote: > I'm using this config in Apache: > > JkMount /*.jsp tomcatlb > > JkMount tomcatlb > Have you tried? SetHandler jakarta-servlet The worker used will be the first one in worker.list if you explicitly set the handler.

Re: Releasing JK 1.2.19

David Rees wrote: Ok, I'm pretty sure this is a real bug (though not a new one, mod_jk back to 1.2.15 behaves the same). This not an bug. I'm using this config in Apache: JkMount /*.jsp tomcatlb JkMount tomcatlb Have you tried? SetHandler jakarta-servlet The worker used will be

Re: Releasing JK 1.2.19

Ok, I'm pretty sure this is a real bug (though not a new one, mod_jk back to 1.2.15 behaves the same). I'm using this config in Apache: JkMount /*.jsp tomcatlb JkMount tomcatlb The goal of this example to have Tomcat serve all .jsp files and URL which looks like it has been rewritten with th

Re: Releasing JK 1.2.19

On 9/13/06, Rainer Jung <[EMAIL PROTECTED]> wrote: Anything in the mod_jk log? [error] ajp_service::jk_ajp_common.c (1879): (pepper7) Connecting to tomcat failed. Tomcat is probably not started or is listening on the wrong port Tomcat is running, the mod_jk log level was set to error You mea

Re: Releasing JK 1.2.19

This is not a known feature. Anything in the mod_jk log? You mean "first hit" after restart, or after a time of inactivity? Platform? Server version? The new svn HEAD code gives the ability to log useful state info of the LB in the access logs, so you can more easily find out, how often and wh

Re: Releasing JK 1.2.19

Anyone else seeing a problem where sometimes the first hit returns a 503 and shows the worker recovering? Waiting for the recovery period to go and the worker is ok. This is a simple load balanced worker with only one child worker. Unfortunately I can't reliably reproduce this, it seems to happen

Re: Releasing JK 1.2.19

I updated the testing snapshot tarball after Peters report, and set the link to a more durable http://people.apache.org/~rjung/mod_jk-1.2.19-dev/ Regards, Rainer Peter Rossbach wrote: Hi Mladen and Rainer, sometimes I see a small time a strange artifact: start apache look at jkstatus a

Re: Releasing JK 1.2.19

Hi Mladen and Rainer, sometimes I see a small time a strange artifact: start apache look at jkstatus all worker show state N/A all backend tomcats are stopped access a URL look at jkstatus all worker show state ERR access URL again all worker show state REC (very nice new

Re: Releasing JK 1.2.19

In preparation of release 1.2.19 of tomcat-connnectors (including mod_jk) I made the actual HEAD of the code available for download and testing under http://people.apache.org/~rjung/mod_jk-1.2.19-442987/ This is not an official release, but another opportunity to give the code a quick try bef

Re: Releasing JK 1.2.19

Yes, I'm willing and I've got time to cut a release during the weekend. I'll put a HEAD tarball on people.apache.org during the next hour and announce that on tomcat-dev, so that interesting parties have another chance of giving it a quick try (since wwe've got again a lot of changes since the

Releasing JK 1.2.19

Hi, Seems we had a pretty long test window. Can we schedule the release by the end of this week? Rainer, are you still willing to act as the RM for 1.2.19? Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additi

Re: JK 1.2.19

Rainer Jung wrote: OK, so - what's the show stopper: the rewrite windows things? If yes, I would suggest to release this one patch without *any* of the changes I did last week, because I hope, that this release would need no changes. Can you update the changelog.xml so we can see what has be

Re: JK 1.2.19

On Aug 25, 2006, at 7:55 AM, Rainer Jung wrote: - Passing back child worker names, lb_values and states from lb to apache via notes entries, such that you can easily log the names and states of the target workers via LogFormats (standard mod_log_config feature). This is very interesting to track

Re: JK 1.2.19

On Aug 25, 2006, at 6:02 AM, Mladen Turk wrote: Hi, There is one serious bug in 1.2.18 that makes it unusable for IIS if there is a missing optional directive (rewrite_rule_file). Since we had already lots of commits fixing various problems, 1.2.19 is something we should cut pretty soon. Any

Re: JK 1.2.19

OK, so - what's the show stopper: the rewrite windows things? If yes, I would suggest to release this one patch without *any* of the changes I did last week, because I hope, that this release would need no changes. Rainer Mladen Turk schrieb: > Rainer Jung wrote: >> >> I would then make a snaps

Re: JK 1.2.19

Rainer Jung wrote: I would then make a snapshot available on dev, such that interested parties can compile and check, and could start a formal release process a week later. I know, that new features impose new risk, on the other hand the release process does also consume some energy, so persona

Re: JK 1.2.19

Hi all, I plan to commit four more changes during the weekend. 2 of them are already coded and running, the other 2 ones I still need to implement. Most of the commits I did this week were only preparations for these functionally bigger ones. Already done but not committed: - Passing back child

Re: JK 1.2.19

+1. And general kudos regarding the recent energy around the connectors. Yoav On 8/25/06, Mark Thomas <[EMAIL PROTECTED]> wrote: Mladen Turk wrote: > Hi, > > There is one serious bug in 1.2.18 that makes > it unusable for IIS if there is a missing optional > directive (rewrite_rule_file). Tha

Re: JK 1.2.19

Mladen Turk wrote: > Hi, > > There is one serious bug in 1.2.18 that makes > it unusable for IIS if there is a missing optional > directive (rewrite_rule_file). Thanks for your message on the users list about this. > Since we had already lots of commits fixing various > problems, 1.2.19 is somet

Re: JK 1.2.19

+0 2006/8/25, Mladen Turk <[EMAIL PROTECTED]>: Hi, There is one serious bug in 1.2.18 that makes it unusable for IIS if there is a missing optional directive (rewrite_rule_file). Since we had already lots of commits fixing various problems, 1.2.19 is something we should cut pretty soon. Any c

JK 1.2.19

Hi, There is one serious bug in 1.2.18 that makes it unusable for IIS if there is a missing optional directive (rewrite_rule_file). Since we had already lots of commits fixing various problems, 1.2.19 is something we should cut pretty soon. Any comments or pending work? I would like that we make