Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
MIME-Version: 1.0
In-Reply-To: <7D1BF36B-50AC-41FF-BA7B-70C894B41BAB@gmail.com>
References: <DF0CFDD8-969D-4C5F-BE31-9E36D90C26DC@dslextreme.com>
	<pony-37dac5eb3044a9c143279b6f9cc836443c7d97c2-cb0ac320dbbe5a5ed1039e88204261d79a691538@log4j-user.logging.apache.org>
	<pony-37dac5eb3044a9c143279b6f9cc836443c7d97c2-4a957d22545ba21cf96b8888bd57f7a2371079e2@log4j-user.logging.apache.org>
	<CC977EAF-F2B3-4447-9248-314BD35DCA4A@dslextreme.com>
	<7D1BF36B-50AC-41FF-BA7B-70C894B41BAB@gmail.com>
Date: Wed, 15 Jun 2016 20:05:05 -0400
Message-ID: <CABRPL4rKu0KdtyDDjfhjZd_OTvhu05gYHBbhtuG==qwMPSpn=A@mail.gmail.com>
Subject: Re: OnStartupTriggeringPolicy/custom header
From: Leon Finker <leonfin@gmail.com>
To: Log4J Users List <log4j-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=001a1147452887021a053559fd20
archived-at: Thu, 16 Jun 2016 00:05:11 -0000

--001a1147452887021a053559fd20
Content-Type: text/plain; charset=UTF-8

As I remember they are not visible (protected).
On Jun 15, 2016 7:59 PM, "Remko Popma" <remko.popma@gmail.com> wrote:

> I would not use the drain(ByteBuffer) method directly because it would
> cause that message to appear in the log file ahead of the messages that are
> currently in the buffer but haven't been flushed yet.
>
> Have you looked at the parent OutputStreamManager class?
> Why not use one of the write(byte[], ...) methods? They correctly append
> to any existing messages.
>
> Remko
>
> Sent from my iPhone
>
> > On 2016/06/16, at 2:40, Ralph Goers <ralph.goers@dslextreme.com> wrote:
> >
> > Yes, the drain method should write whatever is in the ByteBuffer to the
> file.
> >
> > Ralph
> >
> >> On Jun 15, 2016, at 9:34 AM, Leon Finker <leonfin@gmail.com> wrote:
> >>
> >> An option to roll even empty files would be great. Because in our case
> we always want to roll the previous log file.
> >>
> >>> Actually, the triggering policy could write to the file since it has
> access to the Manager.
> >>
> >> I've looked through all the possible methods on RollingFileManager and
> nothing jumped out that allows us to write to the log file. I only see
> drain(ByteBuffer), is that the one to use? Writing from triggering policy
> seems to be the easiest way in our case.
> >>
> >>> On 2016-06-15 12:25 (-0400), Ralph Goers <ralph.goers@dslextreme.com>
> wrote:
> >>> I can add an option to the OnStartupTriggeringPolicy to only roll if
> the file meets or exceeds a minimum value. The default would be 1 byte.
> >>>
> >>> Also, I believe I introduced another bug.  The file is now going to
> roll every time a reconfiguration takes place, which is obviously
> incorrect. I need to fix that asap.
> >>>
> >>> The PatternLayout does not support interpolation of the header and
> footer but the Configuration does. All attributes are interpolated as the
> configuration is read.  You could create your own custom Lookup to get the
> processId, but that may be something we should add to the standard set of
> properties.
> >>>
> >>> Actually, the triggering policy could write to the file since it has
> access to the Manager.
> >>>
> >>> Ralph
> >>>
> >>>
> >>>
> >>>> On Jun 15, 2016, at 8:17 AM, Leon Finker <leonfin@gmail.com> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> What would be the best way to implement the following:
> >>>> 1. Always roll log file once on JVM startup (and only on JVM
> startup).  - This could be done with implementing another
> OnStartupTriggeringPolicy (the one from 2.6.1+ doesn't roll empty files
> anymore).
> >>>> 2. Log an entry in the new log file (after the roll) with something
> like:
> >>>> Constants.LINE_SEPARATOR + "---------- " + DateTime.now() + "
> STARTING " + service_instance_Name + " " + getProcessId() + " ----------"
> >>>> - Does PatternLayout's header support system property lookup
> variables (i.e.: service instance name and date time now)?
> >>>> - Not sure how to allow for custom method call to get the
> getProcessId() into the header
> >>>> - It could've been easy if I could do it from
> OnStartupTriggeringPolicy, but there is no way to write to the new rolled
> log file from there.
> >>>>
> >>>> Is there a way?
> >>>>
> >>>> Thank you
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>

--001a1147452887021a053559fd20--