PROTOCOL_ERROR: Response contains no data

Question

Does anyone have any ideas what could be causing this:
Sat Mar 24 15:06:49 2007 Found 1 servers
Sat Mar 24 15:06:49 2007 attempt #0 out of a max of 90
Sat Mar 24 15:06:49 2007 trying connect to PRIMARY '#commented out by hoos#'/xxxx/xxxx
Sat Mar 24 15:06:49 2007 INFO: New NON-SSL URL
Sat Mar 24 15:06:49 2007 Local Port of the socket is 58238
Sat Mar 24 15:06:49 2007 Remote Host #commented out by hoos# Remote Port xxxx
Sat Mar 24 15:06:49 2007 INFO: sysSend 573
Sat Mar 24 15:06:49 2007 parsed all headers OK
Sat Mar 24 15:06:49 2007 sendResponse() : r->status = '200'
Sat Mar 24 15:06:49 2007 PROTOCOL_ERROR: Response contains no data - isRecycled:0
Sat Mar 24 15:06:49 2007 *******Exception type [PROTOCOL_ERROR] (Unexpected EOF reading HTTP status - connection reset) raised at line 774 of ../nsapi/URL.cpp
Sat Mar 24 15:06:49 2007 Marking #commented out by hoos# as bad
Sat Mar 24 15:06:49 2007 got exception in sendRequest phase: PROTOCOL_ERROR [line 774 of ../nsapi/URL.cpp]: Unexpected EOF reading HTTP status - connection reset at l
ine 2562
I couldn't find any resolutions in the newgroups or toubleshooting patterns. I'll be raising a support case with BEA shortly in the mean time could this be an application issue or, as I think, more probably a problem caused by a network device?
I can see that the issue seems to be with a response being 0 bytes in size as the connection was reset.
This trace is from a test server under load but the WLS configuration is the same as the productin server which we believe to be under the same loads as we are testing. We do not see this issue on the live servers, but I'll be double checking the logs on the production servers anyway.
Hussein Badakhchani
http://dev2dev.bea.com/blog/hoos
London Middleware
http://londonmiddleware.org/index.html
Edited by hoos at 03/24/2007 9:44 AM

Answer 1

<p>Jesus, thanks for the response. The wl_plugin version and build are: Build date/time: May 7 2004 10:16:34 Change Number: 381825, obtained from the wl_bridge.</p>
<p>I'm loathed to change the wlproxy configuration because it is the same as that used on the production servers and my understanding is that there is no issue on that environment. However its worth testing it as an experiment.</p>
<pre>
<IfModule mod_weblogic.c>
WLProxySSL ON
Debug ON
DebugConfigInfo OFF
DynamicServerList ON
WLLogFile /var/log/xxxxx/apache/wlproxy.log
FileCaching OFF
ErrorPage http://noservice.htm
ConnectTimeoutSecs 180
WLSocketTimeoutSecs 180
WLIOTimeoutSecs 300
ConnectRetrySecs 2
Idempotent OFF
</IfModule>
<p>What is odd is that browsing to the bridge sometimes ends up with the application error page being displayed rather than the bride. This seems to be consistent with proxy log error messages.</p>
</pre>
<p>
Hussein Badakhchani
London Middleware
</p>