Thanks, I will submit a pu<span></span>ll request if I notice it anywhere else.<br><br>On Wednesday, September 17, 2014, Stuart Douglas <<a href="mailto:sdouglas@redhat.com">sdouglas@redhat.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I will change EagerFormParsingHandler to call parseBlocking() if the exchange is in blocking mode.<br>
<br>
Stuart<br>
<br>
Bill O'Neil wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have come across a few Handlers that dispatch to a worker thread these<br>
include blocking handler, resource handler and the form parsing handler.<br>
<br>
My specific use case was with the form parsing handler. I had a bunch<br>
of handlers chained together basically as follows.<br>
<br>
Blocking handler -> ExceptionHandler -> FormParsingHandler -><br>
MyBlockingHandler<br>
<br>
The form parsing handler would cause the handler to be dispatched a<br>
second time to a new executor. This made me lose the stack trace, and<br>
the Exception handler was not catching an exception being thrown inside<br>
of MyBlockingHandler.<br>
<br>
I resolved this by basically cloning the form parsing handler and<br>
calling the parseBlocking() instead of the non blocking parse(). This<br>
is acceptable because I already dispatched to a non IO thread.<br>
<br>
Should any handler that attempts to dispatch first check if the exchange<br>
is in an IO thread before dispatching or is there a specific use case<br>
for some handlers to always dispatch?<br>
<br>
Thanks,<br>
Bill<br>
<br>
______________________________<u></u>_________________<br>
undertow-dev mailing list<br>
<a>undertow-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/undertow-dev" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/undertow-dev</a><br>
</blockquote>
</blockquote>