[jboss-jira] [JBoss JIRA] (WFLY-3652) Network connection leak
Tang Yong (JIRA)
issues at jboss.org
Mon Mar 2 22:51:49 EST 2015
[ https://issues.jboss.org/browse/WFLY-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045441#comment-13045441 ]
Tang Yong commented on WFLY-3652:
---------------------------------
@Stuart Douglas I want to ask whether the issue has been fixed in 9.0.0.Alpha1? Thanks.
--Tang
> Network connection leak
> -----------------------
>
> Key: WFLY-3652
> URL: https://issues.jboss.org/browse/WFLY-3652
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Environment: Linux 2.6.38-16-server
> Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
> Reporter: Jan Vanhercke
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Alpha1
>
>
> When using Asynchronous servlets and AsyncListeners for long polling we observe a connection leak in the undertow subsystem.
> Heap dumps show a large number of org.xnio.io.NioSocketConduit, io.undertow.server.protocol.http.HttpServerConnection and related objects.
> However, since the effective number of connections is far less, nearly all AsyncContext instances we find are in a complete state and lsof output returns a large number of sockets with 'can't identify protocol' entries indicating that sockets are kept open by the JVM but are in fact half closed by the network stack.
> Not all connections appear to be leaking, but over time, depending on the load, the server instance fills up.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jboss-jira
mailing list