My understanding is that when you are interested in closing the underlying
socket when using the SSLEngine, you must call closeOutbound() and WRAP and
UNWRAP until both isInboundDone() and isOutboundDone() return true.
One edge case of this is if you are interested in closing the socket prior to
M, Xuelei Fan wrote:
>
> Hi,
>
> We are working on the JDK 11 close issue.
> https://bugs.openjdk.java.net/browse/JDK-8207009
>
> I appreciate if you can help test if we have a patch.
>
> Thanks,
> Xuelei
>
> On 7/17/2018 4:26 PM, Tim Brooks wrote:
>>
Property as a workaround.
>
> Thanks,
> Xuelei
>
> On 7/18/2018 11:51 AM, Tim Brooks wrote:
>> Yes. I can test once there is a patch. My inquiry was motivated by some work
>> on Elasticsearch fyi. I can test a patch against that work.
>> https://github.
er, existing applications may not did
> this way because TLS 1.2 and prior version can work around it. But for TLS
> 1.3, it is possible to hang the application if the connection is not closed.
> If the source code update is not available, please consider to use the
> "jdk.tls.
case that I can use to
> reproduce the issues?
>
> Thanks,
> Xuelei
>
> On 8/3/2018 5:04 PM, Tim Brooks wrote:
>> Hi Xuelei
>> I pulled the JDK 11 source today and applied your patch. And then I built
>> the jdk to run some tests. I hope that is the correct app
ote:
>
> Hi Tim,
>
> Your concerns make sense to me. Did you have a test case that I can use to
> reproduce the issues?
>
> Thanks,
> Xuelei
>
> On 8/3/2018 5:04 PM, Tim Brooks wrote:
>> Hi Xuelei
>> I pulled the JDK 11 source today and applied your pa
Hi Xuelei,
My test passed using that patch. I’ll continue to explore over the next few
days. But that patch resolves the main issues that I had encountered.
Thanks,
- Tim
> On Aug 7, 2018, at 8:54 AM, Xuelei Fan wrote:
>
> Xuelei
