well the nio ones are typically better, but if you could open an issue on bugs.eclipse.org under RT/Jetty that would be super.
thanks, jesse -- jesse mcconnell [email protected] On Sat, Jul 9, 2011 at 02:04, khiem nguyen <[email protected]> wrote: > nope, i upgraded to 7.4.3, this happens again, i'll switch to NIO-connectors > so see if things get better. > thanx > > > On Thu, Jul 7, 2011 at 3:05 PM, khiem nguyen <[email protected]> wrote: >> >> thanx. >> i'll try it . >> >> fyi, i'm also using it with ConnectHandler/Proxyhandler for proxying >> https-connection. dont know if it has sth to do with the issue ( the new >> ProxyHandler support close-operation on the channel without closing the >> whole socket, could this be that the proxyhandler/connecthandler doesnt >> release the connection correctly which hold the thread from closing >> correctly ?) >> >> >> >> On Thu, Jul 7, 2011 at 2:34 PM, Jesse McConnell >> <[email protected]> wrote: >>> >>> Update to 7.4.3, there has been incremental improvements on this sort >>> of behavior. >>> >>> if you still see this after the upgrade definitely let us know >>> >>> cheers, >>> jesse >>> >>> -- >>> jesse mcconnell >>> [email protected] >>> >>> >>> >>> On Thu, Jul 7, 2011 at 06:33, khiem nguyen <[email protected]> wrote: >>> > Hi there >>> > i'm using jetty 7.4.2 as a embedded webserver & having after awhile a >>> > very >>> > high cpu load. >>> > some analysis shows that 1 connector thread goes into an endless lopp & >>> > occupies 100% cpu load although there's no request >>> > the load stays even when all the clients are disconnected. >>> > tracktrace for this thread from jconsole: >>> > >>> > could someone give some hints how this could happens ? >>> > >>> > thanx >>> > >>> > >>> > Name: qtp1939768105-1610 >>> > State: RUNNABLE >>> > Total blocked: 1 Total waited: 15 >>> > >>> > Stack trace: >>> > >>> > org.eclipse.jetty.io.ByteArrayBuffer.readFrom(ByteArrayBuffer.java:388) >>> > org.eclipse.jetty.io.bio.StreamEndPoint.fill(StreamEndPoint.java:132) >>> > >>> > org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.fill(SocketConnector.java:209) >>> > >>> > org.eclipse.jetty.server.ssl.SslSocketConnector$SslConnectorEndPoint.fill(SslSocketConnector.java:612) >>> > org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:289) >>> > org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:214) >>> > org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411) >>> > >>> > org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241) >>> > >>> > org.eclipse.jetty.server.ssl.SslSocketConnector$SslConnectorEndPoint.run(SslSocketConnector.java:664) >>> > >>> > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529) >>> > java.lang.Thread.run(Thread.java:662) >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > jetty-users mailing list >>> > [email protected] >>> > https://dev.eclipse.org/mailman/listinfo/jetty-users >>> > >>> > >>> _______________________________________________ >>> jetty-users mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > > _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
