RFR 8220570: Additonal trace when native thread creation fails
david.holmes at oracle.com
Fri Mar 22 07:09:16 UTC 2019
On 21/03/2019 8:06 pm, Schmelter, Ralf wrote:
> Hi David,
> here is the new webrev. We now trace at the info level and include the number of Java threads.
That seems okay to me. Only nit is that I would expand Nr to read
Number. No need for new webrev.
> Best regards,
> -----Original Message-----
> From: David Holmes <david.holmes at oracle.com>
> Sent: Mittwoch, 20. März 2019 06:51
> To: Schmelter, Ralf <ralf.schmelter at sap.com>; hotspot-runtime-dev at openjdk.java.net
> Subject: Re: RFR 8220570: Additonal trace when native thread creation fails
> Hi Ralf,
> On 19/03/2019 8:14 pm, Schmelter, Ralf wrote:
>> Hi David,
>> what about lowering the log level to info? Would you think the amount of detail would be OK for that? And if yes, would the first implementation (the one with the lengthy output) be OK, since it saves quiet a lot of program code?
> The original version at "info" would be acceptable to me.
> But as Goetz suggested, adding a small amount of additional detail to
> the existing warning (e.g. number of running threads) is also okay.
>> Best regards,
More information about the hotspot-runtime-dev