It should be fixed in the latest Undertow build, which should make it into Wildfly upstream shortly.

On Wed, Oct 22, 2014 at 1:53 AM, Pedro Igor Silva <> wrote:

    I'm using latest build from wildfly upstream/master.

    Would like to know if there is an issue on how Undertow recognize that a response is already commited or not.

    My code is setting a header and sending an error like that


    and isCommited is always returning "false" after that. To change this behavior I have to force a flush, so isCommited returns true.

    Both WildFly 8.1.0.Final and EAP behave differently and isCommited returns "true" without requiring a manual flush. Is this an issue ?

Pedro Igor
wildfly-dev mailing list