Hi Micky, It looks like jetty is not properly configured or there are two instances of jetty. Can you try to exercise your camel route outside of tomcat first, in a standalone jvm.
Also, it may be good to attach a testcase and/or your tomcat config to the jira you raised. One thing that seems strange to me is the use of jetty (a servlet engine) inside tomcat (another servlet engine). Am I missing something? At the moment, the camel-jetty component requires jetty but it would make sense that it could be configured to deploy its servlet to tomcat. Gary. On 01/04/2008, Micky Santomax <[EMAIL PROTECTED]> wrote: > > Thanks for patch Gary > > > > are you using the latest trunk? > > can you verify that the changes identified @ > > > http://fisheye6.cenqua.com/browse/activemq/camel/trunk/components/camel-jetty/src/main/java/org/apache/camel/component/jetty/JettyHttpComponent.java?r1=614080&r2=641800 > > are in your checkout. > > > I'm using last trunk. In installation phase there aren't problems, but when > I send a soap message to the endpoint, the following exception is thrown : > > 2008-04-01 13:41:26.010::WARN: handle failed > > java.lang.NullPointerException > at > > org.mortbay.thread.BoundedThreadPool.isLowOnThreads(BoundedThreadPool.java:216) > at > > org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:218) > at > > org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:620) > at > > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450) > > -- > View this message in context: > http://www.nabble.com/Password-error-for-https-endpoint-connection-tp16128569s22882p16418451.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > >
