Ok so I think I found the setting that "fixes" this.
The external app's "Max Idle Time" should be set to -1 so that none of the sockets get killed to free up resources.
However, this results in a lot of child lsphp5 processes stacking up taking up RAM, which I would like to avoid if possible.
It sounds like this might be a bug - the fact that the socket gets killed to free up resources should not result in a 503 next time someone requests a page from that virtual host. Is there another configuration setup that I'm missing that fixes this?
Last edited by Ghan_04; 02-19-2012 at 04:54 PM..