[jboss-jira] [JBoss JIRA] (WFLY-4827) Network Connection leak on client abort connection

Mon Jun 29 11:42:06 EDT 2015

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

Andrea Bertolini commented on WFLY-4827:
----------------------------------------

With correct url i can download the new branch...
But using mvn install i get this error.

[INFO] Scanning for projects...
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jboss-parent/19/jboss-parent-19.pom
Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jboss-parent/19/jboss-parent-19.pom (31 KB at 22.7 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Undertow
[INFO] Undertow Parser Generator
[INFO] Undertow Core
[INFO] Undertow Servlet
[INFO] Undertow WebSockets JSR356 implementations
[INFO] Undertow Examples
[INFO] Undertow HTTP2 test suite
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Undertow 1.3.0.Beta3-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-enforcer-plugin/1.4/maven-enforcer-plugin-1.4.pom
Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/1.4/maven-enforcer-plugin-1.4.pom
giu 29, 2015 5:37:11 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: I/O exception (java.net.SocketException) caught when processing request to {s}->https://repo.maven.apache.org:443: Connection reset
giu 29, 2015 5:37:11 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: Retrying request to {s}->https://repo.maven.apache.org:443
giu 29, 2015 5:37:32 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: I/O exception (java.net.SocketException) caught when processing request to {s}->https://repo.maven.apache.org:443: Connection reset
giu 29, 2015 5:37:32 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: Retrying request to {s}->https://repo.maven.apache.org:443
giu 29, 2015 5:37:53 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: I/O exception (java.net.SocketException) caught when processing request to {s}->https://repo.maven.apache.org:443: Connection reset
giu 29, 2015 5:37:53 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: Retrying request to {s}->https://repo.maven.apache.org:443
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Undertow ........................................... FAILURE [01:26 min]
[INFO] Undertow Parser Generator .......................... SKIPPED
[INFO] Undertow Core ...................................... SKIPPED
[INFO] Undertow Servlet ................................... SKIPPED
[INFO] Undertow WebSockets JSR356 implementations ......... SKIPPED
[INFO] Undertow Examples .................................. SKIPPED
[INFO] Undertow HTTP2 test suite .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:28 min
[INFO] Finished at: 2015-06-29T17:38:15+02:00
[INFO] Final Memory: 13M/150M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4: Could not trans
fer artifact org.apache.maven.plugins:maven-enforcer-plugin:pom:1.4 from/to central (https://repo.maven.apache.org/maven2): Connection reset -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

But did I download 1.3.0 version??
[INFO] Building Undertow 1.3.0.Beta3-SNAPSHOT

> Network Connection leak on client abort connection
> --------------------------------------------------
>
>                 Key: WFLY-4827
>                 URL: https://issues.jboss.org/browse/WFLY-4827
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow), Web Sockets
>    Affects Versions: 8.2.0.Final
>         Environment: On Windows Server 2012, JDK 1.8.0_45, Wildfly 8.2.0.Final in standalone mode.
>            Reporter: Andrea Bertolini
>            Assignee: Stuart Douglas
>
> We have a classic client-server application, all written in Java. Each client is installed on a forklift which can move all around a large area. This area is under wi-fi coverage.
> Sometimes the clients can have a bad connection quality and the client-server communication is interrupted; in such a case it takes too many seconds to be restored. 
> To fix this situation, we add a timeout client-side. After 5 seconds it aborts the call and tries again a second time.  
> To achieve this call we use apache httpcomponents library (version 4.4). We use the abort method of httppost to interrupt this call. 
> Server-side, we have a group of web-servlets which listen to the incoming calls, manage requests and send a response. 
> It appears that sometimes a communication remains stuck in reading or writing from/to the stream. When the client aborts the communication, an exception is thrown on the server caused by the channel being closed.
> It happens that a large number of connections remains stuck in connection status 'established' (only server-side) even if the real connection is actually closed (client doesn't have that connection active anymore). 
> When the number of established connections grows up to 200, server stops responding on port 8080, so it cannot accept more connections and it seems to freeze. 
> We tried to add tcp-keep-alive=true and no-request-timeout=120000 on http-listener in undertow subsystem, but sometimes it removes idle connections after any incoming requests are received for 2 minutes, some other times it keep connections as established and doesn't close them.

--
This message was sent by Atlassian JIRA
(v6.3.15#6346)