On 12/01/18 13:17, Rory O'Donnell wrote:
> Hi Mark
> 
> How serious is this issue ?

Hi,

In terms of functionality, it isn't serious. As far as I can tell, there
are no functional side-effects for Tomcat.

However, the more I think about this, the more serious an issue I think
this will be. A large percentage of Tomcat users operate in environments
where any logging that even hints that something isn't right has to be
addressed. A stack trace to stdout would certainly get their attention.

I think we need a way to suppress this message. Without it a large
proportional Tomcat users won't be allowed by organisational policy to
run Tomcat on JDK 10. "Trust us. You can ignore that stack trace, it is
a known issue with Java 10 that doesn't cause any harm." isn't going to
be enough for most users.

My preference remains making that method protected so we can override it
and make it a NO-OP (Tomcat's custom LogManager handles this already).
However, I'd settle for anything that enabled that message to be suppressed.

> It's logged with a low priority, it might have to wait for JDK 11.

Understood.

Cheers,

Mark


> 
> Rgds,Rory
> 
> 
> 
> On 12/01/2018 11:39, Rory O'Donnell wrote:
>> Hi Mark,
>>
>> Thanks for the feedback, I'll pass it on.
>>
>> Rgds,Rory
>>
>>
>> On 12/01/2018 10:20, Mark Thomas wrote:
>>> On 18/12/17 09:56, Rory O'Donnell wrote:
>>>
>>> <snip/>
>>>
>>>> *Feedback* - If you have suggestions or encounter bugs, please submit
>>>> them using the usual Java SE bug-reporting channel.
>>>> Be sure to include complete version information from the output of the
>>>> |java --version| command.
>>> Hi,
>>>
>>> I did some testing on this today. I found a problem with our custom
>>> LogManager triggered by some fixes to the JRE LogManager.
>>>
>>> I've created a report via the standard mechanism as requested. The
>>> internal review ID is 9052225. Anything you can do to get this in front
>>> of the right folks to ensure it doesn't get overlooked would be
>>> appreciated.
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>>
>>
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to