[
https://issues.jboss.org/browse/WFLY-5638?page=com.atlassian.jira.plugin....
]
Arto Huusko commented on WFLY-5638:
-----------------------------------
I will try to test newer WildFly at some point, but it won't be very easy wrt. our
product.
If there is a git commit that fixes this, or if the fix is in newer undertow 1.2 series,
it would be easier to run patch wildfly 9.0.1 with the fix?
Can you confirm if this error can cause a socket leak? We are in the process of deploying
our product on wildfly 9.0.1 fairly soon, and upgrading wildfly version at this point is
not an option.
"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)