jetty 6 proxy Exceptions

[BlastChat]

Hello, can anybody provide a solution to eliminate following warnings
in jetty's stderrout.log? Especially number 1.? Thank you.

1. EOF wanring:
2010-11-05 07:00:39.941:WARN::EXCEPTION on
org.mortbay.proxy.AsyncProxyServlet$1@51456845=GET//127.0.0.1:8080/
components
/file.js?v=200902117688#9
org.mortbay.jetty.EofException
at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:
787)
at org.mortbay.jetty.AbstractGenerator
$Output.blockForOutput(AbstractGenerator.java:550)
at org.mortbay.jetty.AbstractGenerator
$Output.flush(AbstractGenerator.java:571)
at org.mortbay.jetty.HttpConnection
$Output.flush(HttpConnection.java:1005)
at org.mortbay.jetty.AbstractGenerator
$Output.write(AbstractGenerator.java:648)
at org.mortbay.jetty.AbstractGenerator
$Output.write(AbstractGenerator.java:579)
at org.mortbay.proxy.AsyncProxyServlet
$1.onResponseContent(AsyncProxyServlet.java:183)
at org.mortbay.jetty.client.HttpExchange
$Listener.onResponseContent(HttpExchange.java:717)
at org.mortbay.jetty.client.HttpConnection
$Handler.content(HttpConnection.java:500)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:
212)
at
org.mortbay.jetty.client.HttpConnection.handle(HttpConnection.java:
236)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
409)
at org.mortbay.thread.QueuedThreadPool
$PoolThread.run(QueuedThreadPool.java:582)
this warning is logged not for every occurrence of loading same page
or same file, but it is logged quite often...
(error log grows to about 200MB in a day filled with these warnings)

2. IllegalStateExceptions:
2010-11-04 22:42:09.597:WARN::EXCEPTION on
org.mortbay.proxy.AsyncProxyServlet$1@1164506135=GET//127.0.0.1:8080/
componen
ts/file.css?v=200902112393#9
java.lang.IllegalStateException: State==HEADER
at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:
683)
at org.mortbay.jetty.AbstractGenerator
$Output.blockForOutput(AbstractGenerator.java:550)
at org.mortbay.jetty.AbstractGenerator
$Output.flush(AbstractGenerator.java:571)
at org.mortbay.jetty.HttpConnection
$Output.flush(HttpConnection.java:1005)
at org.mortbay.jetty.AbstractGenerator
$Output.write(AbstractGenerator.java:648)
at org.mortbay.jetty.AbstractGenerator
$Output.write(AbstractGenerator.java:579)
at org.mortbay.proxy.AsyncProxyServlet
$1.onResponseContent(AsyncProxyServlet.java:183)
at org.mortbay.jetty.client.HttpExchange
$Listener.onResponseContent(HttpExchange.java:717)
at org.mortbay.jetty.client.HttpConnection
$Handler.content(HttpConnection.java:500)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:
212)
at
org.mortbay.jetty.client.HttpConnection.handle(HttpConnection.java:
236)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
409)
at org.mortbay.thread.QueuedThreadPool
$PoolThread.run(QueuedThreadPool.java:582)
2010-11-04 22:42:09.598:WARN::handle failed
java.lang.IllegalStateException: State==HEADER
at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:
683)
at org.mortbay.jetty.AbstractGenerator
$Output.blockForOutput(AbstractGenerator.java:550)
at org.mortbay.jetty.AbstractGenerator
$Output.flush(AbstractGenerator.java:571)
at org.mortbay.jetty.HttpConnection
$Output.flush(HttpConnection.java:1005)
at org.mortbay.jetty.AbstractGenerator
$Output.write(AbstractGenerator.java:648)
at org.mortbay.jetty.AbstractGenerator
$Output.write(AbstractGenerator.java:579)
at org.mortbay.proxy.AsyncProxyServlet
$1.onResponseContent(AsyncProxyServlet.java:183)
at org.mortbay.jetty.client.HttpExchange
$Listener.onResponseContent(HttpExchange.java:717)
at org.mortbay.jetty.client.HttpConnection
$Handler.content(HttpConnection.java:500)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:
212)
at
org.mortbay.jetty.client.HttpConnection.handle(HttpConnection.java:
236)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
409)
at org.mortbay.thread.QueuedThreadPool
$PoolThread.run(QueuedThreadPool.java:582)


3. INFO printouts:
2010-11-04 22:05:16.803:INFO::org.mortbay.io.nio.SelectorManager
$SelectSet@4a2d51ef JVM BUG(s) - injecting delay6 times
2010-11-04 22:05:16.803:INFO::org.mortbay.io.nio.SelectorManager
$SelectSet@4a2d51ef JVM BUG(s) - recreating selector 6 t imes,
canceled keys 158 times

4. SSL warnings (SSL certificate is valid and placed into keystore
correctly):
2010-11-04 22:29:48.546:WARN::SSL renegotiate denied:
java.nio.channels.SocketChannel[connected local=/71.6.153.212:443
remote=/207.233.67.8:17082]

[Simone Bordet]

Hi,

On Fri, Nov 5, 2010 at 09:09, BlastChat <blas...@gmail.com> wrote:
> Hello, can anybody provide a solution to eliminate following warnings
> in jetty's stderrout.log? Especially number 1.? Thank you.

What is your logging configuration ?
The problem is only that these logs are too verbose for you ?

Also, you can file bugs at http://jetty.codehaus.org.

Simon
--
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz

[BlastChat]

no, problem is not how verbose these warnings are, but

1. Why are they there at all and how to eliminate them?
2. Might they be causing any memory leaks?

P.

On Nov 6, 3:50 am, Simone Bordet <simone.bor...@gmail.com> wrote:
> Hi,
>

> On Fri, Nov 5, 2010 at 09:09, BlastChat <blastc...@gmail.com> wrote:
> > Hello, can anybody provide a solution to eliminate following warnings
> > in jetty's stderrout.log? Especially number 1.? Thank you.
>
> What is your logging configuration ?
> The problem is only that these logs are too verbose for you ?
>
> Also, you can file bugs athttp://jetty.codehaus.org.
>
> Simon

> --http://bordet.blogspot.com

[Simone Bordet]

Hi,

On Sat, Nov 6, 2010 at 21:26, BlastChat <blas...@gmail.com> wrote:
> no, problem is not how verbose these warnings are, but
>
> 1. Why are they there at all and how to eliminate them?

You can't eliminate the fact that if a user closes the browser, the
socket is abruptly closed, and if you try to write to that socket, you
get an exception.
Likewise when it is logged that a SSL renegotiation is denied because
it is a known security hole in the JDK. And likewise for JDK selector
bugs.
You can change the log level though, so you won't see them anymore.

> 2. Might they be causing any memory leaks?

None that I am aware of.

Simon
--