[jboss-jira] [JBoss JIRA] (WFLY-5638) "Buffer was already freed" error from http request processing

[Arto Huusko (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126377#comment-13126377 ] 

Arto Huusko commented on WFLY-5638:
-----------------------------------

That commit fixes buffer leak, but this is about a socket leak, and my wildfly instance is already patched with that commit.

But please see XNIO-254, which I just updated with a new patch to JsseSslConduitEngine which should avoid the "buffer was already freed" and therefore any problems the unexpeced IllegalStateException can cause.

> "Buffer was already freed" error from http request processing
> -------------------------------------------------------------
>
>                 Key: WFLY-5638
>                 URL: https://issues.jboss.org/browse/WFLY-5638
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 9.0.1.Final
>            Reporter: Arto Huusko
>            Assignee: Stuart Douglas
>         Attachments: stacktrace.txt
>
>
> Undertow causes XNIO exception "Buffer was already freed" during response write, possibly due to premature client close.
> I suspect this may also cause the socket to leak, because the number of "Buffer was already freed" messages in widlfly server.log corresponds to the number of leaked sockets in the lsof command output for the wildfly process (seen as sockets with "can't identify protocol" description).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)