You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by re...@apache.org on 2019/04/16 08:26:06 UTC
[tomcat] branch master updated: Edit changelog entry
This is an automated email from the ASF dual-hosted git repository.
remm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/master by this push:
new 187c152 Edit changelog entry
187c152 is described below
commit 187c152759e72908d7e90355145a7c2d412eb73a
Author: remm <re...@apache.org>
AuthorDate: Tue Apr 16 10:25:55 2019 +0200
Edit changelog entry
There was no general connection leak that I can reproduce anymore. As
NioSocketWrapper.close was only closing the channel, this is where the
root of the problem was.
---
webapps/docs/changelog.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml
index a71fb58..de56186 100644
--- a/webapps/docs/changelog.xml
+++ b/webapps/docs/changelog.xml
@@ -59,7 +59,7 @@
value now defaults to <code>true</code>. (remm)
</fix>
<fix>
- Possible HTTP/2 connection leak issue when using async. (remm)
+ Possible HTTP/2 connection leak issue when using async with NIO. (remm)
</fix>
<fix>
Fix socket close discrepancies for NIO, now the wrapper close
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org