You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "mate.magyari" <ma...@gmail.com> on 2015/04/14 11:25:54 UTC

Camel-CometD - SSL problem in Jetty - Date of upgrade to Jetty 9?

Using Camel-CometD 2.13 we have problems with SSL in Jetty.

Using JVisualVM and inspecting the thread usage the busy threads seem to be:
qtp1195791107-2664" - Thread t@2664
java.lang.Thread.State: RUNNABLE
at org.eclipse.jetty.io.nio.SslConnection.process(SslConnection.java:278)
locked <2dcb00fd> (a org.eclipse.jetty.io.nio.SslConnection)
at org.eclipse.jetty.io.nio.SslConnection.access$900(SslConnection.java:48)
at
org.eclipse.jetty.io.nio.SslConnection$SslEndPoint.flush(SslConnection.java:690)
at org.eclipse.jetty.http.HttpGenerator.flushBuffer(HttpGenerator.java:850)
at
org.eclipse.jetty.http.AbstractGenerator.flush(AbstractGenerator.java:443)
at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:100)
at
org.eclipse.jetty.server.AbstractHttpConnection$Output.flush(AbstractHttpConnection.java:1085)
at
org.eclipse.jetty.server.AbstractHttpConnection$Output.sendContent(AbstractHttpConnection.java:1199)
at
org.eclipse.jetty.servlet.DefaultServlet.sendData(DefaultServlet.java:910)
at org.eclipse.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:519)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1317)
at
org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:247)
at
org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:210)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1288)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:369)
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:486)
at
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:933)
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:995)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at org.eclipse.jetty.io.nio.SslConnection.handle(SslConnection.java:196)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:745)

This stack trace shows some similarity to the one mentioned in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=456741. This thread suggests
the problem is solved in Jetty 9.2.

When is it due to upgrade Camel-CometD to use Jetty 9?



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-CometD-SSL-problem-in-Jetty-Date-of-upgrade-to-Jetty-9-tp5765749.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Camel-CometD - SSL problem in Jetty - Date of upgrade to Jetty 9?

Posted by "mate.magyari" <ma...@gmail.com>.
Thanks a lot!



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-CometD-SSL-problem-in-Jetty-Date-of-upgrade-to-Jetty-9-tp5765749p5765816.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Camel-CometD - SSL problem in Jetty - Date of upgrade to Jetty 9?

Posted by Willem Jiang <wi...@gmail.com>.
I just filled a JIRA[1] for it.
Now we can update the camel-cometd to Jetty9 in the camel master branch.

[1]https://issues.apache.org/jira/browse/CAMEL-8637
--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On April 14, 2015 at 10:21:09 PM, mate.magyari (mate.magyari@gmail.com) wrote:
> Thanks William.
>  
> The transition to Jetty 9 is unfortunately not that smooth, since the Jetty
> API has changed considerably. E.g.
> org.apache.camel.component.cometd.CometdComponent uses
> org.eclipse.jetty.server.nio.SelectChannelConnector,
> org.eclipse.jetty.server.ssl.SslConnector or
> org.eclipse.jetty.server.ssl.SslSelectChannelConnector which are no longer
> present in Jetty 9.
>  
> Hence my question. Do you have plans to support Jetty 9 (8 being EOL now) in
> the foreseeable future? If so, we don't have to start tinkering with it
> ourself.
>  
> regards,
> -mate
>  
>  
>  
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-CometD-SSL-problem-in-Jetty-Date-of-upgrade-to-Jetty-9-tp5765749p5765767.html  
> Sent from the Camel Development mailing list archive at Nabble.com.
>  


Re: Camel-CometD - SSL problem in Jetty - Date of upgrade to Jetty 9?

Posted by "mate.magyari" <ma...@gmail.com>.
Thanks William. 

The transition to Jetty 9 is unfortunately not that smooth, since the Jetty
API has changed considerably. E.g.
org.apache.camel.component.cometd.CometdComponent uses 
org.eclipse.jetty.server.nio.SelectChannelConnector,
org.eclipse.jetty.server.ssl.SslConnector or
org.eclipse.jetty.server.ssl.SslSelectChannelConnector which are no longer
present in Jetty 9.

Hence my question. Do you have plans to support Jetty 9 (8 being EOL now) in
the foreseeable future? If so, we don't have to start tinkering with it
ourself.

regards,
-mate



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-CometD-SSL-problem-in-Jetty-Date-of-upgrade-to-Jetty-9-tp5765749p5765767.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Camel-CometD - SSL problem in Jetty - Date of upgrade to Jetty 9?

Posted by Willem Jiang <wi...@gmail.com>.
I think it should be OK to use Jetty9 in Camel 2.16.x (camel master branch).
Camel 2.15.x has the Jetty9 support, but we don’t upgrade the Jetty version in side of camel-cometd, you may need to some addition work yourself. Please feel free to try it and share the result with us :) 

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On April 14, 2015 at 5:33:40 PM, mate.magyari (mate.magyari@gmail.com) wrote:
> Using Camel-CometD 2.13 we have problems with SSL in Jetty.
>  
> Using JVisualVM and inspecting the thread usage the busy threads seem to be:
> qtp1195791107-2664" - Thread t@2664
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.jetty.io.nio.SslConnection.process(SslConnection.java:278)  
> locked <2dcb00fd> (a org.eclipse.jetty.io.nio.SslConnection)
> at org.eclipse.jetty.io.nio.SslConnection.access$900(SslConnection.java:48)  
> at
> org.eclipse.jetty.io.nio.SslConnection$SslEndPoint.flush(SslConnection.java:690)  
> at org.eclipse.jetty.http.HttpGenerator.flushBuffer(HttpGenerator.java:850)  
> at
> org.eclipse.jetty.http.AbstractGenerator.flush(AbstractGenerator.java:443)  
> at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:100)
> at
> org.eclipse.jetty.server.AbstractHttpConnection$Output.flush(AbstractHttpConnection.java:1085)  
> at
> org.eclipse.jetty.server.AbstractHttpConnection$Output.sendContent(AbstractHttpConnection.java:1199)  
> at
> org.eclipse.jetty.servlet.DefaultServlet.sendData(DefaultServlet.java:910)  
> at org.eclipse.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:519)  
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)  
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1317)  
> at
> org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:247)  
> at
> org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:210)  
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1288)  
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443)  
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)  
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044)  
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372)  
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)  
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978)  
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)  
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)  
> at org.eclipse.jetty.server.Server.handle(Server.java:369)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:486)  
> at
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:933)
> at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:995)  
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
> at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)  
> at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)  
> at org.eclipse.jetty.io.nio.SslConnection.handle(SslConnection.java:196)  
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)  
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)  
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)  
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)  
> at java.lang.Thread.run(Thread.java:745)
>  
> This stack trace shows some similarity to the one mentioned in
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=456741. This thread suggests  
> the problem is solved in Jetty 9.2.
>  
> When is it due to upgrade Camel-CometD to use Jetty 9?
>  
>  
>  
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-CometD-SSL-problem-in-Jetty-Date-of-upgrade-to-Jetty-9-tp5765749.html  
> Sent from the Camel Development mailing list archive at Nabble.com.
>