Hi Chris,
Good finding!
I agree with the principle, but I think that strictly speaking
it would be more correct if the server's workers ArrayList was
changed into a ConcurrentLinkedQueue.
The main could then poll the queue & join until it's empty
(or alternatively use forEach)
best regards,
-
> On 27 Sep 2018, at 11:51, Norman Maurer wrote:
>
> Forgot to ask… is it somehow possible to “subscribe” to an issue and get
> notified once there are some updates ?
Yes, you can “watch” an issue, component, or subcomponent, BUT
you need to be, at least, an OpenJDK author.
Unfortunately, I
Forgot to ask… is it somehow possible to “subscribe” to an issue and get
notified once there are some updates ?
Bye
Norman
> On 27. Sep 2018, at 12:18, Norman Maurer wrote:
>
> Thanks a lot.
>
> That would provide exactly what we need in netty.
>
> Bye
> Norman
>
>
>> On 27. Sep 2018, at
Reviving this RFR ...
In fact we don’t need to wait for jtreg b14, we can change the test now
and remove it from the problem list.
The issue with the test is that is creates non-daemon threads that
remain blocked in socket read until the HTTP keep-alive times out on the
client-side. This is fine,
Thanks a lot.
That would provide exactly what we need in netty.
Bye
Norman
> On 27. Sep 2018, at 12:09, Chris Hegarty wrote:
>
> Norman,
>
>> On 26 Sep 2018, at 12:45, Norman Maurer wrote:
>>
>> BTW I am happy to open an enhancement request for this with more details .
>> Just wanted to c
Norman,
> On 26 Sep 2018, at 12:45, Norman Maurer wrote:
>
> BTW I am happy to open an enhancement request for this with more details .
> Just wanted to check in first here :)
I searched the bug database to ensure that this request had
not come up before, and found nothing. I took the liberty
