Re: JEP 158 support for JIT

a On 2017/01/03 12:00, Vladimir Kozlov wrote: On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: Hi all, Java 9 has JEP 158: Unified JVM Logging. This JEP describes that existing 'tty->print...' logging should use unified logging as output. However, C2 compiler does not seem to use it. D

Re: JEP 158 support for JIT

gt; On Jan 2, 2017, at 6:08 PM, Yasumasa Suenaga wrote: >>>>> >>>>> Thanks Vladimir, >>>>> >>>>>> Definitely not in JDK 9. And I can't say when it could be done or done >>>>>> at all. >>>>> >>>>> I hope this

Re: JEP 158 support for JIT

o difficult. Yasumasa On 2017/01/03 12:00, Vladimir Kozlov wrote: On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: Hi all, Java 9 has JEP 158: Unified JVM Logging. This JEP describes that existing 'tty->print...' logging should use unified logging as output. However, C2 compiler doe

Re: JEP 158 support for JIT

e: Thanks Vladimir, Definitely not in JDK 9. And I can't say when it could be done or done at all. I hope this feature will be implemented ASAP. Yasumasa On 2017/01/03 12:00, Vladimir Kozlov wrote: On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: Hi all, Java 9 has JEP 158: Unified JVM Lo

Re: JEP 158 support for JIT

ation. Shouldn’t be too difficult. Yasumasa On 2017/01/03 12:00, Vladimir Kozlov wrote: On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: Hi all, Java 9 has JEP 158: Unified JVM Logging. This JEP describes that existing 'tty->print...' logging should use unified logging as output. However

Re: JEP 158 support for JIT

I can't say when it could be done or done >> at all. > > I hope this feature will be implemented ASAP. > > > > Yasumasa > > > > On 2017/01/03 12:00, Vladimir Kozlov wrote: > >> On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: >> >>> Hi all,

Re: JEP 158 support for JIT

tation. Shouldn’t be too difficult. > > > Yasumasa > > > On 2017/01/03 12:00, Vladimir Kozlov wrote: >> On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: >>> Hi all, >>> >>> Java 9 has JEP 158: Unified JVM Logging. >>> This JEP describes that e

Re: JEP 158 support for JIT

done or done at all. I hope this feature will be implemented ASAP. You can always contribute an implementation. Shouldn’t be too difficult. Yasumasa On 2017/01/03 12:00, Vladimir Kozlov wrote: On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: Hi all, Java 9 has JEP 158: Unified JVM Logging.

Re: JEP 158 support for JIT

Thanks Vladimir, Definitely not in JDK 9. And I can't say when it could be done or done at all. I hope this feature will be implemented ASAP. Yasumasa On 2017/01/03 12:00, Vladimir Kozlov wrote: On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: Hi all, Java 9 has JEP 158: Unified JVM Lo

Re: JEP 158 support for JIT

On 1/2/17 6:33 PM, Yasumasa Suenaga wrote: Hi all, Java 9 has JEP 158: Unified JVM Logging. This JEP describes that existing 'tty->print...' logging should use unified logging as output. However, C2 compiler does not seem to use it. Do you have any plan to use JEP 158

JEP 158 support for JIT

Hi all, Java 9 has JEP 158: Unified JVM Logging. This JEP describes that existing 'tty->print...' logging should use unified logging as output. However, C2 compiler does not seem to use it. Do you have any plan to use JEP 158 in JIT codes? I uploaded Unified JVM logging viewer

Re: JEP 158: Unified JVM Logging

tool. I want to merge it by Feature Complete. Thanks, Yasumasa 2015/10/16 22:55 "Yasumasa Suenaga" : Hi all, I contributed JDK-7090324: gclog rotation via external tool to be synchronized with logrotated tool on Linux. I think JEP 158 is in progress. However, this JEP does not c

Re: JEP 158: Unified JVM Logging

external tool to be > synchronized with > logrotated tool on Linux. > > I think JEP 158 is in progress. > However, this JEP does not contain log rotation via external tool in the > spec. > I want to rotate logs via jcmd in this JEP. > > I've updated a patch for it: > >

JEP 158: Unified JVM Logging

Hi all, I contributed JDK-7090324: gclog rotation via external tool to be synchronized with logrotated tool on Linux. I think JEP 158 is in progress. However, this JEP does not contain log rotation via external tool in the spec. I want to rotate logs via jcmd in this JEP. I've updated a

Re: Updates to JEP-158: JVM Unified Logging are coming...

add guide lines for the expected verbosity of log levels, either in terms of datasize/time or messages/time. I look forward to this logging system in practice! Kind Regards, Thomas On Fri, Apr 17, 2015 at 9:32 AM, Fredrik Arvidsson < fredrik.arvids...@oracle.com> wrote: > Hi > &

Re: Updates to JEP-158: JVM Unified Logging are coming...

On Apr 17, 2015, at 11:29 AM, Fredrik Arvidsson wrote: > Hi > Ill try to reply in-line below. > > On 2015-04-17 10:27, Mattis Castegren wrote: >> Ok. One risk I see would be that you would forget "base tags". For example, >> if you write a lot of code in g1, it would be easy to log something

Re: Updates to JEP-158: JVM Unified Logging are coming...

/Mattis > > > > From: Fredrik Arvidsson > Sent: den 17 april 2015 14:36 > To: Martijn Verburg > Cc: serviceability-dev@openjdk.java.net serviceability-dev@openjdk.java.net; > hotspot-...@openjdk.java.net Source Developers > Subject: Re: Updates to JEP-158: JVM Unifi

RE: Updates to JEP-158: JVM Unified Logging are coming...

@openjdk.java.net; hotspot-...@openjdk.java.net Source Developers Subject: Re: Updates to JEP-158: JVM Unified Logging are coming...   Hi Martijn, and the others :) I'm glad you like what we do. We also think the tag based logging is something good, and that it will make the logging in the JVM e

Re: Updates to JEP-158: JVM Unified Logging are coming...

On 17 April 2015 at 09:32, Fredrik Arvidsson mailto:fredrik.arvids...@oracle.com>> wrote: Hi We are planning to release an updated version of JEP-158 very soon. The work to update this JEP has been going on for some time and we now feel we are ready to present it to a wid

Re: Updates to JEP-158: JVM Unified Logging are coming...

ce Logging? Human readable is nice for looking at logs immediately, but for some of our customers they'd be looking to offload that concern to another process/host. Cheers, Martijn On 17 April 2015 at 09:32, Fredrik Arvidsson wrote: > Hi > > We are planning to release an updated

Re: Updates to JEP-158: JVM Unified Logging are coming...

't see that there is another way really :( Cheers /Fredrik Kind Regards /Mattis -Original Message- From: Fredrik Arvidsson Sent: den 17 april 2015 10:14 To: Mattis Castegren; serviceability-dev@openjdk.java.net serviceability-dev@openjdk.java.net; hotspot-...@openjdk.java.net Source

RE: Updates to JEP-158: JVM Unified Logging are coming...

rom a run, we would have to ask customers to run with "Xverbose:gc,g1,g1_init,g1_other_module,..." Kind Regards /Mattis -Original Message- From: Fredrik Arvidsson Sent: den 17 april 2015 10:14 To: Mattis Castegren; serviceability-dev@openjdk.java.net serviceability-dev@openj

Re: Updates to JEP-158: JVM Unified Logging are coming...

nal Message- From: Fredrik Arvidsson Sent: den 17 april 2015 09:33 To: serviceability-dev@openjdk.java.net serviceability-dev@openjdk.java.net; hotspot-...@openjdk.java.net Source Developers Subject: Updates to JEP-158: JVM Unified Logging are coming... Hi We are planning to release an updated ver

RE: Updates to JEP-158: JVM Unified Logging are coming...

ceability-dev@openjdk.java.net; hotspot-...@openjdk.java.net Source Developers Subject: Updates to JEP-158: JVM Unified Logging are coming... Hi We are planning to release an updated version of JEP-158 very soon. The work to update this JEP has been going on for some time and we now feel we are

Updates to JEP-158: JVM Unified Logging are coming...

Hi We are planning to release an updated version of JEP-158 very soon. The work to update this JEP has been going on for some time and we now feel we are ready to present it to a wider audience. The JEP for JVM Unified Logging was created back in February 2012. The requirements for the API

Re: Need comments on JEP-158: Unified JVM Logging

suggestion of tagging partial >> lines would be a great help to log tool writers. >> > There could be several reasons for the current logs to be interleaved I > think. One reason can be that the lowest level log writing primitives > aren't thread safe themselves. > A sec

Re: Need comments on JEP-158: Unified JVM Logging

Hi Mario, thanks for the feedback! Pleas see my comments in-lined below. On 2014-05-16 13:41, Mario Torre wrote: On Fri, 2014-05-16 at 11:45 +0100, Richard Warburton wrote: Hi, Hi all, I share this same doubts, and I'm also a bit confused. I'm not saying that an abstract framework should de

Re: Need comments on JEP-158: Unified JVM Logging

Hi Thomas and thanks for the feedback. Interesting to see that you already have a design that is so close to what we are proposing in this JEP. I have added some comments in-line below. On 2014-05-20 09:59, Thomas Stüfe wrote: Hi all, I like you proposal and hope this tracing system turns ou

Re: Need comments on JEP-158: Unified JVM Logging

to implement the logging in a way that guarantees non partial lines in the log. JEP-158 tries to address both of these reasons. Thread safety issues can be addressed using the leanest locking/critical section technique we can have. This might have different solutions depending on platform an

Re: Need comments on JEP-158: Unified JVM Logging

Hi Martijn Thank you for doing that. I'm afraid it is going to be hard enough anyway to keep myself updated on all feedback given :) For me it is a matter of course that these kind of discussions should be held in the open. We are all stake holders in this. As long as the discussion does not tu

Re: Need comments on JEP-158: Unified JVM Logging

Hi Dmitry, thanks for the feedback. I will comment in-line below. On 2014-05-16 15:40, Dmitry Samersoff wrote: Fredrik, 1. I'm not sure we have to provide user-configurable decoration. It add complication to logger because not all decorations available for all components and it creates

Re: Need comments on JEP-158: Unified JVM Logging

Hi Fredrik, I've asked all of the discussions on our list to be fed back here or directly to you. Thanks for opening the discussion, we really appreciate it! Cheers, Martijn On Sunday, 18 May 2014, Fredrik Arvidsson wrote: > Hi Richard > > I will add more text in the JEP describing the intent

Re: Need comments on JEP-158: Unified JVM Logging

Hi all On 2014-05-18 12:14, Kirk Pepperdine wrote: Hi Fredrik, I do need more information but I think a flat structure would provide less overhead rather than passing messages through a network of “sub” loggers. Kirk, I can understand that you are concerned that the hierarchical structure wou

Re: Need comments on JEP-158: Unified JVM Logging

Hi Fredrik, I do need more information but I think a flat structure would provide less overhead rather than passing messages through a network of “sub” loggers. Peter Lawrey wrote JChronicle which at it’s core is a messaging system but it’s also a wickedly fast logger. That said, there isn’t a

Re: Need comments on JEP-158: Unified JVM Logging

or post-execution log tool writers > it is also useful for end users to be able to easily locate and load a > single log file. > > Kind regards, > > Chris > > [1] https://github.com/AdoptOpenJDK/jitwatch > >>>> -- Forwarded message

Re: Need comments on JEP-158: Unified JVM Logging

Hi Richard I will add more text in the JEP describing the intent of the hierarchical logger design. As you said, it is not that clear in the current one. Thanks. Regarding out off band discussions. I have noted that and I will try to keep myself updated to that. It is not optimal to have dis

Re: Need comments on JEP-158: Unified JVM Logging

Hi Fredrik, In the JEP I tried to explain the concept of 'sub' loggers but I did not > put in anything about the intent of having them. I think that your > requirement easily could be solved using sub loggers, or sub components if > you like that wording better. > > Loggers are ordered in an hiera

Re: Need comments on JEP-158: Unified JVM Logging

sers to be able to easily locate and load a single log file. Kind regards, Chris [1] https://github.com/AdoptOpenJDK/jitwatch >>> -- Forwarded message -- >>> From: Fredrik Arvidsson >>> Date: 16 May 2014 09:47 >>> Subject: Need

Re: Need comments on JEP-158: Unified JVM Logging

wrote: > Hi all > Please help me review this updated version of the JEP-158 Unified JVM > Logging that was pushed today to the JEP repository. > > Since the service posting the JEPs to http://openjdk.java.net/jeps/ site > seems to be non working at the moment I am linking direct

Re: Need comments on JEP-158: Unified JVM Logging

On Fri, 2014-05-16 at 11:45 +0100, Richard Warburton wrote: > Hi, Hi all, I share this same doubts, and I'm also a bit confused. > I'm not saying that an abstract framework should depend upon the details of > the different components but if you had component definable markers for the > type of i

Re: Need comments on JEP-158: Unified JVM Logging

ly could solve the requirements by using sub loggers instead. Please tell me if you don't think this approach would work, and in that case why. Regards /Fredrik // Adding back hotspot-dev.openjdk.java.net // On 2014-05-16 12:45, Richard Warburton wrote: Hi, Please help me review

Re: Need comments on JEP-158: Unified JVM Logging

Hi, Please help me review this updated version of the JEP-158 Unified JVM > Logging that was pushed today to the JEP repository. > > Since the service posting the JEPs to http://openjdk.java.net/jeps/ site > seems to be non working at the moment I am linking directly to the HG

Need comments on JEP-158: Unified JVM Logging

Hi all Please help me review this updated version of the JEP-158 Unified JVM Logging that was pushed today to the JEP repository. Since the service posting the JEPs to http://openjdk.java.net/jeps/ site seems to be non working at the moment I am linking directly to the HG repository instead

Re: JEP 158: Unified JVM logging

I'll only add to this that an option to provide a Human Readable format out of the box would be desirable, but not as a default. On 15 August 2012 09:44, Kirk Pepperdine wrote: > Hi Dmitry, > > Lets start with this. > > Common logging command-line options for all components > Logging is performed

Re: JEP 158: Unified JVM logging

On 17 aug 2012, at 22:32, Kirk Pepperdine wrote: >> >> The suggestion in the JEP is that each category/component has several >> levels, so in that sense they are not independent. To enable logging you >> would specify a list of {component, level} tuples, like: >> >> gc:info, younggen:trace >

Re: JEP 158: Unified JVM logging

Hi Staffan, Thanks for the response. You call it levels, I call is at hierarchy. I'm happy to change to the work levels. On 2012-08-17, at 10:20 PM, Staffan Larsen wrote: > > On 15 aug 2012, at 16:19, Dmitry Samersoff > wrote: > >> On 2012-08-15 12:44, Kirk Pepperdine wrote: >> >>> The cu

Re: JEP 158: Unified JVM logging

On 15 aug 2012, at 16:19, Dmitry Samersoff wrote: > On 2012-08-15 12:44, Kirk Pepperdine wrote: > >> The current system of command-line (experimental) options follow a >> format that is quite consistent. The options provide semantic meaning as >> to what will be logged. This semantic meaning is

Re: JEP 158: Unified JVM logging

Hi, I would agree that there are great merits to tag-based systems instead of hierarchical systems. However, the JEP does not have a hierarchical system in mind. Components, as the JEP refers to them, are not hierarchical, but they are disjunct. Disjunct in the sense that a particular log outpu

Re: JEP 158

I don't think the JEP has been updated, only published. I have not had time to do any changes to it. /Staffan On 10 jul 2012, at 17:16, Kirk Pepperdine wrote: > Hi Staffan, > > I've noticed that the specification has been updated but still contains the > hierarchical level system. Is it you

Re: JEP 158: Unified JVM logging

Kirk, Please see below. ** Staffan, please correct me if I misunderstood something. On 2012-08-15 12:44, Kirk Pepperdine wrote: > Hi Dmitry, > > Lets start with this. > > * Common logging command-line options for all components > * Logging is performed at different levels: error, warning,

Re: JEP 158: Unified JVM logging

On 2012-08-15, at 3:28 PM, Dmitry Samersoff wrote: > Kirk, > > On 2012-08-15 12:56, Kirk Pepperdine wrote: >> I should have added that Neal Ford has an excellent talk on taxonomy systems >> and tags vs. hierarchies. >> It includes a bit on the 5 kingdoms that all organisms are split into. Yet

Re: JEP 158: Unified JVM logging

Kirk, On 2012-08-15 12:56, Kirk Pepperdine wrote: > I should have added that Neal Ford has an excellent talk on taxonomy systems > and tags vs. hierarchies. > It includes a bit on the 5 kingdoms that all organisms are split into. Yet > many organisms show characteristics > from more than one k

Re: JEP 158: Unified JVM logging

On 2012-08-15, at 11:29 AM, Dmitry Samersoff wrote: > Kirk, > > Thank you. I'm downloading it. > > PS: > Tags vs hierarchy discussion is as old as taxonomy it self. which is why I'm surprised we're here ;-) Kirk

Re: JEP 158: Unified JVM logging

Kirk, Thank you. I'm downloading it. PS: Tags vs hierarchy discussion is as old as taxonomy it self. -Dmitry On 2012-08-15 13:25, Kirk Pepperdine wrote: > Hi Dmitry, > > Neal Ford talk is call "Abstraction Distraction".. it's downloadable and > you can see it here. http://vimeo.com/44235657 >

Re: JEP 158: Unified JVM logging

Hi Dmitry, Neal Ford talk is call "Abstraction Distraction".. it's downloadable and you can see it here. http://vimeo.com/44235657 -- Kirk On 2012-08-14, at 12:17 PM, Dmitry Samersoff wrote: > Kirk, > >> However I do have very serious concerns about this JEP in that it >> doesn't fix the pr

Re: JEP 158: Unified JVM logging

Hi Dmitry, I should have added that Neal Ford has an excellent talk on taxonomy systems and tags vs. hierarchies. It includes a bit on the 5 kingdoms that all organisms are split into. Yet many organisms show characteristics from more than one kingdom while some others show characteristics of n

Re: JEP 158: Unified JVM logging

Hi Dmitry, Lets start with this. Common logging command-line options for all components Logging is performed at different levels: error, warning, info, debug, trace Logging messages are in human-readable plain text IMHO, these current set of goals are based on the assumptions that all component

Re: JEP 158: Unified JVM logging

Hi, Other softwares (e.g. syslog, apache) are implemented log rotation support. When these software receives SIGHUP, they close current log and reopen it. I think that JVM should be supported same level of log management at least. Current implementation, JVM open logs at start, and never close i

JEP 158: Unified JVM logging

Kirk, > However I do have very serious concerns about this JEP in that it > doesn't fix the problems that exist in current logging frameworks, > it only mimics them. > http://openjdk.java.net/jeps/158 Any comments is much appreciated. Personally, I think that log rotation is out of scope and re

Re: JEP 158

Hi Staffan, I've noticed that the specification has been updated but still contains the hierarchical level system. Is it your intention to maintain level in the specification? Regards, Kirk On 2012-06-20, at 12:50 PM, Staffan Larsen wrote: > Hi, > > Thanks for the feedback! > > It is goin

Re: JEP 158

> >>> >>> I understand what you want and I see that the logging level won't help us >>> get there. I don't agree that the logging we have today can't fit nicely >>> into a hierarchical scheme though, it just needs to be more fine grained to >>> achieve what you want. >> >> I think to do this

Re: JEP 158

Hi Staffan, I should have added, the existing frameworks are very developer oriented and that's ok except that more often than not if operational people that are looking at these logs and their perspective and purpose is often quite different. I would just like to bring a more operational POV i

Re: JEP 158

Hi Jesper, On 2012-06-20, at 9:32 AM, Jesper Wilhelmsson wrote: > Hi Kirk, > > I'm CC'ing serviceability on this since this is really their JEP and > discussions around it should go on the serviceability list, even though it > seems you are mainly interested in GC logging at this point. I'm

Re: JEP 158

Hi Staffan, > Thanks for the feedback! > > It is going to be hard to find the right balance between a system that > provides great power and one that is simple to use and to implement. In > general, I will lean more towards making it simple, but I want to make sure > we cover the major use ca

Re: JEP 158

On 06/20/2012 02:07 PM, Kirk Pepperdine wrote: Hi Staffan, Thanks for the feedback! It is going to be hard to find the right balance between a system that provides great power and one that is simple to use and to implement. In general, I will lean more towards making it simple, but I want to

Re: JEP 158

Hi Kirk, 20 jun 2012 kl. 10:33 skrev Kirk Pepperdine >: Hi Jesper, On 2012-06-20, at 9:32 AM, Jesper Wilhelmsson wrote: Hi Kirk, I'm CC'ing serviceability on this since this is really their JEP and discussions around it should go on the serviceability list, even

Re: JEP 158

Hi, Thanks for the feedback! It is going to be hard to find the right balance between a system that provides great power and one that is simple to use and to implement. In general, I will lean more towards making it simple, but I want to make sure we cover the major use cases as well. It loo

Re: JEP 158

Hi Kirk, I'm CC'ing serviceability on this since this is really their JEP and discussions around it should go on the serviceability list, even though it seems you are mainly interested in GC logging at this point. I understand what you want and I see that the logging level won't help us get

JEP 158: Unified JVM Logging

Posted: http://openjdk.java.net/jeps/158 - Mark