Hi.
I have a problem with Jetty component in camel.
I need to handle the long http get-query error to my route.

Component didn`t throw any exception, it catch any error itself. As result,
http-client hover in infinite loop.

How can I solve this problem?
And one more quation. Can <from /> elements throws any exception in route?

*This`s my camel route:*
/<route>
        <from ref="jetty:http://host:port/some"; />
        <onException>
                <exception>java.lang.Exception</exception>
                <handled>
                        <constant>true</constant>
                </handled>
                <setBody>
                        <constant>ERROR FULL head</constant>
                </setBody>
        </onException>
        <process ref="mdmRequestSaver" />                       
</route>/

*log trace:*

/03.10.2012 9:36:11 org.eclipse.jetty.server.AsyncHttpConnection handle
FINE: 
HttpException(413,FULL head,null)
        at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:945)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:274)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
        at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:52)
        at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
        at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
        at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
        at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
        at java.lang.Thread.run(Unknown Source)
03.10.2012 9:36:11 org.eclipse.jetty.http.AbstractGenerator sendError
FINE: sendError: 413 FULL head
03.10.2012 9:36:11 org.eclipse.jetty.io.nio.SelectorManager$SelectSet
destroyEndPoint
FINE: destroyEndPoint
s...@18686494java.nio.channels.SocketChannel[closed][o=false
d=false,io=0,w=true,rb=false,wb=false]
03.10.2012 9:36:11 org.eclipse.jetty.server.HttpConnection closed
FINE: closed
org.eclipse.jetty.server.nio.SelectChannelConnector$SelectChannelHttpConnection@f72f09@127.0.0.1:8083<->127.0.0.1:1138
03.10.2012 9:36:11 org.eclipse.jetty.http.HttpParser parseNext
FINE: state=-10 length=0 len=-3
HttpException(413,FULL head,null)
        at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:945)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:274)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
        at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:52)
        at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
        at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
        at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
        at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
        at java.lang.Thread.run(Unknown Source)
03.10.2012 9:36:11 org.eclipse.jetty.server.AsyncHttpConnection handle
FINE: uri=
03.10.2012 9:36:11 org.eclipse.jetty.server.AsyncHttpConnection handle
FINE: fields=/

P.S. Sorry for my english )



--
View this message in context: 
http://camel.465427.n5.nabble.com/Jetty-component-long-get-query-tp5720429.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to