Re: Tagging tomcat-native 1.1.8
Peter Rossbach wrote: Hi I have test to compile apr at mac os x 10.4..8 intel and get following warning: src/network.c:449: warning: pointer targets in passing argument 2 of 's-net-send' differ in signedness OK. This should be resolved. Rely don't understand the vast universe of compilers that could impose such a warning. The unsigned char should always be mapped to char without warning. I really see no how the size of 'unsigned char' and size of 'char' could be different so that warning could be issued. Weired! Other problem is that poller are not created: 11.12.2006 20:17:26 org.apache.tomcat.util.net.AprEndpoint allocatePoller INFO: Failed to create poller with specified size of 8192 Looks like OS/X doesn't allow default 8192 poller size. The solution is either to increase the ulimit or add the pollerSize=xxx to the APR connector. Can you see what is default maximum limit for that by lowering down the pollerSize in 1024 decrements on OS/X, so we can make that OS related like on WIN32/WIN64? If it's only ulimit dependent, then no patch should be needed. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging tomcat-native 1.1.8
+1 2006/12/11, Mladen Turk [EMAIL PROTECTED]: Hi, I'll tag the 1.1.8 later today and put the distro files in regular places, so they can be used for Tomcat builds. BTW, can we again consider to use the minimum version required to that version (1.1.8). Although the API is compatible with 1.1.3 version, the all versions between 1.1.3 and 1.1.8 are broken for AjpAprConnector except the current Tomcat trunk. Think it'll lower down the support questions, because user will be forced to install the 1.1.8 version instead wondering why the previous version doesn't work or eats CPU. Regards, Mladen. - 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: Tagging tomcat-native 1.1.8
Mladen Turk wrote: Hi, I'll tag the 1.1.8 later today and put the distro files in regular places, so they can be used for Tomcat builds. BTW, can we again consider to use the minimum version required to that version (1.1.8). Although the API is compatible with 1.1.3 version, the all versions between 1.1.3 and 1.1.8 are broken for AjpAprConnector except the current Tomcat trunk. Think it'll lower down the support questions, because user will be forced to install the 1.1.8 version instead wondering why the previous version doesn't work or eats CPU. My little tweak will most likely be ported back to 5.5.x. As a result, when you install a new build, you'll get a warning, and the code will not use the problematic method by default. As a result, the forced upgrade is a waste of time for most. So I am against this plan. I've stated my position already: unless there's an API change that was needed, the minimum version number should not be upgraded. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging tomcat-native 1.1.8
Remy Maucherat wrote: Mladen Turk wrote: My little tweak will most likely be ported back to 5.5.x. As a result, when you install a new build, you'll get a warning, and the code will not use the problematic method by default. As a result, the forced upgrade is a waste of time for most. OK. So I am against this plan. I've stated my position already: unless there's an API change that was needed, the minimum version number should not be upgraded. Also fine. The problem we have is the 1.1.5 that eats the CPU. The 1.1.3 as minimum means that any version up to recommended is allowable, which is not the real case. Anyhow, this should at least be clearly documented if not enforced. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging tomcat-native 1.1.8
On Dec 11, 2006, at 5:00 AM, Mladen Turk wrote: Hi, I'll tag the 1.1.8 later today and put the distro files in regular places, so they can be used for Tomcat builds. BTW, can we again consider to use the minimum version required to that version (1.1.8). Although the API is compatible with 1.1.3 version, the all versions between 1.1.3 and 1.1.8 are broken for AjpAprConnector except the current Tomcat trunk. Think it'll lower down the support questions, because user will be forced to install the 1.1.8 version instead wondering why the previous version doesn't work or eats CPU. +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
