5 PM:
--
It's still not working for me, is it because I'm using a
{{RollingRandomAccessFileAppender}} instead of a {{RollingFileAppender}}?
*Update:* changing the appender "works", but the files have the time of the
next interval. I have a {{TimeBasedTriggeringPolicy}} with {{
2 PM:
-
It's still not working for me, is it because I'm using a
{{RollingRandomAccessFileAppender}} instead of a {{RollingFileAppender}}?
*Update:* changing the appender "works", but the files have the time of the
next interval. I have a {{TimeBasedTriggeringPolicy}} with {{
t because I'm using a
{{RollingRandomAccessFileAppender}} instead of a {{RollingFileAppender}}?
> Ability to change the fileName dynamically in RollingFileAppender
> -
>
> Key: LOG4J2-1185
&g
[
https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-239.
--
> RollingFileAppender should support logging directly to the file referenced in
> the fileP
[
https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-239.
Resolution: Fixed
Fix Version/s: 2.8
> RollingFileAppender should support logging direc
1101
> RollingFileAppender should support logging directly to the file referenced in
> the filePattern.
> --
>
> Key: LOG4J2-239
> URL: https://issues.apache.org/
bute entirely. The rolling file appender
will write directly to the target file using its pattern.
> Ability to change the fileName dynamically in RollingFileAppender
> -
>
> Key: LOG4J2-1185
>
ly in the official documentation.
> Ability to change the fileName dynamically in RollingFileAppender
> -
>
> Key: LOG4J2-1185
> URL: https://issues.apache.org/jira/browse/LOG4J2-1185
>
lity to change the fileName dynamically in RollingFileAppender
> -
>
> Key: LOG4J2-1185
> URL: https://issues.apache.org/jira/browse/LOG4J2-1185
> Project: Log4j 2
>
fileName dynamically in RollingFileAppender
> -
>
> Key: LOG4J2-1185
> URL: https://issues.apache.org/jira/browse/LOG4J2-1185
> Project: Log4j 2
> Issue Type: New Feature
>
and TimeBasedTrigger
> used simultaniously with RollingFileAppender
> --
>
> Key: LOG4J2-915
> URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/LOG4J2-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vaibhav singh resolved LOG4J2-1832.
---
Resolution: Fixed
> Programmatical Configuration of Log4j2 with RollingFileAppender does
d the classname to be printed.
>From the APIdoc:
includeLocation - whether location should be passed downstream
Maybe the documentation for the parameter could be made clearer, but for now, I
think I am satisfied. So, marking this question as Resolved.
> Programmat
hen SizeBasedTriggering and TimeBasedTrigger
> used simultaniously with RollingFileAppender
> --
>
> Key: LOG4J2-915
> URL: https://issues.apac
tp://pastebin.com/yBQ7mGPC
Output:
http://pastebin.com/cnfnqauz
> Programmatical Configuration of Log4j2 with RollingFileAppender does not
> honor logging classnames
> -
>
>
configured.
The final process will be to try to write to Logger "logger", which will have
an AppenderRef of "File" that might not exist. It will then log to the root
logger and do whatever that says.
> Programmatical Configuration of Log4j2 with RollingFi
vaibhav singh created LOG4J2-1832:
-
Summary: Programmatical Configuration of Log4j2 with
RollingFileAppender does not honor logging classnames
Key: LOG4J2-1832
URL: https://issues.apache.org/jira/browse/LOG4J2
hen SizeBasedTriggering and TimeBasedTrigger
> used simultaniously with RollingFileAppender
> --
>
> Key: LOG4J2-915
> URL: https://issues.apac
case.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.apache.org/jira/browse/LOG4J2-1640
> Project: Log4j 2
> Issue Type: Bug
&
lose this issue, then (if it isn't already
closed by now). I'm guessing this fix will make it into a 2.7.1 or 2.8 release.
Thanks so much, [~ralphgoers]!
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
>
ings correctly so far. This morning, it seems
everything in `Launcher.log` moved to `16 - Launcher.log` and it is now storing
today's (17th) data in `Launcher.log`. I'll let it run overnight tonight, see
how it looks in the morning, and let you know.
> RollingFileAppender with CronTrigge
and close if it works for
you.
> Ability to change the fileName dynamically in RollingFileAppender
> -
>
> Key: LOG4J2-1185
> URL: https://issues.apache.org/jira/browse/LOG4J2-1185
>
uild. If you want the rollover at
midnight then you can set your clock before starting the test application or
just let it roll at midnight. Otherwise you can change your pattern to have it
roll every hour or 2 instead of only at midnight.
> RollingFileAppender with CronTriggeringPolicy
is time, let it run overnight naturally rather than forcing a rollover with a
system clock change.)
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.
[
https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812875#comment-15812875
]
Matt Sicker commented on LOG4J2-1640:
-
Oh ok, got it.
> RollingFileAppend
tive to the time the server started
whereas Date and System.currentTimeMillis() are relative to the epoch. There
is no accurate way to coordinate them.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
>
{new Date(TimeUnit.NANOS.toMillis(nanoValue))}} or something
like that?
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.apache.org/jira/browse/LOG4J2-1640
>
[
https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1640.
-
Resolution: Fixed
Fix Version/s: 2.8
Please verify and close.
> RollingFileAppender w
the delay interval since there is no way to
associate a Date value with the nanotime clock. Adding a sleep to the run
method to handle the case where it is fired early has fixed the problem.
> RollingFileAppender with CronTriggeringP
cron event is firing a couple of
milliseconds early so the next event gets scheduled for the same time. Looking
into the cause.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
>
nnot get it to rollover twice again.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.apache.org/jira/browse/LOG4J2-1640
>
was in the target directory, however
the trace showed that rollover was attempted twice. I am investigating that.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
>
x27;t, and doesn't, show the rollover occurring.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.apache.org/jira/browse/LOG4J2-1640
>
not
guaranteed to occur at the exact instant it should and it cannot complete
instantaneously.
was (Author: [email protected]):
Yes, please post the latest trace output and sample log files.
> RollingFileAppender with CronTriggeringPolicy
odly-long, I have posted these to
Pastebin.
* Log4j's Trace: http://pastebin.com/H8mF1KPV
* "06 - Launcher-1.log": http://pastebin.com/vpYbUxrh
If you'd rather have them pasted elsewhere--in these comments or edited into
the original post--just let me know.
Thanks again.
&g
asted elsewhere--in these comments or edited into
the original post--just let me know.
Thanks again.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
>
and sample log files.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.apache.org/jira/browse/LOG4J2-1640
> Project: Log4j 2
>
ntents:
* "06 - Launcher.log" -- Contains logs from the 6th.
* "06 - Launcher-1.log" -- Contains logs from the 6th and the 7th.
* "06 - Launcher-2.log" -- Contains logs from the 7th and the 8th.
It's worth noting that the first of these files was created before I set
lo
aven. The steps are:
1. git clone http://git-wip-us.apache.org/repos/asf/logging-log4j2.git
2. cd logging-log4j2
3. mvn clean install.
At that point you will have all the Log4j jars in your local Maven repository.
> RollingFileAppender with CronTriggeringPolicy
figure
out how to make .jar files out of the -core and -api folders, though. May I
please have a little push in the right direction so I can test it out with my
project?
> RollingFileAppender with CronTriggeringPolicy broken?
> -
&
SO8601} [%t] %-5p [%c{50}#%M:%L] :
%m%n
4. could not get the daily roll over file of yesterday.
5. and get ERROR Unable to move file...
ERROR Unable to copy file..
> RollingFileAppender can't g
r? I suspect that they fix for
LOG4J2-1653 addressed this issue.
> RollingFileAppender can't generate daily file according to cron expressions
>
>
> Key: LOG4J2-1621
>
fix for LOG4J2-1653 which seems to have fixed this problem -
at least your app runs correctly for me.
Please verify and close if it works for you.
> Log4j RollingFileAppender every minute
> --
>
> Key: LOG4J2-1487
>
ster? I expect that the fixes for
LOG4J2-1653 have fixed the issue.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/LOG4J2-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1487:
Description:
http://stackoverflow.com/questions/38638105/log4j-rollingfileappender-every-minute
[
https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1640:
Priority: Major (was: Blocker)
> RollingFileAppender with CronTriggeringPolicy bro
html#producerconfigs
IMO, what needs to happen is convert the appender to using a builder and
then add a new setting.
The build changes are now in Git master. See Apache JIRA LOG4J2-1739.
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not
the issue:
https://github.com/apache/logging-log4j2/pull/50
Thanks for the message, I will wait until you're finished. Should I simply
checkin to master after you're done?
Vincent
> 2.7-rc1: RollingFileAppender immediateFlush default value should be t
uth/ABIfN78DuS3aamTbF8qD4mQ52DyFdqbzks5rIAqigaJpZM4LMKJB>
> .
>
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not
> false
> ---
>
> Key:
ay I can
also correct the PR to 1733.
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not
> false
> ---
>
> Key: LOG4J2-1620
> URL: https://
pull request at:
https://github.com/apache/logging-log4j2/pull/50
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not
> false
> ---
>
> Key: LOG4J2-1620
&g
the issue:
https://github.com/apache/logging-log4j2/pull/50
Yes, it is. I don't know why I entered 1620.
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true,
d on the issue:
https://github.com/apache/logging-log4j2/pull/50
This PR is about LOG4J2-1733, right?
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not
d on the issue:
https://github.com/apache/logging-log4j2/pull/50
The documentation in `src/site/xdoc/manual/appenders.xml` needs to be
updated.
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not
Add sync.send configuration property to Kafka Appender to
support asynchronous sends
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not
> false
> ---
>
>
this with building Git master sources?
We've had changes in this area that might matter for your use case.
> Log4j RollingFileAppender every minute
> --
>
> Key: LOG4J2-1487
> URL: https://issues.apache.org
; Log4j RollingFileAppender every minute
> --
>
> Key: LOG4J2-1487
> URL: https://issues.apache.org/jira/browse/LOG4J2-1487
> Project: Log4j 2
> Issue Type: Bug
> Components: App
shows an odd file naming issue when the
rollover happens at Midnight. Not sure if it's related, though.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: h
igure out how it could be anything else currently. Full disclosure: I am still
a newbie.
I've been using the log4j 2.6.x series for a while, but noticed that the
CronTriggeringPolicy when used with RollingFileAppender causes that infinite
rollover bug. I noted that this bug was to be fixed
etter and provide more detailed info.
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.apache.org/jira/browse/LOG4J2-1640
> Project: Lo
status="TRACE" and provide the resulting output?
> RollingFileAppender with CronTriggeringPolicy broken?
> -
>
> Key: LOG4J2-1640
> URL: https://issues.apache.org/jira/browse/LOG
Chris McGee created LOG4J2-1640:
---
Summary: RollingFileAppender with CronTriggeringPolicy broken?
Key: LOG4J2-1640
URL: https://issues.apache.org/jira/browse/LOG4J2-1640
Project: Log4j 2
Issue
hen SizeBasedTriggering and TimeBasedTrigger
> used simultaniously with RollingFileAppender
> --
>
> Key: LOG4J2-915
> URL: https://issues.apache.org/
ders
documentation|https://github.com/apache/logging-log4j2/blob/master/src/site/xdoc/manual/appenders.xml#L2211],
could you mention the default value for the new {{createOnDemand}} attribute?
> RollingFileAppender should be able to create files on
rc1: RollingFileAppender immediateFlush default value should be true, not
> false
> ---
>
> Key: LOG4J2-1620
> URL: https://issues.apache.org/jira/browse/LOG4J2-1620
>
close.
Gary
> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not
> false
> ---
>
> Key: LOG4J2-1620
> URL: https://issues.apache.org/jira/
[
https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1620:
-
Summary: 2.7-rc1: RollingFileAppender immediateFlush default value should
be true, not false
[
https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1620:
-
Affects Version/s: (was: 2.7)
> 2.7-rc1: RollingFileAppender immediateFlush default va
[
https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory reassigned LOG4J2-1620:
Assignee: Gary Gregory
> 2.7-rc1: RollingFileAppender immediateFlush default va
[
https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1620:
-
Affects Version/s: 2.7
> 2.7-rc1: RollingFileAppender immediateFlush default value chan
Tboy created LOG4J2-1621:
Summary: RollingFileAppender can't generate daily file according
to cron expressions
Key: LOG4J2-1621
URL: https://issues.apache.org/jira/browse/LOG4J2-1621
Project: Lo
Sascha Scholz created LOG4J2-1620:
-
Summary: 2.7-rc1: RollingFileAppender immediateFlush default value
changed
Key: LOG4J2-1620
URL: https://issues.apache.org/jira/browse/LOG4J2-1620
Project: Log4j 2
this? We are getting the exact same error.
> Log4j RollingFileAppender every minute
> --
>
> Key: LOG4J2-1487
> URL: https://issues.apache.org/jira/browse/LOG4J2-1487
> Project: Log4j 2
>
[
https://issues.apache.org/jira/browse/LOG4J2-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1574.
Resolution: Fixed
In Git master.
> Allow the RollingFileAppender to use default pattern lay
Gary Gregory created LOG4J2-1574:
Summary: Allow the RollingFileAppender to use default pattern
layout.
Key: LOG4J2-1574
URL: https://issues.apache.org/jira/browse/LOG4J2-1574
Project: Log4j 2
for you to test this with building Git master sources?
We've had changes in this area that might matter for your use case.
Thank you!
Gary
> Log4j RollingFileAppender every minute
> --
>
> Key: LOG4J2-1487
>
[
https://issues.apache.org/jira/browse/LOG4J2-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1504:
-
Description:
RollingFileAppender should be able to create files lazily.
Add a {{createOnDemand
[
https://issues.apache.org/jira/browse/LOG4J2-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1504:
-
Fix Version/s: 2.7
> RollingFileAppender should be able to create files on-dem
[
https://issues.apache.org/jira/browse/LOG4J2-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1504:
-
Description:
RollingFileAppender should be able to create files lazily.
Add a {{createOnDemand
[
https://issues.apache.org/jira/browse/LOG4J2-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-1504.
--
Resolution: Fixed
In Git master.
> RollingFileAppender should be able to create files
[
https://issues.apache.org/jira/browse/LOG4J2-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1504:
-
Summary: RollingFileAppender should be able to create files on-demand
(was: RollingFileAppender
" is more descriptive.
> RollingFileAppender should be able to create files lazily
> -
>
> Key: LOG4J2-1504
> URL: https://issues.apache.org/jira/browse/LOG4J2-1504
> Project: Lo
egory):
Hi All:
Should the option name be {{lazyCreate}} or {{createOnDemand}}?
I have {{lazyCreate}} now but when wrote the docs the term "on-demand" sounds
better and feels more accessible.
Thoughts?
Gary
> RollingFileAppender should be
e be {{lazyCreate}} or {{createOnDemand}}?
I have {{lazyCreate}} now but when wrote the docs the term "on-demand" sounds
better and feels more accessible.
Thoughts?
Gary
> RollingFileAppender should be able to cr
[
https://issues.apache.org/jira/browse/LOG4J2-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1504:
-
Fix Version/s: (was: 2.7)
> RollingFileAppender should be able to create files laz
[
https://issues.apache.org/jira/browse/LOG4J2-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1504:
-
Description:
RollingFileAppender should be able to create files lazily.
Add a {{lazyCreate
Gary Gregory created LOG4J2-1504:
Summary: RollingFileAppender should be able to create files lazily
Key: LOG4J2-1504
URL: https://issues.apache.org/jira/browse/LOG4J2-1504
Project: Log4j 2
Enrique Lamas created LOG4J2-1487:
-
Summary: Log4j RollingFileAppender every minute
Key: LOG4J2-1487
URL: https://issues.apache.org/jira/browse/LOG4J2-1487
Project: Log4j 2
Issue Type: Bug
Cheryl Mrozienski created LOG4J2-1462:
-
Summary: defer creation/open of RollingFileAppender log files when
level="OFF"
Key: LOG4J2-1462
URL: https://issues.apache.org/jira/browse/L
sing in log4j 2.x
See also:
http://stackoverflow.com/questions/30059333/log4j2-rolling-appender-filename-sliding-according-to-pattern
It has been missing for migrating from log4j 1.x, and various people have been
requesting, see also LOG4J2-907, LOG4J2-1185, ...
> RollingFileAppender should
f log4j 1.x > log4j2, this feature
would be more than welcome.
> Ability to change the fileName dynamically in RollingFileAppender
> -
>
> Key: LOG4J2-1185
> URL: https://issues.apache.
hen SizeBasedTriggering and TimeBasedTrigger
> used simultaniously with RollingFileAppender
> --
>
> Key: LOG4J2-915
> URL: https://issues.apac
hen SizeBasedTriggering and TimeBasedTrigger
> used simultaniously with RollingFileAppender
> --
>
> Key: LOG4J2-915
> URL: https://issues.apac
hen SizeBasedTriggering and TimeBasedTrigger
> used simultaniously with RollingFileAppender
> --
>
> Key: LOG4J2-915
> URL: https://issues.apac
tion.
> RollingFileAppender logs first log to old dated file
>
>
> Key: LOG4J2-1205
> URL: https://issues.apache.org/jira/browse/LOG4J2-1205
> Project: Log4j 2
>
s
are each an increment bigger than the previous.
%d{-MM-dd HH:mm:ss.SSS} [%10.10t]
%X{client} %-5p %c{2} - %m%n
file if the system is busy and the events are
processed before the rollover thread is allowed to run.
> RollingFileAppender logs first log to old dated file
>
>
> Key: LOG4J2-1205
> URL: https://iss
Taisuke Tashiro created LOG4J2-1205:
---
Summary: RollingFileAppender logs first log to old dated file
Key: LOG4J2-1205
URL: https://issues.apache.org/jira/browse/LOG4J2-1205
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers reassigned LOG4J2-1185:
---
Assignee: Ralph Goers
> Ability to change the fileName dynamically in RollingFileAppen
o be processed) and if it is, it
will also call Appender.flush() in addition to the above.
=
Note 1: The FlumeAppender uses a maxDelayMillis to address this.
Note 2: Could all synchronous appenders benefit from this improvement?
> Improve RollingFileAppender to avoid having stale
1 - 100 of 438 matches
Mail list logo
