On 28.02.2012 07:23, Harsimranjit singh Kler wrote:
Hi Thanks for reply i have these setting for build:: Server version: Apache/2.2.17 (Unix) Server built:Apr 19 2011 21:11:59 Server's Module Magic Number: 20051115:25 Server loaded:APR 1.4.2, APR-Util 1.3.10 Compiled using: APR 1.4.2, APR-Util 1.3.10 Architecture:64-bit Server MPM:Worker threaded:yes (fixed thread count) forked:yes (variable process count 1)i am using worker mpm and had done lot performance tests to set parameters like start server,ServerLimit ,MaxClients etc.So now i can use same parameter values or again i have to go through that tests for values?
You can and 2.4 will happily run with the known worker MPM, but the new default MPM is caled "event" and will need new tuning. Some of the parameter names (like MaxClients) are deprecated now, because their names are missleading, but they still will work.
2)I have plan to use SSL as well so all required ssl libs are available and compatible?
mod_ssl will now only support OpenSSL (I think starting at 0.9.7, but is also fine with 0.9.8 and 1.0.0 and likely also 1.0.1 beta).
3) Using modjk any change for that?
I added two small fixes to mod_jk for use with 2.4 to the current code, but those are not yet released. A release should not be far away, but you can also use the latest version and apply the following two patches yourself:
http://svn.apache.org/viewvc?diff_format=h&view=revision&revision=1022975 (the real patch is: http://svn.apache.org/viewvc/tomcat/jk/trunk/native/apache-2.0/mod_jk.c?r1=1022975&r2=1022974&pathrev=1022975&view=patch ) and http://svn.apache.org/viewvc?diff_format=h&view=revision&revision=1293818 (the real patch is: http://svn.apache.org/viewvc/tomcat/jk/trunk/native/apache-2.0/mod_jk.c?r1=1293818&r2=1293817&pathrev=1293818&view=patch ) Regards, Rainer --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|