Hello guys,
I am getting some stuck threads on my application when it connects to Solr.
The stuck threads occur in an even time, in such a way that each 3 days the
app is online it hangs up the entire cluster.
I don't know if there's any direct relation to Solr, but I get the following
exception on some sparse connections the application does to Solr.
Is there any know bug about Solr writing wrong responses?
####<Nov 25, 2008 6:14:35 PM BRST> <Error> <HTTP> <localhost> <cluster0>
<[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (s
elf-tuning)'> <<WLS Kernel>> <> <> <1227644075142> <BEA-101083> <Connection
failure.
java.net.ProtocolException: Didn't meet stated Content-Length, wrote: '259'
bytes instead of stated: '258' bytes.
at weblogic.servlet.internal.
ServletOutputStreamImpl.ensureContentLength(ServletOutputStreamImpl.java:410)
at
weblogic.servlet.internal.ServletResponseImpl.ensureContentLength(ServletResponseImpl.java:1358)
at
weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1400)
at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1375)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
--
Alexander Ramos Jardim
