UCM, mod_wl_ohs and http response
Some extensive testing, “maybe” some code decompiling, and some talking to an great ACS consultant about nice error pages for UCM when using a HTTP front-end ended in this statement:
If we add “HttpSevereErrorFirstLine=HTTP/1.1 400 Bad Request” in the config.cfg and restart the Content Server, the actual error message is seen instead of the bridge error. This undocumented parameter overrides the default 503 response sent by the Content Server in case of an error to 400.
Apache complains about the bridge error when a 503 response is sent and doesn’t when it’s something like HTTP/1.1 400 Bad Request.
This feature was tested on Universal Content Manager (UCM) 11.1.1.4.
hope this helps 
Advertisement
Found this after a google search. We’re getting 503 errors consistently once we simulate >100 users off our Oracle content server. Unfortunately this didn’t help but thats probably because we misunderstood the context.
matt
November 19, 2011 at 4:13 am