Hi,
Sorry for my late reply.
I think being able to force rotation via jcmd seems like a good feature.
Files are currently opened in append mode so it should already be
possible to use external log rotation tools by copying and truncating
the files. Still I think it would be nice to provide th
Hi all,
Have you ever seen my change?
I (and my customers) need log rotation function via external 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
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 patch f
Hi all,
I like you proposal and hope this tracing system turns out well.
I'm with the SAP JVM; we have had our own homebrewn tracing system for
years, which resembles your proposal a lot. If your solution turns out
well, we may decide to abandon our propietary solution in favor of your
proposal.
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
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
Hi Chris
You will find my comments in-line below.
On 2014-05-17 09:47, Chris Newland wrote:
Hi Fredrik,
The discussion I had with David Holmes and John Rose on hotspot-dev back
in February might be relevant to this JEP:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2014-February/012718.ht
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
>
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
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
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
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,
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
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
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
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
>
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
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
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
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
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
Posted: http://openjdk.java.net/jeps/158
- Mark
37 matches
Mail list logo