Hi Nicolai,
On 19/08/16 16:21, Nicolai Parlog wrote:
Hi Daniel,
thanks for the quick reply. And you are of course right.
Luckily I don't care about the specific G1 message. After setting
everything up, I was looking for _anything_ that logs a message and that
was the first thing I came up wit
Hi Nicolai,
On 19/08/16 16:05, Nicolai Parlog wrote:
On a tangent, I also wondered what would be the preferred way to log
from inside my code. Should I use System::getLogger directly?
Logger logger = System.getLogger("Application");
logger.log(Level.INFO, "Hello, World!");
so
Hi Daniel,
thanks for the quick reply. And you are of course right.
Luckily I don't care about the specific G1 message. After setting
everything up, I was looking for _anything_ that logs a message and that
was the first thing I came up with. Forgot the "platform classes" in the
first sentence.
Hi Nicolai,
Log messages emitted by the JVM are not emitted through
the System.Logger API. JEP 264 is a pure Java API which
aims at replacing the sun.util.logging.PlatformLogger
implementation.
I believe what you are looking for is JEP 158
Unified JVM Logging [1]
best regards,
-- daniel
[1] h
Hi!
I'm trying out JEP 264: Platform Logging API and Service but can't get
it to work (or misunderstood something).
My understanding is that the JVM should use the provided LoggerFinder to
log its own messages. So when I start with "-verbose:gc" I expected the
message "Using G1" to go through my
