Re: log4j warning at startup

t; -Original Message- > From: Jörg Jansen > Sent: Mittwoch, 17. Februar 2021 15:03 > To: user > Subject: RE: log4j warning at startup > > Hi JB, > > yes, I tried with the original downloaded (and unmodified!) assembly. > The strange thing is, that it seem

RE: log4j warning at startup

Hi JB, Just found a solution. Setting system property -Dsun.stdout.encoding=UTF-8 solved the issue. Regards, Joerg -Original Message- From: Jörg Jansen Sent: Mittwoch, 17. Februar 2021 15:03 To: user Subject: RE: log4j warning at startup Hi JB, yes, I tried with the original

RE: log4j warning at startup

. Regards, Joerg -Original Message- From: Jean-Baptiste Onofre Sent: Mittwoch, 17. Februar 2021 14:22 To: user Subject: Re: log4j warning at startup Hi Joerg, I didn’t see such ERROR message (ok, I’m not using Windows ;)). Are you using the default etc/org.ops4j.pax.logging.cfg ? Regards JB

Re: log4j warning at startup

Hi Joerg, I didn’t see such ERROR message (ok, I’m not using Windows ;)). Are you using the default etc/org.ops4j.pax.logging.cfg ? Regards JB > Le 17 févr. 2021 à 12:19, Jörg Jansen a > écrit : > > Hi everybody, > > when starting the karaf-container (4.3.0) on a windows server, I receive

Re: Log4j NTEventLogAppender in Karaf 4.0.5

OK - thanks for trying. /Bengt 2016-07-12 11:12 GMT+02:00 Achim Nierbeck : > Hi Bengt, > > sorry been very busy lately. I did give it a try but couldn't find a > reason why Log4j2 should be used or Pax Logging should be triggered to be > restarted. There isn't any

Re: Log4j NTEventLogAppender in Karaf 4.0.5

Hi Bengt, sorry been very busy lately. I did give it a try but couldn't find a reason why Log4j2 should be used or Pax Logging should be triggered to be restarted. There isn't any reason for the pax web bundles to do so ... :/ sorry didn't get any further on this .. regards, Achim 2016-07-11

Re: Log4j NTEventLogAppender in Karaf 4.0.5

Did you have a chance to look at this Achim? If there is a problem with the pax-jetty feature it would be nice to have it fixed in Karaf 4.0.6 which I understand is in the works. /Bengt 2016-07-07 9:13 GMT+02:00 Bengt Rodehav : > OK - thanks Achim, > > /Bengt > > 2016-07-06

Re: Log4j NTEventLogAppender in Karaf 4.0.5

OK - thanks Achim, /Bengt 2016-07-06 22:08 GMT+02:00 Achim Nierbeck : > Hi Bengt, > > I'll try to find out if one of the bundles in that feature depends on > log4j2 ... but I'm not aware of such a dependency. > > Your suspicion about dynamic loading of DLLs is correct

Re: Log4j NTEventLogAppender in Karaf 4.0.5

Hi Bengt, I'll try to find out if one of the bundles in that feature depends on log4j2 ... but I'm not aware of such a dependency. Your suspicion about dynamic loading of DLLs is correct in case of the location of the dll is inside of a bundle and does have dependencies to another dll. If it's a

Re: Log4j NTEventLogAppender in Karaf 4.0.5

Another theory: Looking at the stack trace this seems to be triggered by a configuration update. Could the problem be that Pax-logging is trying to load the DLL again and failing since it is already loaded? Perhaps the initial load works but subsequent configuration updates does not? I tried to

Re: Log4j NTEventLogAppender in Karaf 4.0.5

A theory: Could one of the bundles installed by feature pax-jetty be using log4j 2.x directly without using Pax-logging? If so, would it too try to read the log4j configuration file? I guess it would fail to load the DLL since it is probably not compatible with log4j 2.x. Could this happen? If

Re: Log4j NTEventLogAppender in Karaf 4.0.5

Turned out not to be so easy to switch version of Pax-logging. I edited startup.properties.I also had to change version of pax-url-aether to 2.3.0. However, it seems like org.apache.karaf.features.core bundle requires a version of pax-url-aehter that is at least 2.4. However, I still think that

Re: Log4j NTEventLogAppender in Karaf 4.0.5

OK - I guess I misunderstood this then. Looking in the POM's I now see that there are dependencies to both log4j 1.2.16 and log4j 2.x. I wonder then why the NTEventLogAppender can't be used in Karaf 4.0.5. For a while I thought it might be a java version problem. I now use Java 8 instead of Java

Re: Log4j NTEventLogAppender in Karaf 4.0.5

Hi Bengt, newer versions of Pax-Logging don't use log4j2 per default so this should still work ... the underlying impl is still log4j 1 unless someone changed it on a minor version update ... regards, Achim 2016-06-30 16:23 GMT+02:00 Bengt Rodehav : > Thanks JB, > > Tried

Re: Log4j NTEventLogAppender in Karaf 4.0.5

Thanks JB, Tried it though and no diffference. When investigating this it seems like newer versions of pax-logging uses log4j2. Unfortunately the NTEventLogAppender is incompatible with log4j2. I've found the project log4jna that seems to target this. Unfortunately I cannot find a released

Re: Log4j NTEventLogAppender in Karaf 4.0.5

In Karaf 4, the dll should go in lib/ext. Regards JB On 06/30/2016 02:16 PM, Bengt Rodehav wrote: I have a feeling that I need to put the NTEventLogAppender.amd4.dll in another directory in Karaf 4.0.5 then in Karaf 2.4.1. I have always put it in the directory %KARAF_HOME%/lib which works for

Re: Log4j NTEventLogAppender in Karaf 4.0.5

I have a feeling that I need to put the NTEventLogAppender.amd4.dll in another directory in Karaf 4.0.5 then in Karaf 2.4.1. I have always put it in the directory %KARAF_HOME%/lib which works for Karaf 2.4.1. Where should DLL's be put in Karaf 4.0.5? /Bengt 2016-06-29 17:37 GMT+02:00 Bengt

Re: Log4J v2

Hey, The question would rather be: Does pax-logging support log4jv2 and AFAIK the answer is no. The question would be: how difficult can it be to add log4j v2 support to pax-logging :-) Kind regards, Andreas On Thu, Jun 13, 2013 at 3:50 PM, CLEMENT Jean-Philippe

RE: Log4J v2

Thanks for the info. Is PAX logging part of Felix ? JP [@@ OPEN @@] De : Andreas Pieber [mailto:anpie...@gmail.com] Envoyé : jeudi 13 juin 2013 15:56 À : Apache Karaf Objet : Re: Log4J v2 Hey, The question would rather be: Does pax-logging support log4jv2 and AFAIK the answer

Re: Log4J v2

:* Andreas Pieber [mailto:anpie...@gmail.com] *Envoyé :* jeudi 13 juin 2013 15:56 *À :* Apache Karaf *Objet :* Re: Log4J v2 ** ** Hey, ** ** The question would rather be: ** ** Does pax-logging support log4jv2 and AFAIK the answer is no. The question would be: how

Re: log4j

That's really the best thing to do in karaf, as the log configuration is handled in an osgi way, so no code should try to directly configure the logging framework. On Fri, May 4, 2012 at 1:01 PM, maaruks maris.orbid...@gmail.com wrote: Achim Nierbeck wrote I'm not sure what you are trying

Re: log4j

I'm not sure what you are trying to do, but log4j as slf4j and a couple more logging framworks are supported by Karaf. We use Pax Logging for this, log4j is even the underlying implementation for logging. If you want to use your own appenders you need to take special care for this. Regards, Achim

Re: log4j

Custom appenders can be deployed by using fragments attached to the pax-logging-service bundle fwiw. On Thu, May 3, 2012 at 1:21 PM, Achim Nierbeck bcanh...@googlemail.comwrote: I'm not sure what you are trying to do, but log4j as slf4j and a couple more logging framworks are supported by