[Bug 61751] NIO2 connector cuts incoming request

2018-02-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #19 from Markus Dörschmidt --- Thank you very much. The bug is fixed! -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61751] NIO2 connector cuts incoming request

2018-02-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED

[Bug 61751] NIO2 connector cuts incoming request

2018-02-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 Mark Thomas changed: What|Removed |Added Resolution|FIXED |---

[Bug 61751] NIO2 connector cuts incoming request

2018-02-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #16 from Remy Maucherat --- I added a follow up: http://svn.apache.org/viewvc?rev=1824201=rev As this didn't happen with the regular JSSE engine, I think the missing underflow status is the root cause (the unwrap

[Bug 61751] NIO2 connector cuts incoming request

2018-02-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #15 from Remy Maucherat --- On second thought, this will need to be revisited as the blocking read of SecureNio2Channel is supposed to block until it returns non 0. Of course, the algorithm is complex already ... I

[Bug 61751] NIO2 connector cuts incoming request

2018-02-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #14 from Remy Maucherat --- Great job on that fix ! :) -- You are receiving this mail because: You are the assignee for the bug. - To

[Bug 61751] NIO2 connector cuts incoming request

2018-02-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED

[Bug 61751] NIO2 connector cuts incoming request

2018-02-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #12 from Mark Thomas --- I've found the root cause. A blocking read obtained bytes from the network but after unwrapping there were zero application bytes. Since this is a blocking read, more network bytes should

[Bug 61751] NIO2 connector cuts incoming request

2018-02-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #11 from Mark Thomas --- Thanks for the additional information. I can now reproduce this (thanks to Microsoft for the free azure credits). I have two clean Tomcat 9.0.x builds. One locally, one on Azure. Key

[Bug 61751] NIO2 connector cuts incoming request

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 Markus Dörschmidt changed: What|Removed |Added Resolution|WORKSFORME |---

[Bug 61751] NIO2 connector cuts incoming request

2018-01-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 Remy Maucherat changed: What|Removed |Added Status|NEEDINFO|RESOLVED

[Bug 61751] NIO2 connector cuts incoming request

2017-11-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #8 from Mark Thomas --- I can't reproduce this problem with the given test case either. I've tested: - NIO2 - 8.5.x trunk - http and https - https with OpenSSL (Tomcat native 1.2.16, OpenSSL ubuntu latest) - https

[Bug 61751] NIO2 connector cuts incoming request

2017-11-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #7 from Remy Maucherat --- As I said, I tried the same connector with your test upload, it worked for me. This issue is not very well presented IMO, for instance it seems to imply it is a NIO2 + OpenSSL issue

[Bug 61751] NIO2 connector cuts incoming request

2017-11-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #6 from Markus Dörschmidt --- The real web application uses Spring Webservices 2.4.0. The SOAP request contains a base64-encoded binary element. The SOAP request never reaches the Webservice framework,

[Bug 61751] NIO2 connector cuts incoming request

2017-11-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #5 from Remy Maucherat --- This works for me. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe,

[Bug 61751] NIO2 connector cuts incoming request

2017-11-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #4 from Markus Dörschmidt --- I attached a simple web application to reproduce the code. Try sending XML data to application using curl: curl -X POST -k --header "Content-Type: text/xml;charset=UTF-8"

[Bug 61751] NIO2 connector cuts incoming request

2017-11-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #3 from Markus Dörschmidt --- Created attachment 35539 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35539=edit Minimal code to reproduce bug -- You are receiving this mail because: You are the

[Bug 61751] NIO2 connector cuts incoming request

2017-11-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 Mark Thomas changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment

[Bug 61751] NIO2 connector cuts incoming request

2017-11-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61751 --- Comment #1 from Remy Maucherat --- Do you think you could give some pointers on reproduction ? In the past there was BZ57799 which was caused by an unexpected interaction with use of available() by the framework. -- You