We┬┤re using apache (2., with ssl) to proxy the demands to some web service placed on weblogic. We've mod_wl.so installed, and all sorts of works fine with small demands. However, with bigger demands (say, 300 KB), the apache stalls and display this error message:

"Failure of server APACHE bridge: No After sales Sever readily available for connections": timed out after 20 seconds or idempotent is placed to off."

We replicate the scenario in another server, and also the error continues (rather than "20 seconds", it states "thirty secondsInch for the similar request).

How do i avoid this size limitation? Could it be a bug in mod_wl.so? Could it be a config value that's missing? (Like a side note, the net service works fine when examined directly from the weblogic console, regardless of how large the file)

Thank you for any help!

UPDATE: transformed to mod_wl_20.so with same results, this is actually the slice of the log:

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Content-Length]=[352196]

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Connection]=[Keep-Alive]

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[WL-Proxy-SSL]=[true]

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[WL-Proxy-Client-IP]=[163.247.57.10]

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Proxy-Client-IP]=[163.247.57.10]

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-Submitted-For]=[163.247.57.10]

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[30]

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-WebLogic-Request-ClusterInfo]=[true]

Get married Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[x-weblogic-cluster-hash]=[2Ik836PQKnD7XHQ2RcWGOWkcRRA]

Get married Sep 28 11:27:37 2011 <15359131722005124> operation WRITE unsuccessful on fd 23: revents=0x00000018

Get married Sep 28 11:27:37 2011 <15359131722005124> IO TImed out error

Get married Sep 28 11:27:37 2011 <15359131722005124> Publish timed to the server 10.182.5.5:7005

Get married Sep 28 11:27:37 2011 <15359131722005124> ***Exception type [WRITE_ERROR_TO_SERVER] (Publish ti mediterranean to the server 10.182.5.5:7005 ) elevated at line 152 of ap_proxy.cpp

Get married Sep 28 11:27:37 2011 <15359131722005124> error delivering headers or Publish Data to WebLogic, sys er r#: [] sys errmsg [Success]

Get married Sep 28 11:27:37 2011 <15359131722005124> Marking 10.182.5.5:7005 badly

Get married Sep 28 11:27:37 2011 <15359131722005124> got exception in sendRequest phase: WRITE_ERROR_TO_SER VER [os error=, line 152 of ap_proxy.cpp]: Publish timed to the server 10.182.5.5:7005 at line 2994

Get married Sep 28 11:27:37 2011 <15359131722005124> Failing over after WRITE_ERROR_TO_SERVER exception in sendRequest()

Get married Sep 28 11:27:37 2011 <15359131722005124> attempt #1 from a max of 10

Get married Sep 28 11:27:37 2011 <15359131722005124> Not good servers left within the general list, reverting ba ck towards the static list

Get married Sep 28 11:27:37 2011 <15359131722005124> Host removed from serverlist is [10.182.5.5]

Get married Sep 28 11:27:37 2011 <15359131722005124> Host removed from serverlist is [10.182.5.5]

Get married Sep 28 11:27:37 2011 <15359131722005124> Initializing lastIndex= for a listing of length=2

Publish timed to 10.182.5.5:7005

This is actually the WebLogic which Apache is attempting to publish to.

You've confirmed this works when directly published towards the same Weblogic server.

The 20 seconds mathces the default KeepAliveSecs which you'll attempt to increase.

Perhaps you have set something within the wordpress plugin for WLIOTimeoutSecs.
This defaults to 300. Defines how long within minutes the plug-in waits for any reaction to a request from WebLogic Server.

But out of your log it doesn't seem like Apache delays for 300 seconds before failing.

Similarly MaxPostSize defaults to -1, just make sure that you haven't set some low value for your.

Browse the other wordpress plugin parameters about this list

http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143055

You could also wish to mess using the FileCaching element for Publish demands