On Fri, 5 Nov 2021 22:55:16 GMT, Jamil Nimeh wrote:
>> This fix handles cases where two or more threads may be acting on a single
>> SSLSocket instance. In cases where one thread closes the socket while the
>> other is in the middle of a read, a SocketException is appropriately thrown,
>> but
On Fri, 5 Nov 2021 22:30:50 GMT, Bradford Wetmore wrote:
>> Jamil Nimeh has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Do not reinstantiate SSLContext, add more iterations, add test batch
>> without using session tickets
>
> test/jdk/s
> This fix handles cases where two or more threads may be acting on a single
> SSLSocket instance. In cases where one thread closes the socket while the
> other is in the middle of a read, a SocketException is appropriately thrown,
> but it results in SSLSession invalidation even though the ses
On Fri, 5 Nov 2021 17:23:40 GMT, Jamil Nimeh wrote:
>> This fix handles cases where two or more threads may be acting on a single
>> SSLSocket instance. In cases where one thread closes the socket while the
>> other is in the middle of a read, a SocketException is appropriately thrown,
>> but
> This fix handles cases where two or more threads may be acting on a single
> SSLSocket instance. In cases where one thread closes the socket while the
> other is in the middle of a read, a SocketException is appropriately thrown,
> but it results in SSLSession invalidation even though the ses
On Tue, 2 Nov 2021 14:03:50 GMT, Jamil Nimeh wrote:
>> This fix handles cases where two or more threads may be acting on a single
>> SSLSocket instance. In cases where one thread closes the socket while the
>> other is in the middle of a read, a SocketException is appropriately thrown,
>> but
> This fix handles cases where two or more threads may be acting on a single
> SSLSocket instance. In cases where one thread closes the socket while the
> other is in the middle of a read, a SocketException is appropriately thrown,
> but it results in SSLSession invalidation even though the ses
> This fix handles cases where two or more threads may be acting on a single
> SSLSocket instance. In cases where one thread closes the socket while the
> other is in the middle of a read, a SocketException is appropriately thrown,
> but it results in SSLSession invalidation even though the ses
On Mon, 1 Nov 2021 18:28:54 GMT, Jamil Nimeh wrote:
> This fix handles cases where two or more threads may be acting on a single
> SSLSocket instance. In cases where one thread closes the socket while the
> other is in the middle of a read, a SocketException is appropriately thrown,
> but it
This fix handles cases where two or more threads may be acting on a single
SSLSocket instance. In cases where one thread closes the socket while the
other is in the middle of a read, a SocketException is appropriately thrown,
but it results in SSLSession invalidation even though the session was
10 matches
Mail list logo
