Permission Violation when trying to view bug JDK-8016309
stefan.karlsson at oracle.com
Tue Oct 1 11:14:28 UTC 2013
On 10/01/2013 11:34 AM, Volker Simonis wrote:
> Hi Stefan,
> thanks for the information. So does this mean that every bug report
> which contains some kind of "internal" URLs will be marked
> confidential automatically by the bug system? It would be interesting
> to know which URLs are objected to avoid putting such URLs in a bug
> report. Otherwise it may happen that I create a bug to which I will
> have no access later on because it included such an offending URL.
I'm not sure what the current proceedures are. Hopefully someone with
more insight into this will answer.
When JBS was opened all bugs with internal URLs in the summary were
marked as confidential. Internal URLs in the comments only hid those
> Is it possible to manually remove the confidential flag if the author
> judges that it may be appropriate?
I don't think so, but I might be wrong.
> On Tue, Oct 1, 2013 at 11:05 AM, Stefan Karlsson
> <stefan.karlsson at oracle.com> wrote:
>> Hi Volker,
>> On 10/01/2013 10:48 AM, Volker Simonis wrote:
>>> when trying to look at certain bugs like for example
>>> https://bugs.openjdk.java.net/browse/JDK-8016309 I am asked to log in
>>> to the JIRA system. However if I'm doing so I get the following error
>>> Permission Violation
>>> It seems that you have tried to perform an operation which you are not
>>> permitted to perform.
>>> If you think this message is wrong, please contact your JIRA
>>> What does this exactly mean?
>> The bug was marked 'confidential' because it mentions Oracle internal URLs
>> from our testing in the summary.
>> This is rather unfortunate and it's something bug reporters need to be more
>> cautious about going forward.
>>> Notice that the fix for JDK-8016309 is currently under review on the
>>> hotspot-gc-dev list so it seems odd that the bug itself is not
More information about the discuss