I'm also can not work around this bug. I need to emulate behavior of some proprietary log system, that always names log files as "module_yyyyMMddHHmmss.log" and rolls over only by file size trigger.
I'd like to use pattern like "module_%d
{yyyyMM}
%d
{ddHHmmss,aux}
.%i.log" with size based trigger. It's suitable to roll each month too, but when file size trigger acts, it creates new file with the same time stamp and new number. Actually I don't need the %i token because the log file can not overflow in one second. But omitting the %i token leads to NPE.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
I'm also can not work around this bug. I need to emulate behavior of some proprietary log system, that always names log files as "module_yyyyMMddHHmmss.log" and rolls over only by file size trigger.
I'd like to use pattern like "module_%d
{yyyyMM}%d
{ddHHmmss,aux}.%i.log" with size based trigger. It's suitable to roll each month too, but when file size trigger acts, it creates new file with the same time stamp and new number. Actually I don't need the %i token because the log file can not overflow in one second. But omitting the %i token leads to NPE.