RFR 8220570: Additonal trace when native thread creation fails

David Holmes david.holmes at oracle.com
Thu Mar 14 01:20:16 UTC 2019

Hi Ralf,

On 13/03/2019 10:17 pm, Schmelter, Ralf wrote:
> Hi,
> I've added additional trace in case an OS thread could not be created. Depending on the OS, not being able to create a thread could have many reasons. On Windows for example it should only be the result of not having enough memory, but on Linux it could be hitting other limits in addition. In order to keep the additional code needed small, I've would reuse methods already used in printing the limits to a hs_err* file, so it includes some which have no relevance for the failure (see the example in the bug report). But given the low occurrence of this errors, I think it should be OK.
> webrev: http://cr.openjdk.java.net/~rschmelter/webrevs/8220570/webrev.0/
> bugreport: https://bugs.openjdk.java.net/browse/JDK-8220570

I don't think it appropriate to add all that extra information dump at 
the "warning" level. Either it needs to be significantly reduced, or 
else moved to a lower level. Basic logging is not intended to suffice 
for remote support - YMMV.


> Best regards,
> Ralf Schmelter

More information about the hotspot-runtime-dev mailing list