1) This Apache vhost is proxying traffic with mod_proxy (simply ProxyPass rule) to an oc4j application server where the flash is hosted. The other vhosts serve a variety of static content, run multiple rewrite rules, etc - this is the "simple" vhost 2) No, only the single vhost is providing flash content. 3) This vhost is the only one that receives traffic from the F5 device. All of the other traffic to the other vhosts is edge traffic - no intermediate 3rd party devices outside of firewalls / routers are involved. 4) I'll assume you're asking for Start servers, max threads, etc: ServerLimit 80 ThreadLimit 30 StartServers 3 MaxClients 2000 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 ThreadStackSize 2097152 Agreed on 200 current being nothing - we only pull about 4 million hits / day through that vhost and its a trivial amount of cpu and memory utilization. However, there are no issues at traffic loads less than 100 concurrent so it does appear to be load based. -----Original Message----- From: Jim Jagielski [mailto:jim@xxxxxxxxxxx] Sent: Tuesday, August 27, 2013 11:08 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: Timeouts after upgrading from 2.2.23 to 2.4.6 1) Is the Flash content hosted on the server running Apache or is Apache the front-end of the Flash content provider? 2) Are all vhosts also proving Flash content? 3) Is there anything "special" about the vhost? 4) What are the typical server settings for the Worker MPM? 200 concurrent users is nothing... On Aug 27, 2013, at 10:11 AM, "Spangler, Tim" <Tim.Spangler@xxxxxxx> wrote: > Hello, > > I recently upgraded from Apache 2.2.23 to Apache 2.4.6, and after the upgrade, we're seeing random timeouts / drops on Flash content. The problem also exhibited itself on Apache 2.4.3, so it doesn't appear to be limited to just 2.4.6. This is in an enterprise environment and the problem only occurs during peak times where there are over 200 concurrent users, and unfortunately, our non production environments with much less load do not exhibit this problem. > > Only a single virtual host of 6 is exhibiting this problem, and it is fronted by F5 Big IP that I do not have access to. Rolling back to Apache 2.2.23 resolves the random timeouts, but I would like to go forward with 2.4 as I would eventually prefer to be running the Event MPM (I'm still running MPM worker at this time to keep changes to a minimum). I've been over the Apache upgrade doc, and I don't see any changes that should cause problems with Flash or F5, but I'm out of other ideas at this time. Any advise out there? > > Thanks, > > Tim > > ---------------------------------------------------------------------- > This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|