Sure. I was not 100% sure if this is a bug or a configuration issue.
https://issues.apache.org/jira/browse/LOG4J2-2875
Greetings
Benjamin
On 2020-06-18 17:15, Ralph Goers wrote:
Thanks,
Would you mind creating a Jira issue and attaching this there?
Ralph
On Jun 18, 2020, at 8:12 AM, Benjami
Thanks,
Would you mind creating a Jira issue and attaching this there?
Ralph
> On Jun 18, 2020, at 8:12 AM, Benjamin Asbach wrote:
>
> I could reproduce the problem wiht some test code:
>
> ```
> import java.util.Properties;
> import org.apache.logging.log4j.core.Logger;
> import org.apache.l
I could reproduce the problem wiht some test code:
```
import java.util.Properties;
import org.apache.logging.log4j.core.Logger;
import org.apache.logging.log4j.core.LoggerContext;
import
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration;
import
org.apache.logging.log4j.co
Yes you're right the folder is not created.
Just additional information: We're using Java 1.8u151.
Greetings
Benjamin
On 2020-06-18 05:05, Ralph Goers wrote:
You don’t have a filename specified so it is trying to use
DirectWriteRolloverStrategy. You are using SizeBasedTriggeringPolicy
and don’
You don’t have a filename specified so it is trying to use
DirectWriteRolloverStrategy. You are using SizeBasedTriggeringPolicy and don’t
have %I in the pattern, which is normally required for a size based rollover.
However, that doesn’t seem to be a problem here.
I notice that the previous fil
Hi,
every night after rolling we experience IOExceptions when our logger
tries to log. So after midnight there's no logging to that log file at
all. The application is running on four WebLogic12 nodes. All nodes are
running on the same machine. All logs are going to the same directory.
The lo
