i was wondering what the state of the checked in code is for mod_jk. the last tag on jk was 1.2.5 after which (i assume) there have been several checkins.
would you recommend pushing out a cvs built mod_jk to production (probably unsafe, right) or should we wait for the next tagged, jakarta-blessed, deemed stable mod_jk? (i guess i answered my question... any thoughts, gut-feelings, recommendations anyone?) apu > On Fri, February 13, 2004 1at 1:03 am, Chris Pennock wrote: >> >> I have recently encountered a bug in the interaction between mod_jk and >> Tomcat. In brief, Tomcat does not get the POST data from mod_jk >> following >> failover from one Tomacat node to another. >> >> Also, here is a link to the bug in Apache's Bugzilla: >> http://issues.apache.org/bugzilla/show_bug.cgi?id=24882 > > It's should be fixed in CVS. Try pulling the latest code and see if it > fixes it for you and post your results in the bug, the developers would > love to hear about it. > > -Dave > > --------------------------------------------------------------------- > 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]
