I am hitting the Jetty org.eclipse.jetty.server.handler.ErrorHandler
Am Dienstag, 6. Februar 2018 11:23:16 UTC+1 schrieb Maurice Betzel: > > If you take a look at > > org.eclipse.jetty.server.Response method sendError > > > > you will see Jetty is returning the default error web page if no error > handler is set :( . For my understanding it should pick up my default > handler for producing the page. > Can i set the error handler to point to my default handler? > > Am Dienstag, 6. Februar 2018 11:07:38 UTC+1 schrieb Grzegorz Grzybek: >> >> And the error handler is NOT the one you wanted to set? I don't see any >> custom ErrorHandler in your jetty.xml... >> >> ~Grzegorz >> >> 2018-02-06 11:03 GMT+01:00 Maurice Betzel <[email protected]>: >> >>> Camel is calling the method after not finding any matching consumer: >>> >>> response.sendError(HttpServletResponse.SC_NOT_FOUND); >>> >>> >>> and just returns the thread, meaning the Response produced by Jetty has >>> the default Jetty exception page set somewhere. >>> >>> >>> Am Dienstag, 6. Februar 2018 10:49:22 UTC+1 schrieb Maurice Betzel: >>>> >>>> I am getting to the point here :), in the >>>> >>>> org.eclipse.jetty.servlet.ServletHolder.class >>>> >>>> >>>> i am hitting method handle on line 571 calling the >>>> CamelHttpTransportServlet: >>>> >>>> servlet.service(request, response); >>>> >>>> >>>> Before the call the request reports not handled and the response object >>>> does not have a writer yet. If it returns from Camel _handled is true and >>>> the response object has a writer set containing the default Jetty html >>>> page. where did this come from? >>>> >>>> Dienstag, 6. Februar 2018 10:37:48 UTC+1 schrieb Grzegorz Grzybek: >>>>> >>>>> Hello >>>>> >>>>> Hmm, I see your case is quite complex - is there a chance you prepare >>>>> integration test in >>>>> pax-web-itests/pax-web-itests-container/pax-web-itests-container-jetty? >>>>> >>>>> I'd have to try to reproduce your issue, but I have to know what other >>>>> web bundles / wars you have installed - maybe you also have some >>>>> whiteboard >>>>> services or plain httpService.registerServlet() calls? >>>>> >>>>> regards >>>>> Grzegorz Grzybek >>>>> >>>>> 2018-02-06 10:28 GMT+01:00 Maurice Betzel <[email protected]>: >>>>> >>>>>> No, it did not. Jetty is producing the response using the default >>>>>> Jetty handler. >>>>>> >>>>>> >>>>>> Am Dienstag, 6. Februar 2018 09:49:55 UTC+1 schrieb Maurice Betzel: >>>>>>> >>>>>>> My default handler gets hit on >>>>>>> https://somehost/api/rest/existingcontext/nonexistingcontext, but >>>>>>> reports that the base request was handled and the response was >>>>>>> committed. >>>>>>> Did the Camel servlet handle the error before my default handler? >>>>>>> >>>>>> -- >>>>>> -- >>>>>> ------------------ >>>>>> OPS4J - http://www.ops4j.org - [email protected] >>>>>> >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "OPS4J" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>> -- >>> ------------------ >>> OPS4J - http://www.ops4j.org - [email protected] >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "OPS4J" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
