Hi, the tests for mod_jk 1.2.16 had a couple of results, unfortunately with one bad regression bug:
1) The status worker (aka jkmanager) had a bug, which resulted in double locking and hanging when a user tried to change the important attributed "disabled" or "stopped" (and also for the new one "distance"). The fix was obvious, but I think this is a show-stopper for 1.2.16, since jkmanager is really helpful, and one of the most interesting things is to be able to change disabled/stopped. (Reported by Mohan2005) 2) Henri Gomez reported a problem on AS400 related to APR MUTEX. This is not a regression, it already showed up for 1.2.15, but had never gotten fixed. William already offered to discuss this and [EMAIL PROTECTED], so I will soon report the error there and I hope Henri will be able to give more details if necessary. I don't think this is a showstopper, since it is no regression. I added a fix (workaround). 3) Martin Kaemer reported a problem with SHELL detection during configure when not using gmake. He was able to get it build nevertheles by setting SHELL explicitely and using gmake. I'm not sure, if this is really a mod_jk bug, but I will try to go deeper into it next week. Not a showstopper. 4) Mladen Turk is adding some changes to the network connection handling. He would need to comment on these by himself. As a result of 1) I propose to roll 1.2.17 as soon, as Mladen has done 4) (assuming it's just minor stuff). For the next feature release I will prepare the use of release candidates, because I think then the naming will look more familiar to users. I'll let 1.2.17 out there for tests a short time (assuming, that not many people will be retesting) and then start a release vote. Comments on this? Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
