[jetty-users] exception upgrading jetty

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jetty-users] exception upgrading jetty

Mattia Merzi
Hi everyone,

I've just upgraded jetty version from 7.3.0 to 7.6.1
and we started to see this exception, more ore less
1 every 2 or 3 HTTP requests:

java.net.SocketException: Transport endpoint is not connected
        at sun.nio.ch.SocketChannelImpl.shutdown(Native Method)
        at sun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:633)
        at sun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:360)
        at org.eclipse.jetty.io.nio.ChannelEndPoint.shutdownChannelInput(ChannelEndPoint.java:123)
        at org.eclipse.jetty.io.nio.ChannelEndPoint.shutdownInput(ChannelEndPoint.java:147)
        at org.eclipse.jetty.io.nio.ChannelEndPoint.fill(ChannelEndPoint.java:242)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.fill(SelectChannelEndPoint.java:309)
        at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:1038)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:276)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)
        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:76)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:609)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)


Jetty is behind an apache httpd with mod_proxy + mod_proxy_http; not every time,
but 1 out of 100 requests, associated with the java exception, the
client receives an
HTTP 502 (proxy error) from the apache httpd (apache httpd is 2.2.17); mod_proxy
is configured with no keep-alive and a very long timeout, the server
handles about
10~15 requests/sec.

If you need more details, let me know.

Greetings,

Mattia.
_______________________________________________
jetty-users mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-users
Reply | Threaded
Open this post in threaded view
|

Re: [jetty-users] exception upgrading jetty

Jesse McConnell
I would recommend putting jetty into debug mode and looking for WARN
messages associated with the nio plumbing...

and see if you can record the event with wireshark or the tcpdump to
confirm that it is the jetty side of the connection having issues.

if you see any WARN messages out of the nio bits open up a bug in
bugzilla and attach the revalent information there

cheers,
jesse

--
jesse mcconnell
[hidden email]



On Thu, Feb 23, 2012 at 03:15, Mattia Merzi <[hidden email]> wrote:

> Hi everyone,
>
> I've just upgraded jetty version from 7.3.0 to 7.6.1
> and we started to see this exception, more ore less
> 1 every 2 or 3 HTTP requests:
>
> java.net.SocketException: Transport endpoint is not connected
>        at sun.nio.ch.SocketChannelImpl.shutdown(Native Method)
>        at sun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:633)
>        at sun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:360)
>        at org.eclipse.jetty.io.nio.ChannelEndPoint.shutdownChannelInput(ChannelEndPoint.java:123)
>        at org.eclipse.jetty.io.nio.ChannelEndPoint.shutdownInput(ChannelEndPoint.java:147)
>        at org.eclipse.jetty.io.nio.ChannelEndPoint.fill(ChannelEndPoint.java:242)
>        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.fill(SelectChannelEndPoint.java:309)
>        at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:1038)
>        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:276)
>        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)
>        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:76)
>        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:609)
>        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>        at java.lang.Thread.run(Thread.java:662)
>
>
> Jetty is behind an apache httpd with mod_proxy + mod_proxy_http; not every time,
> but 1 out of 100 requests, associated with the java exception, the
> client receives an
> HTTP 502 (proxy error) from the apache httpd (apache httpd is 2.2.17); mod_proxy
> is configured with no keep-alive and a very long timeout, the server
> handles about
> 10~15 requests/sec.
>
> If you need more details, let me know.
>
> Greetings,
>
> Mattia.
> _______________________________________________
> jetty-users mailing list
> [hidden email]
> https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-users