RFR: 8349206: j.u.l.Handler classes create deadlock risk via synchronized publish() method

[Jason Mehrens]

On Thu, 13 Feb 2025 22:43:59 GMT, David Beaumont <duke at openjdk.org> wrote:

>Yes, it's certainly something you can deliberately provoke in a way that wasn't possible before.

Setting limit to 1 byte with a large count is a way to make sure each log file contains 0 or 1 log record.  I think this patch breaks that behavior when threads pile up resulting files containing 2 or more log records.  If so that is a breaking incompatibility that should be avoided as some formats only make sense to contain a single record or require post processing to be one record per file.

I'll answer your other questions as soon as I can.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/23491#discussion_r1955603117