Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: 2.4.1 in a production environment |
|
| Author |
|
tguerin
Joined: 04 Apr 2012
Posts: 2
|
 Posted: Thu 05 Apr '12 11:53 Post subject: 2.4.1 in a production environment |
 |
|
Hi,
I'd like to use version 2.4.1 because it fixes a cache_disk bug (that only affects 2.2.x Windows versions), but as no official binaries are provided (and there isn't any visibility as to when/if they will ever be provided), I'm considering using the ones provided here.
From what I've gathered, apacheLounge's binaries are equivalent (if not better because VC10 is used) to the ones that were provided by Apache. I also noted that this site uses its binaries to run.
My question goes to the users of these 2.4.1 binaries: do you consider them production-ready? Or should I stick with 2.2.22 for the time being?
My main concern here is the warning on Apache's site:
| Quote: | | Important: Windows users: AcceptFilter None has replaced Win32DisableAcceptEx and the feature appears to have interoperability issues with mod_ssl. Apache 2.4.1 may not yet be suitable for all Windows servers. |
I don't need SSL, but this leaves me wondering if there are other bugs preventing the use of this version in a production environment. |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
| Posted: Thu 05 Apr '12 12:57 Post subject: |
|
|
Tons of users are running it already in production for a few months. When I see the problems reported (primarly config/user faults) then it is even better then 2.2. No problem to use in Producton, except SSL users can have issues..
When you not use SSL and getting errors in the log like for example: Asynchronous AcceptEx failed. Then you had to add in 2.2 the Win32DisableAcceptEx directive, in 2.4 it is now AcceptFilter http none, also advised to have EnableSendfile Off and EnableMMAP Off.
When you use SSL, the AccepFilter https none is broken, so when you get AcceptEx errors in the log, then you have bad luck. Then you can use 2.2 or set 2.2 in front (Reverse Proxy) of 2.4.
Steffen |
|
| Back to top |
|
tguerin
Joined: 04 Apr 2012
Posts: 2
|
| Posted: Fri 06 Apr '12 10:50 Post subject: |
|
|
| Ok, thanks for the answer! |
|
| Back to top |
|
|
|
|
|
|
