[jira] [Commented] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender
[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436635#comment-16436635 ] Carter Kozak commented on LOG4J2-2301: -- Not a problem, I'm not in a rush. Thanks! > gc-free mixed async loging loses parameter values after the first appender > -- > > Key: LOG4J2-2301 > URL: https://issues.apache.org/jira/browse/LOG4J2-2301 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.11.0 >Reporter: Carter Kozak >Assignee: Carter Kozak >Priority: Major > > When gc-free logging is used with mixed synchronous/asynchronous loggers, > parameter values are replaced with "null" after the first AsyncLoggerConfig. > The message format is still present, as well as the parameter count, however > all values are nulls. > It appears that Log4jEventWrapperHandler.onEvent invokes > MutableLogEvent.clear, which nulls out the parameter array. > I have constructed a failing test (which I need to clean up and deduplicate > some code from the fix for LOG4J2-2299): > https://github.com/cakofony/logging-log4j2/commit/b9c03f5c6881bfe778f8e2d75d046ce6e021c4f1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (LOG4J2-1705) Kotlin wrapper for Log4j 2 API
[
https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436406#comment-16436406
]
Matt Sicker edited comment on LOG4J2-1705 at 4/12/18 10:34 PM:
---
The site doesn't seem to build anything ({{mvn site}}). Not sure what's wrong
there. Other than that, I think we're ready to begin the release process over
on the mailing list where it'd be great to have your feedback as well.
Edit: we should also update the readme with a quick overview. This info can
generally be copied from elsewhere.
was (Author: jvz):
The site doesn't seem to build anything ({{mvn site}}). Not sure what's wrong
there. Other than that, I think we're ready to begin the release process over
on the mailing list where it'd be great to have your feedback as well.
> Kotlin wrapper for Log4j 2 API
> --
>
> Key: LOG4J2-1705
> URL: https://issues.apache.org/jira/browse/LOG4J2-1705
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
>Reporter: Raman Gupta
>Assignee: Matt Sicker
>Priority: Major
>
> Similar to LOG4J2-1181 for Scala, provide a Kotlin wrapper for the Log4j 2
> API that makes use of Kotlin features like delegates and string interpolation.
> If there is interest in this, I'd like to contribute a patch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (LOG4J2-1705) Kotlin wrapper for Log4j 2 API
[
https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436406#comment-16436406
]
Matt Sicker edited comment on LOG4J2-1705 at 4/12/18 10:33 PM:
---
The site doesn't seem to build anything ({{mvn site}}). Not sure what's wrong
there. Other than that, I think we're ready to begin the release process over
on the mailing list where it'd be great to have your feedback as well.
was (Author: jvz):
The site doesn't seem to build anything. Not sure what's wrong there. Other
than that, I think we're ready to begin the release process over on the mailing
list where it'd be great to have your feedback as well.
> Kotlin wrapper for Log4j 2 API
> --
>
> Key: LOG4J2-1705
> URL: https://issues.apache.org/jira/browse/LOG4J2-1705
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
>Reporter: Raman Gupta
>Assignee: Matt Sicker
>Priority: Major
>
> Similar to LOG4J2-1181 for Scala, provide a Kotlin wrapper for the Log4j 2
> API that makes use of Kotlin features like delegates and string interpolation.
> If there is interest in this, I'd like to contribute a patch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (LOG4J2-1705) Kotlin wrapper for Log4j 2 API
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436406#comment-16436406 ] Matt Sicker commented on LOG4J2-1705: - The site doesn't seem to build anything. Not sure what's wrong there. Other than that, I think we're ready to begin the release process over on the mailing list where it'd be great to have your feedback as well. > Kotlin wrapper for Log4j 2 API > -- > > Key: LOG4J2-1705 > URL: https://issues.apache.org/jira/browse/LOG4J2-1705 > Project: Log4j 2 > Issue Type: New Feature > Components: API >Reporter: Raman Gupta >Assignee: Matt Sicker >Priority: Major > > Similar to LOG4J2-1181 for Scala, provide a Kotlin wrapper for the Log4j 2 > API that makes use of Kotlin features like delegates and string interpolation. > If there is interest in this, I'd like to contribute a patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4NET-108) [PATCH] add support for multiple evaluators in BufferingAppenderSkeletan
[
https://issues.apache.org/jira/browse/LOG4NET-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436315#comment-16436315
]
Michael Schall commented on LOG4NET-108:
I realize this is an old ticket. However we needed something like this to
trigger the evaluator on a Level or a custom property. I implemented Nicko
Cadell's idea of a collection of evaluators.
Below is our implementation of a MultipleEvaluator. It has a list of
evaluators and can be in Any or All mode.
*MultipleEvaluator.cs*
{code:java}
public class MultipleEvaluator : ITriggeringEventEvaluator {
public enum MultipleEvaluatorMode {
Any,
All
}
private readonly List _evaluators = new
List();
public MultipleEvaluatorMode Mode { get; set; } =
MultipleEvaluatorMode.Any;
public void AddEvaluator(ITriggeringEventEvaluator evaluator) {
_evaluators.Add(evaluator);
}
public bool IsTriggeringEvent(LoggingEvent loggingEvent) {
switch (Mode) {
case MultipleEvaluatorMode.Any:
return _evaluators.Any(e =>
e.IsTriggeringEvent(loggingEvent));
case MultipleEvaluatorMode.All:
return _evaluators.All(e =>
e.IsTriggeringEvent(loggingEvent));
default:
throw new Exception("unknown mode: " + Mode);
}
}
}
{code}
We also created the following where you can specify a name/value of a property
that will trigger a flush (if value is not set it will trigger if the name is
present).
*PropertyValueEvaluator.cs*
{code:java}
public class PropertyValueEvaluator : ITriggeringEventEvaluator {
public string Name { get; set; }
public object Value { get; set; }
public bool IsTriggeringEvent(LoggingEvent loggingEvent) {
if (Value == null) {
return loggingEvent.Properties.Contains(Name);
}
return Equals(loggingEvent.Properties[Name], Value);
}
}
{code}
This can then be configured with the following xml (assuming the two new
Evaluators are in the log4net.Core namespace)
{code:xml}
{code}
> [PATCH] add support for multiple evaluators in BufferingAppenderSkeletan
>
>
> Key: LOG4NET-108
> URL: https://issues.apache.org/jira/browse/LOG4NET-108
> Project: Log4net
> Issue Type: Improvement
> Components: Appenders, Core
>Affects Versions: 1.2.10
>Reporter: Drew Schaeffer
>Assignee: Nicko Cadell
>Priority: Minor
> Fix For: 1.2/2.0 Maintenance Release
>
> Attachments: EvaluatorCollection.cs, patch-file.diff
>
>
> Currently BufferedAppenders only have support for one evaluator and one lossy
> evaluator. This is fine when the only available evaluator is LevelEvaluator
> (as multriple LevelEvaluators do not make sense) but with the addition of
> ExceptionEvaluator (LOG4NET-107) it would be nice for
> BufferingAppenderSkeletan to have a collection of evaluators.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2
[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435656#comment-16435656
]
Gary Gregory edited comment on LOG4J2-548 at 4/12/18 2:19 PM:
--
The patch needs to be updated to cleanly apply on top of either {{master}} or
{{release-2.x}}.
was (Author: garydgregory):
The patch needs to be updates to cleanly apply on top of either {{master}} or
{{release-2.x}}.
> Log4j 2.0 with JBoss EAP 6.2
> -
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0-rc1, 2.1
> Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler
>Reporter: Shehata
>Assignee: Ralph Goers
>Priority: Major
> Attachments: LOG4J2-548 - evictors.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message:
> "ERROR StatusLogger Could not search jar file
> 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core'
> for classes matching criteria: annotated with @Plugin file not found"
> after debugging the application found that the problem is located in :
> org.apache.logging.log4j.core.config.plugins.ResolverUtil
> method: findInPackage --> line number 247
> the protocol used in the jar is vfs not vfszip
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2
[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435656#comment-16435656
]
Gary Gregory commented on LOG4J2-548:
-
The patch needs to be updates to cleanly apply on top of either {{master}} or
{{release-2.x}}.
> Log4j 2.0 with JBoss EAP 6.2
> -
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0-rc1, 2.1
> Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler
>Reporter: Shehata
>Assignee: Ralph Goers
>Priority: Major
> Attachments: LOG4J2-548 - evictors.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message:
> "ERROR StatusLogger Could not search jar file
> 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core'
> for classes matching criteria: annotated with @Plugin file not found"
> after debugging the application found that the problem is located in :
> org.apache.logging.log4j.core.config.plugins.ResolverUtil
> method: findInPackage --> line number 247
> the protocol used in the jar is vfs not vfszip
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2
[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435497#comment-16435497 ] Martin edited comment on LOG4J2-548 at 4/12/18 12:57 PM: - We have that specific problem in production here and the patch works as a workaround. It's been more than a year since the patch was suggested, may I ask when that could be integrated in a build? I will try to setup my local computer to test the workaround and create a PR if it does. was (Author: laforet): We have that specific problem in production here and the patch works as a workaround. It's been more than a year since the patch was suggested, may I ask when that could be integrated in a build? > Log4j 2.0 with JBoss EAP 6.2 > - > > Key: LOG4J2-548 > URL: https://issues.apache.org/jira/browse/LOG4J2-548 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.0-rc1, 2.1 > Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler >Reporter: Shehata >Assignee: Ralph Goers >Priority: Major > Attachments: LOG4J2-548 - evictors.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message: > "ERROR StatusLogger Could not search jar file > 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core' > for classes matching criteria: annotated with @Plugin file not found" > after debugging the application found that the problem is located in : > org.apache.logging.log4j.core.config.plugins.ResolverUtil > method: findInPackage --> line number 247 > the protocol used in the jar is vfs not vfszip -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2
[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435497#comment-16435497 ] Martin edited comment on LOG4J2-548 at 4/12/18 12:54 PM: - We have that specific problem in production here and the patch works as a workaround. It's been more than a year since the patch was suggested, may I ask when that could be integrated in a build? was (Author: laforet): It's been more than a year since the patch was suggested. We have that specific problem in production here and the patch works as a workaround. May I ask when that could be integrated in a build? > Log4j 2.0 with JBoss EAP 6.2 > - > > Key: LOG4J2-548 > URL: https://issues.apache.org/jira/browse/LOG4J2-548 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.0-rc1, 2.1 > Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler >Reporter: Shehata >Assignee: Ralph Goers >Priority: Major > Attachments: LOG4J2-548 - evictors.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message: > "ERROR StatusLogger Could not search jar file > 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core' > for classes matching criteria: annotated with @Plugin file not found" > after debugging the application found that the problem is located in : > org.apache.logging.log4j.core.config.plugins.ResolverUtil > method: findInPackage --> line number 247 > the protocol used in the jar is vfs not vfszip -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2
[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435497#comment-16435497 ] Martin edited comment on LOG4J2-548 at 4/12/18 12:53 PM: - It's been more than a year since the patch was suggested. We have that specific problem in production here and the patch works as a workaround. May I ask when that could be integrated in a build? was (Author: laforet): It's been more than a year since the patch was suggested. We have that specific problem in production here and the patch works as a workaround. Any idea when that could be integrated in a build? > Log4j 2.0 with JBoss EAP 6.2 > - > > Key: LOG4J2-548 > URL: https://issues.apache.org/jira/browse/LOG4J2-548 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.0-rc1, 2.1 > Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler >Reporter: Shehata >Assignee: Ralph Goers >Priority: Major > Attachments: LOG4J2-548 - evictors.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message: > "ERROR StatusLogger Could not search jar file > 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core' > for classes matching criteria: annotated with @Plugin file not found" > after debugging the application found that the problem is located in : > org.apache.logging.log4j.core.config.plugins.ResolverUtil > method: findInPackage --> line number 247 > the protocol used in the jar is vfs not vfszip -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2
[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435497#comment-16435497 ] Martin commented on LOG4J2-548: --- It's been more than a year since the patch was suggested. We have that specific problem in production here and the patch works as a workaround. Any idea when that could be integrated in a build? > Log4j 2.0 with JBoss EAP 6.2 > - > > Key: LOG4J2-548 > URL: https://issues.apache.org/jira/browse/LOG4J2-548 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.0-rc1, 2.1 > Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler >Reporter: Shehata >Assignee: Ralph Goers >Priority: Major > Attachments: LOG4J2-548 - evictors.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message: > "ERROR StatusLogger Could not search jar file > 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core' > for classes matching criteria: annotated with @Plugin file not found" > after debugging the application found that the problem is located in : > org.apache.logging.log4j.core.config.plugins.ResolverUtil > method: findInPackage --> line number 247 > the protocol used in the jar is vfs not vfszip -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[ https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner resolved LOG4NET-592. - Resolution: Works for Me Resolving as works for me. Please close the issue when you had the chance to review or reopen the issue otherwise. > log4net 2.0.8 does not support .netcore 2.1 > --- > > Key: LOG4NET-592 > URL: https://issues.apache.org/jira/browse/LOG4NET-592 > Project: Log4net > Issue Type: New Feature > Environment: Windows 7 > VSCode > .netcore 2.1 > .NET Command Line Tools (2.1.300-preview1-008174) >Reporter: Sathish >Assignee: Dominik Psenner >Priority: Major > Attachments: netcore-2.1.tar > > > log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final) > > Error while installing log4net 2.0.8 package: > error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for > '.NETCoreApp,Version=v2.1'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[
https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435336#comment-16435336
]
Dominik Psenner edited comment on LOG4NET-592 at 4/12/18 10:47 AM:
---
I just uploaded a sample project that targets netcoreapp2.1 and it works for
me. Here's what the project consists of in plaintext:
Program.cs:
{code}
using System;
using log4net;
using log4net.Config;
using log4net.Core;
namespace ConsoleApp
{
class Program
{
static void Main(string[] args)
{
var repository = LogManager.CreateRepository("root");
BasicConfigurator.Configure(repository);
var logger = repository.GetLogger(typeof(Program).Name);
Console.WriteLine("Hello World!");
logger.Log(new LoggingEvent(new LoggingEventData()
{
Level = Level.Info,
Message = "Hello World!",
}));
Console.WriteLine("Press [Enter] to terminate ..");
Console.ReadLine();
}
}
}
{code}
ConsoleApp.csproj:
{code:xml}
Exe
netcoreapp2.1
{code}
May I close this issue?
was (Author: nachbarslumpi):
I just uploaded a sample project that targets netcoreapp2.1 and it works for
me. Here's what the project consists of in plaintext:
Program.cs:
{code}
using System;
using log4net;
using log4net.Config;
using log4net.Core;
namespace ConsoleApp
{
class Program
{
static void Main(string[] args)
{
var repository = LogManager.CreateRepository("root");
BasicConfigurator.Configure(repository);
var logger = repository.GetLogger(typeof(Program).Name);
Console.WriteLine("Hello World!");
logger.Log(new LoggingEvent(new LoggingEventData()
{
Level = Level.Info,
Message = "Hello World!",
}));
Console.WriteLine("Press [Enter] to terminate ..");
Console.ReadLine();
}
}
}
{code}
ConsoleApp.csproj:
{code:xml}
Exe
netcoreapp2.1
{code}
May I close this issue?
> log4net 2.0.8 does not support .netcore 2.1
> ---
>
> Key: LOG4NET-592
> URL: https://issues.apache.org/jira/browse/LOG4NET-592
> Project: Log4net
> Issue Type: New Feature
> Environment: Windows 7
> VSCode
> .netcore 2.1
> .NET Command Line Tools (2.1.300-preview1-008174)
>Reporter: Sathish
>Priority: Major
> Attachments: netcore-2.1.tar
>
>
> log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final)
>
> Error while installing log4net 2.0.8 package:
> error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for
> '.NETCoreApp,Version=v2.1'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[ https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner reassigned LOG4NET-592: --- Assignee: Dominik Psenner > log4net 2.0.8 does not support .netcore 2.1 > --- > > Key: LOG4NET-592 > URL: https://issues.apache.org/jira/browse/LOG4NET-592 > Project: Log4net > Issue Type: New Feature > Environment: Windows 7 > VSCode > .netcore 2.1 > .NET Command Line Tools (2.1.300-preview1-008174) >Reporter: Sathish >Assignee: Dominik Psenner >Priority: Major > Attachments: netcore-2.1.tar > > > log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final) > > Error while installing log4net 2.0.8 package: > error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for > '.NETCoreApp,Version=v2.1'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[
https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435336#comment-16435336
]
Dominik Psenner commented on LOG4NET-592:
-
I just uploaded a sample project that targets netcoreapp2.1 and it works for
me. Here's what the project consists of in plaintext:
Program.cs:
{code}
using System;
using log4net;
using log4net.Config;
using log4net.Core;
namespace ConsoleApp
{
class Program
{
static void Main(string[] args)
{
var repository = LogManager.CreateRepository("root");
BasicConfigurator.Configure(repository);
var logger = repository.GetLogger(typeof(Program).Name);
Console.WriteLine("Hello World!");
logger.Log(new LoggingEvent(new LoggingEventData()
{
Level = Level.Info,
Message = "Hello World!",
}));
Console.WriteLine("Press [Enter] to terminate ..");
Console.ReadLine();
}
}
}
{code}
ConsoleApp.csproj:
{code:xml}
Exe
netcoreapp2.1
{code}
May I close this issue?
> log4net 2.0.8 does not support .netcore 2.1
> ---
>
> Key: LOG4NET-592
> URL: https://issues.apache.org/jira/browse/LOG4NET-592
> Project: Log4net
> Issue Type: New Feature
> Environment: Windows 7
> VSCode
> .netcore 2.1
> .NET Command Line Tools (2.1.300-preview1-008174)
>Reporter: Sathish
>Priority: Major
> Attachments: netcore-2.1.tar
>
>
> log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final)
>
> Error while installing log4net 2.0.8 package:
> error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for
> '.NETCoreApp,Version=v2.1'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[ https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner updated LOG4NET-592: Attachment: (was: netcore-2.1.tar) > log4net 2.0.8 does not support .netcore 2.1 > --- > > Key: LOG4NET-592 > URL: https://issues.apache.org/jira/browse/LOG4NET-592 > Project: Log4net > Issue Type: New Feature > Environment: Windows 7 > VSCode > .netcore 2.1 > .NET Command Line Tools (2.1.300-preview1-008174) >Reporter: Sathish >Priority: Major > Attachments: netcore-2.1.tar > > > log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final) > > Error while installing log4net 2.0.8 package: > error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for > '.NETCoreApp,Version=v2.1'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[ https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner updated LOG4NET-592: Attachment: netcore-2.1.tar > log4net 2.0.8 does not support .netcore 2.1 > --- > > Key: LOG4NET-592 > URL: https://issues.apache.org/jira/browse/LOG4NET-592 > Project: Log4net > Issue Type: New Feature > Environment: Windows 7 > VSCode > .netcore 2.1 > .NET Command Line Tools (2.1.300-preview1-008174) >Reporter: Sathish >Priority: Major > Attachments: netcore-2.1.tar > > > log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final) > > Error while installing log4net 2.0.8 package: > error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for > '.NETCoreApp,Version=v2.1'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[ https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner updated LOG4NET-592: Attachment: netcore-2.1.tar > log4net 2.0.8 does not support .netcore 2.1 > --- > > Key: LOG4NET-592 > URL: https://issues.apache.org/jira/browse/LOG4NET-592 > Project: Log4net > Issue Type: New Feature > Environment: Windows 7 > VSCode > .netcore 2.1 > .NET Command Line Tools (2.1.300-preview1-008174) >Reporter: Sathish >Priority: Major > Attachments: netcore-2.1.tar > > > log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final) > > Error while installing log4net 2.0.8 package: > error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for > '.NETCoreApp,Version=v2.1'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-2129) Log4j2 throws NoClassDefFoundError in Java 9
[
https://issues.apache.org/jira/browse/LOG4J2-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435160#comment-16435160
]
Björn Kautler commented on LOG4J2-2129:
---
Well, if you have to use that evil plugin [~Johnston], then at least configure
it correctly.
Your problem has nothing to do with this bug, but that you leave out necessary
files.
It is surely significant, that the plugins documentation even uses {{log4j}} as
example for preventing the minimizing:
[https://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html]
last example
> Log4j2 throws NoClassDefFoundError in Java 9
>
>
> Key: LOG4J2-2129
> URL: https://issues.apache.org/jira/browse/LOG4J2-2129
> Project: Log4j 2
> Issue Type: Bug
> Components: API
>Affects Versions: 2.10.0, 2.11.0
> Environment: Java 9
>Reporter: Blazej
>Priority: Major
> Fix For: 2.11.0
>
> Attachments: log4j-api-patch.jar
>
>
> When I execute a sample project
> (https://github.com/bbucko/log4j2-jpms-sample) in Java 9 a following
> exception is thrown:
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError: Could not
> initialize class org.apache.logging.log4j.util.PropertiesUtil
> at
> org.apache.logging.log4j/org.apache.logging.log4j.status.StatusLogger.(StatusLogger.java:71)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.LogManager.(LogManager.java:60)
> {code}
> Exception is a little bit misleading because it seems that true root cause
> can be found here:
> {code}
> java.util.ServiceConfigurationError:
> org.apache.logging.log4j.util.PropertySource: module org.apache.logging.log4j
> does not declare `uses`
> at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588)
> at java.base/java.util.ServiceLoader.checkCaller(ServiceLoader.java:574)
> at java.base/java.util.ServiceLoader.(ServiceLoader.java:503)
> at java.base/java.util.ServiceLoader.load(ServiceLoader.java:1684)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil$Environment.(PropertiesUtil.java:319)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil$Environment.(PropertiesUtil.java:310)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil.(PropertiesUtil.java:69)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil.(PropertiesUtil.java:49)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.util.Constants.(Constants.java:30)
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:375)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.spi.AbstractLogger.createClassForProperty(AbstractLogger.java:198)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.spi.AbstractLogger.(AbstractLogger.java:88)
> at
> org.apache.logging.log4j/org.apache.logging.log4j.LogManager.(LogManager.java:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[ https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435106#comment-16435106 ] Dominik Psenner edited comment on LOG4NET-592 at 4/12/18 7:49 AM: -- log4net targets netstandard-1.6 and I wonder why it cannot be used in a netcoreapp 2.1? Does a library have to explicitly add support for each future netcoreapp release? was (Author: nachbarslumpi): log4net targets netstandard-1.6 and I wonder why it cannot be used in a netcoreapp 2.1? Does a library have to explicitly add support each future netcoreapp release? > log4net 2.0.8 does not support .netcore 2.1 > --- > > Key: LOG4NET-592 > URL: https://issues.apache.org/jira/browse/LOG4NET-592 > Project: Log4net > Issue Type: New Feature > Environment: Windows 7 > VSCode > .netcore 2.1 > .NET Command Line Tools (2.1.300-preview1-008174) >Reporter: Sathish >Priority: Major > > log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final) > > Error while installing log4net 2.0.8 package: > error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for > '.NETCoreApp,Version=v2.1'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[ https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435106#comment-16435106 ] Dominik Psenner commented on LOG4NET-592: - log4net targets netstandard-1.6 and I wonder why it cannot be used in a netcoreapp 2.1? Does a library have to explicitly add support each future netcoreapp release? > log4net 2.0.8 does not support .netcore 2.1 > --- > > Key: LOG4NET-592 > URL: https://issues.apache.org/jira/browse/LOG4NET-592 > Project: Log4net > Issue Type: New Feature > Environment: Windows 7 > VSCode > .netcore 2.1 > .NET Command Line Tools (2.1.300-preview1-008174) >Reporter: Sathish >Priority: Major > > log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final) > > Error while installing log4net 2.0.8 package: > error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for > '.NETCoreApp,Version=v2.1'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (LOG4NET-592) log4net 2.0.8 does not support .netcore 2.1
[ https://issues.apache.org/jira/browse/LOG4NET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner updated LOG4NET-592: Issue Type: New Feature (was: Bug) > log4net 2.0.8 does not support .netcore 2.1 > --- > > Key: LOG4NET-592 > URL: https://issues.apache.org/jira/browse/LOG4NET-592 > Project: Log4net > Issue Type: New Feature > Environment: Windows 7 > VSCode > .netcore 2.1 > .NET Command Line Tools (2.1.300-preview1-008174) >Reporter: Sathish >Priority: Major > > log4net package doesn't support .netcore2.1 ( 2.1.0-preview1-final) > > Error while installing log4net 2.0.8 package: > error NU1100: Unable to resolve 'log4net (>= 2.0.8)' for > '.NETCoreApp,Version=v2.1'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender
[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435008#comment-16435008 ] Remko Popma commented on LOG4J2-2301: - Hi Carter, sorry I have not been able to spend as much time as I would like on Log4j (been trying to get GROOVY-8520 done before the groovy 2.5 release). I really appreciate the work you've been doing recently and I will try to take a look at PR #164 soon. > gc-free mixed async loging loses parameter values after the first appender > -- > > Key: LOG4J2-2301 > URL: https://issues.apache.org/jira/browse/LOG4J2-2301 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.11.0 >Reporter: Carter Kozak >Assignee: Carter Kozak >Priority: Major > > When gc-free logging is used with mixed synchronous/asynchronous loggers, > parameter values are replaced with "null" after the first AsyncLoggerConfig. > The message format is still present, as well as the parameter count, however > all values are nulls. > It appears that Log4jEventWrapperHandler.onEvent invokes > MutableLogEvent.clear, which nulls out the parameter array. > I have constructed a failing test (which I need to clean up and deduplicate > some code from the fix for LOG4J2-2299): > https://github.com/cakofony/logging-log4j2/commit/b9c03f5c6881bfe778f8e2d75d046ce6e021c4f1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
