FULL PRODUCT VERSION :


A DESCRIPTION OF THE PROBLEM :
Hi, previously I've submitted a comment which is recorded in JDK-8161917.

I think it was misinterpreted seeing the response
>> At this time I see no need for additional JBS issues open to track them. 

I did not write about additional issues, there is no need. 

The situation is as follows: 

There is JDK-8134843 which is open (submitted by me as well). It describes some observances for hard to investigate bug and has a bunch of duplicate/releted tickets attached. 

It doesn't describe exactly what the problem is nor the solution. It is just not clear from the ticket what the issue is, how to solve it and what is the effort. It requires developers time to dig in and understand.

On the other hand, JDK-8136536, which came from my message later and was closed as a duplicate, has a complete, elaborate analysis for the problem and what exactly should be fixed to solve it on code level.

Hence JDK-8136536 should be THE open ticket and JDK-8134843 with attached might be closed as its duplicate. 

Otherwise, one needs to open all duplicates to find relevant information which the open one (JDK-8134843) does not provide .

Also I don't understand why these messages created as separate tickets. 

This is a discussion on the existing ticket and should be in JDK-8134843 ticket comments, why create new ticket on each message. If messages were inserted properly as comments -  instead of new tickets - we had now just one ticket with comments instead of this multiple tickets havoc. 

Reagards, 
fedor.losev@gmail.com



REPRODUCIBILITY :
This bug can be reproduced always.