[
https://issues.apache.org/jira/browse/LOG4J2-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jd updated LOG4J2-320:
--
Attachment: ProviderUtil.java
patch.diff
JPAAppender stops logging
-
[
https://issues.apache.org/jira/browse/LOG4J2-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731723#comment-13731723
]
jd commented on LOG4J2-320:
---
The problem was fixed by closing the stream that was opened when
Hi Nick,
The JIRA ticket is: https://issues.apache.org/jira/browse/LOG4J2-320
The solution for me as to close the inputstream that was opened when
loading the properties in ProviderUtil.java
I attached the patch and my changed version to the ticket just in case you
want to take a look.
Should I
Andre Bogus created LOG4J2-336:
--
Summary: AsyncLogger.log fail with NullPointerException after
double reconfigure
Key: LOG4J2-336
URL: https://issues.apache.org/jira/browse/LOG4J2-336
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-320:
Summary: JPAAppender stops logging because
META-INF/log4j-provider.properties is left open (was:
[
https://issues.apache.org/jira/browse/LOG4J2-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-320.
-
Resolution: Fixed
Fix Version/s: 2.0-beta9
{noformat}
commit -m [LOG4J2-320] JPAAppender
[
https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-336:
---
Description:
Using reconfigure() to select log files at runtime.
After the second reconfigure, the
[
https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733030#comment-13733030
]
Remko Popma commented on LOG4J2-336:
Thanks for finding this.
On reconfiguration, a
Hi JD,
This is how I see the workflow:
1. User reports issue, JIRA ticket gets raised.
2. Developer commits solution, marks JIRA ticket as Resolved.
3. User verifies that solution fixes the original problem and marks JIRA ticket
as Closed.
Variations:
Between 1 and 2, developers may ask for
