On Wed, Mar 13, 2024 at 11:07 PM Grzegorz Grzybek
wrote:
> I hope this helps.
>
> regards
> Grzegorz Grzybek
>
> It looks helpful, I'll take a stab at it next week and follow up. Thank
you.
Regards,
Will Hartung
might have to refactor it. The
fragment that is exporting the internal backend classes as Grzegorz mentioned
might help you in some cases, but this means that your classes can access the
log4j classes, but log4j cannot access your classes (which means that if your
code contains an appender
Hello
So, for this fragment, do I simply need to make a fragment containing the
> extra log4j information, or do I need to extract the code that is using
> those log4j pieces and put that into a fragment. That seems to be a much
> taller order. Compared to bolting the necessary log4j.cor
independently, and making
them bundles individually. One of the bundles has a Log4j appender class of
its own, this is in contrast to the example you posted which seems to be a
specific pax appender.
There's also some other code. It looks like this:
@Override
public IELogLevel toIELogLev
j2 bundle.
>>
> Hi, thanks for getting back.
>
> Yes, it seems that the code is doing a couple of things. One is creating its
> own appender, and another it seems to be looking at different kinds of events
> that contain raw logging information, so it's using some of the classe
it's using some of the
classes to extract information from those.
So, for this fragment, do I simply need to make a fragment containing the
extra log4j information, or do I need to extract the code that is using
those log4j pieces and put that into a fragment. That seems to be a much
taller
ing to get our legacy application running in an OSGI runtime,
> and have been trying with Karaf.
>
> After much pushing modules around, I was getting this error about Log4j:
>
> Error executing command: Error executing command on bundles:
> Error starting bundle 138: Unable to resol
I've been trying to get our legacy application running in an OSGI runtime,
and have been trying with Karaf.
After much pushing modules around, I was getting this error about Log4j:
Error executing command: Error executing command on bundles:
Error starting bundle 138: Unable to resolve caterwaul
Correct - by hotfix I mean updating the log4j version without upgrading to
karaf 4.3.4. Restarting Karaf is not an issue.
Thanks for the hint regarding bundle:update.
I prefer removing the vulnerable log4j from the classpath (which this
procedure achieves)
Am Mo., 13. Dez. 2021 um 14:02 Uhr
If you want to upgrade, you have to change in etc/startup.properties
(and populate system repo).
Regards
JB
On 13/12/2021 13:42, Raggy Fab wrote:
> Hello,
>
> I am aware that the new karaf version 4.3.4 will fix the Log4j
> Vulnerabili
to upgrade, you have to change in etc/startup.properties
> (and populate system repo).
>
> Regards
> JB
>
> On 13/12/2021 13:42, Raggy Fab wrote:
> > Hello,
> >
> > I am aware that the new karaf version 4.3.4 will fix the Log4j
> > Vulnerabilit
am aware that the new karaf version 4.3.4 will fix the Log4j
Vulnerability (CVE-2021-44228).
However, I can't upgrade karaf in my project. Is there a hotfix option?
(Ideally only touching log4j)
I tried to swap out Pax Logging:
bundle:install mvn:org.ops4j.pax.logging/pax-logging-log4j2/2.0.11
Hello,
I am aware that the new karaf version 4.3.4 will fix the Log4j
Vulnerability (CVE-2021-44228).
However, I can't upgrade karaf in my project. Is there a hotfix option?
(Ideally only touching log4j)
I tried to swap out Pax Logging:
bundle:install mvn:org.ops4j.pax.logging/pax-logging
Hi Paul
Only log4j 2.x is only impacted, Karaf 3.0/pax logging 1.8 uses log4j 1.x so no
problem.
Regards
JB
> Le 12 déc. 2021 à 19:18, Paul Spencer a écrit :
>
> For users of Karaf 3.0.x that uses Pax Logging version 1.8.x, what is the
> recommended mitigation for "Ap
For users of Karaf 3.0.x that uses Pax Logging version 1.8.x, what is the
recommended mitigation for "Apache Log4j Remote Code Execution Vulnerability",
CVE-2021-44228?
Paul Spencer
I already replied to Oleg:
log4j2.formatMsgNoLookups=true
In system.properties
Regards
JB
> Le 12 déc. 2021 à 19:05, Paul Spencer a écrit :
>
> For users of Karaf 4.2.x, what is the recommended mitigation for "Apache
> Log4j Remote Code Execution Vulnerability", CVE
For users of Karaf 4.2.x, what is the recommended mitigation for "Apache Log4j
Remote Code Execution Vulnerability", CVE-2021-44228?
Paul Spencer
mitigation for "Apache
Log4j Remote Code Execution Vulnerability", CVE-2021-44228?
Paul Spencer
écrit :
>>>
>>> For users of Karaf 4.3.x, what is the recommended mitigation for "Apache
>>> Log4j Remote Code Execution Vulnerability", CVE-2021-44228?
>>>
>>> Paul Spencer
>>>
>>
>
fix by default.
>
>> Le 12 déc. 2021 à 17:54, Paul Spencer a écrit :
>>
>> For users of Karaf 4.3.x, what is the recommended mitigation for "Apache
>> Log4j Remote Code Execution Vulnerability", CVE-2021-44228?
>>
>> Paul Spencer
>>
>
You can use system.properties to set the msg format on existing version.
Else Karaf 4.3.4 will include fix by default.
> Le 12 déc. 2021 à 17:54, Paul Spencer a écrit :
>
> For users of Karaf 4.3.x, what is the recommended mitigation for "Apache
> Log4j Remote Code Execut
For users of Karaf 4.3.x, what is the recommended mitigation for "Apache Log4j
Remote Code Execution Vulnerability", CVE-2021-44228?
Paul Spencer
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
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
.
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
on: Can't find bundle
> for base name Log4j-charsets, locale en_US
>org.ops4j.pax.logging.pax-logging-log4j2 [log4j2] ERROR : Unable to invoke
> factory method in class
> org.apache.logging.log4j.core.appender.ConsoleAppender for element Console:
> java.lang.IllegalS
for
element Console: java.util.MissingResourceException: Can't find bundle for base
name Log4j-charsets, locale en_US
org.ops4j.pax.logging.pax-logging-log4j2 [log4j2] ERROR : Unable to invoke
factory method in class org.apache.logging.log4j.core.appender.ConsoleAppender
for element Console
I am having an issue when using Log4j 1 (via pax-logging-service, version
1.10.1) with Karaf 4.1.2, where the logging color in the Karaf console (when
tailing the logs) is always white instead of the usual default colors of
purple for warn, red for error and blue for trace and info, etc.
I have
In your case you would have to make sure the pax logging bunde has access
to the jms api. So you would need to write a fragment for it.
An easier way is to use Apache Decanter with the jms appender. It is
already well prepared for OSGi.
See:
https://karaf.apache.org/manual/decanter/latest-1/#_jms
Hi Karaf User,
how can i configure a Log4j StringMatchFilter for the Karaf Decanter Log
Collector?
For manual built up appenders it works like this:
log4j.appender.FILE=org.apache.log4j.FileAppender
log4j.appender.FILE.File=info.log
Hi Guillaume,
Thanks for reply. Unfortunately this is exactly the bundle setup I've used so
far.
I am not happy with that because I have to maintain two log4j configurations,
therefore I am searching for a solution to integrate pax-logging somehow.
Regards
Von: Guillaume Nodet [mailto:gno
In such a case, one possibility would be to create an uber bundle
containing the library + an embedded version of log4j, without importing
the package. It will force that library to use the embedded version of
log4j which will be complete. So you won't run into ClassNotFoundException
Hi,
I have a non-OSGI 3rd party Jar which seems to use Log4j in a way that I cannot
connect it to Pax-Logging.
I followed the instructions in
https://ops4j1.jira.com/wiki/display/paxlogging/How+to+use+Pax+Logging+in+my+bundles
I created a wrapper bundle without the log4j Jar and made an import
gt;>>> and DEBUG). This causes no error.
>>>>>
>>>>> But after having installed feature pax-jetty (after step 10 in my
>>>>> previous post), every change in org.ops4j.pas.logging.cfg causes the same
>>>>> error to appear (the stack trace inc
>>>> It's as if installing the pax-jetty feature takes gives control of
>>>> org.ops4j.pas.logging.cfg to someone who cannot load the DLL. I have no
>>>> idea how this could happen.
>>>>
>>>> Anyone else has an idea?
>>>>
>&
he stack trace included in my previous post).
>>>
>>> It's as if installing the pax-jetty feature takes gives control of
>>> org.ops4j.pas.logging.cfg to someone who cannot load the DLL. I have no
>>> idea how this could happen.
>>>
>>> A
tty feature takes gives control of
>> org.ops4j.pas.logging.cfg to someone who cannot load the DLL. I have no
>> idea how this could happen.
>>
>> Anyone else has an idea?
>>
>> /Bengt
>>
>>
>>
>>
>>
>>
>>
>> /Beng
Bengt
>
> 2016-07-04 15:51 GMT+02:00 Bengt Rodehav <be...@rodehav.com>:
>
>> 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 g
/Bengt
2016-07-04 15:51 GMT+02:00 Bengt Rodehav <be...@rodehav.com>:
> 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 wou
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 so
conversation to the OOPS4J mailing list.
/Bengt
2016-07-01 8:55 GMT+02:00 Bengt Rodehav <be...@rodehav.com>:
> 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.
>
>
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
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 <be...@rodehav.com>:
> Thanks JB,
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
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
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
I'm trying to upgrade from Karaf 2..1 to 4.0.5 and I run into problems
regarding NTEventLogAppender. I get the following on startup:
2016-06-29 17:16:05,354 | ERROR | 4j.pax.logging]) | configadmin
| ?
? | [org.osgi.service.log.LogService,
org.knopflerfish.service.log.LogService,
Hi JB,
After adoption one of log4j2 GELF appenders I’ve share results with example
configuration. Installation process of custom appender in general already
properly documented in section «Custom appenders» of User Guide.
Configuration example for gelfj appender for current Karaf (log4j 1.x
egards,
Lukasz
—
Apache Karaf Committer & PMC
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org
Wiadomość napisana przez Владимир Коньков <vkon...@citc.ru
<mailto:vkon...@citc.ru>> w dniu 16 mar 2016, o godz. 11:32:
Hi
As of version 4.1 Karaf will
Hi Valdimir,
by feature, I meant "a simple way" to provide/add it (not necessary a
Karaf feature) ;)
Probably the easier way now is to document how to do it in the dev guide
with an associated sample.
Regards
JB
On 03/19/2016 03:03 PM, Владимир Коньков wrote:
Hi Jean-Baptiste!
We
Hi there!
Lukasz, Jean-Baptiste, thanx for reply. Actually your opinion is expected and
reasonable.
Lukasz, couple of comments:
Proposed solution is not specific for any tool - GELF is very common format for
app log streaming and it’s popularity is growing.
About custom distribution:
Hi Jean-Baptiste!
We actively use GELF for streaming logs from Karaf based platforms for years.
But we stop building custom distributions at beginning of adoption because of
we use use different distrs from different vendors (FuseSource, Talend, stock
Servicemix, plain Karaf etc). Not all
& PMC
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org
> Wiadomość napisana przez Владимир Коньков <vkon...@citc.ru> w dniu 16 mar
> 2016, o godz. 11:32:
>
> Hi
>
> As of version 4.1 Karaf will use Log4J 2 as logging backend (thanx,
Hi Vladimir
anyway, do you already have GELF in your custom distribution ?
If so, I would love to document it for other potential users, or even
propose an optional feature to add this.
WDYT ?
Regards
JB
On 03/17/2016 06:33 AM, Владимир Коньков wrote:
Hi there!
Lukasz, Jean-Baptiste,
Hi
As of version 4.1 Karaf will use Log4J 2 as logging backend (thanx, Guillaume).
It’s very good news, because it greatly simplify configuration of robust
production logging - compression, flexible rotation rules, async, fallback
logging. All this features comes out of the box with Log4J 2
I am trying to use JSONEventLayoutV1
<https://github.com/logstash/log4j-jsonevent-layout> as the pattern layout
for karaf logging.
The steps that I have followed.
1. Modified the pom.xml file of jsonevent-layout as shown below:-
org.apache.felix
maven-bundle-plugin
2.3.
What I'm suggesting is to decouple the logfile location, as done with
other kinds of locations such as:
${karaf.home}
${karaf.base}
${karaf.data}
${karaf.etc}
and introduce an additional ${karaf.log} ($KARAF_LOG)
Currently, ${karaf.data}/log (or $KARAF_DATA/log) occurs in several
places:
I was wondering about supporting configuring a specific location for the Karaf
log files.
There are use cases where these files must not be kept under the data
directory.
Could it be supported by use of a ${karaf.log} which defaults to
${karaf.data}/log ?
How about ${karaf.home}/log?
2015-03-11 11:00 GMT+01:00 Martin Lichtin lich...@yahoo.com:
I was wondering about supporting configuring a specific location for the
Karaf log files.
There are use cases where these files must not be kept under the data
directory.
Could it be supported by use
to append any log.
Details:
bundle:list or la
shows that the fragment host is resolved.
---
7 | Resolved | 7 | 1.0.0.SNAPSHOT | Flume NG Log4j Appender,
Hosts: 9
8 | Active | 8 | 1.7.2 | OPS4J Pax Logging - API
9 | Active | 8 | 1.7.2 | OPS4J
The good news,
Your setup is good as the list of bundles already shows the fragment bundle
to be attached to the right host bundle.
Does the appender require something special? Any certain classes from
log4j?
You could try to debug into the appender and try to see if it is actually
called
I tried remote debugging by putting karaf in debug + suspend mode and
connect from the other end running log4j flume appender code. The log4j
flume Appender class configured in org.ops4j.pax.logging.cfg as shown
below doesn't get called.
---
# Root logger
log4j.rootLogger = DEBUG
Hi,
I have been trying unsuccessfully to have a karaf distribution connect
to elastic search via flume using the FlumeLog4jAppender.
I followed the steps listed here
http://blog.nanthrax.net/2012/12/create-custom-log4j-appender-for-karaf-and-pax-logging/
for adding a custom appender
://karaf.922171.n3.nabble.com/Enabling-Flume-log4j-appender-logging-in-Karaf-tp4036033p4036035.html
Sent from the Karaf - User mailing list archive at Nabble.com.
We are seeing the following message when deploying a WAR bundle and starting
karaf 3.0.1:
admin@NextGate () log4j:WARN No appenders could be found for logger
(org.springframework.web.servlet.DispatcherServlet).
log4j:WARN Please initialize the log4j system properly.
I was told to remove log4j
message when deploying a WAR bundle and
starting
karaf 3.0.1:
admin@NextGate () log4j:WARN No appenders could be found for logger
(org.springframework.web.servlet.DispatcherServlet).
log4j:WARN Please initialize the log4j system properly.
I was told to remove log4j and use 'mvn
-log4j-related-tp4034739p4034742.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Achim, thx for reply! So I need to use Import-Package only instead of
Bundle-Classpath?
And if yes, which packages do I need to import specifically?
--
View this message in context:
http://karaf.922171.n3.nabble.com/No-appenders-could-be-found-for-logger-log4j-related-tp4034739p4034743.html
Ok so I removed the three JARs (one log4j and two slf4j) from the
Bundle-ClassPath section and added the following to the package-import
section:
Import-Package
...
,org.apache.log4j
,org.slf4j
...
/Import-Package
Now I am not seeing the WARN in the console during karaf startup, but I am
seeing
So I added back the following to the Bundle-ClassPath section:
,WEB-INF/lib/log4j-1.2.16.jar
and still getting this exception on karaf startup. I still have the import
for org.apache.log4j in the Import-Package section so not sure what else
to try at this point
Caused
, to install org.apache.log4j either as it's own
bundle or as a part of a dependency-bundle. I'm still pretty new to OSGI,
though, so I could be wrong.
--
View this message in context:
http://karaf.922171.n3.nabble.com/No-appenders-could-be-found-for-logger-log4j-related-tp4034739p4034748.html
First of all, if you want to have a working logging with Karaf, use the
logging provided by it.
Karaf uses Pax Logging which supports a wide range of logging frameworks.
So don't embed log4j in your bundles. It's not needed and just doesn't work
that way!
You also should check the way you do your
. The
correct answer is, I think, to install org.apache.log4j either as it's own
bundle or as a part of a dependency-bundle. I'm still pretty new to
OSGI, though, so I could be wrong.
--
View this message in context:
http://karaf.922171.n3.nabble.com/No-appenders-could-be-found-for-logger-log4j
Hi guys,
sorry I was out for a rugby game ;)
Pax Logging wraps log4j, it doesn't import the whole log4j api.
Some part of the log4j API is not included because all doesn't make
sense in OSGi.
It's the case for org.apache.log4j.LogManager: it's part of log4j but
it's not included in pax
In the web.xml:
listener
listener-classorg.springframework.web.util.Log4jConfigListener/listener-class
/listener
Should we be using a different listener?
--
View this message in context:
http://karaf.922171.n3.nabble.com/No-appenders-could-be-found-for-logger-log4j-related
wraps log4j, it doesn't import the whole log4j api.
Some part of the log4j API is not included because all doesn't make
sense in OSGi.
It's the case for org.apache.log4j.LogManager: it's part of log4j but
it's not included in pax-logging (api or service).
In the latest pax-logging release, I
/listener-class
/listener
Should we be using a different listener?
--
View this message in context:
http://karaf.922171.n3.nabble.com/No-appenders-could-be-found-for-logger-log4j-related-tp4034739p4034757.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Well,
Pax Logging does provide a couple of different APIs for logging:
log4j, slf4j commons-logging, etc..
So actually it's a service that hides a lot of details from you.
As it is using log4j as the underlying logging infrastructure you most
likely are tempted to use a lot of it,
though those
it with pax-loggin-api
and pax-loggin-serice
dependancy and indeed there are no
removeAllAppenders method in it.
2014-06-26 10:49 GMT+02:00 Achim Nierbeck [via Karaf]
ml-node+s922171n4033807...@n3.nabble.com:
Well,
Pax Logging does provide a couple of different APIs for logging:
log4j, slf4j
Yep, that's the only constraint,
practically for standard logging you usually shouldn't care much.
For example if you take only the slf4j API as your logging api, you don't
really care if it is log4j or logback that does the actuall logging for
you.
So basically Pax Logging tries to do the same
Hey !
I have a problem with karaf (packaged in fuse esb version 6.1.0) I am in a
camel / spring / maven / jboss fuse / karaf environnement
I have a bundle which use log4j like this :
[...]
import org.apache.log4j.*;
[...]
Logger classlogger = Logger.getLogger(LoggerWrapper
I have exclude log4j dependancy in my maven project and insert
org.ops4j.pax.logging reference.
dependency
groupIdorg.ops4j.pax.logging/groupId
artifactIdpax-logging-api/artifactId
version1.7.2/version
I have try to find a workaround with log4J, but nothing works, any idea ?
--
View this message in context:
http://karaf.922171.n3.nabble.com/NoClassDefFoundError-org-apache-log4j-Layout-tp4033773p4033778.html
Sent from the Karaf - User mailing list archive at Nabble.com.
So you are trying to build a custom Logger, is that right?
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Layout
at
com.ericsson.mediation.core.bean.CoreLogger.log(CoreLogger.java:90)[265:
MEDIATION-SI800-Core:1.0.0]
If so you'll need to add this Logger by adding
Hi,
Pax Logging provides log4j 1.2.15.
I bet that you use log4j 1.2.17.
So, your project should use the 1.2.15 log4j dependency and Import-Package.
Regards
JB
On 06/25/2014 02:12 PM, loky wrote:
I have exclude log4j dependancy in my maven project and insert
org.ops4j.pax.logging reference
http://karaf.apache.org/manual/latest/users-guide/log.html
latest section: Custom appenders.
Regards
JB
On 06/25/2014 03:57 PM, Achim Nierbeck wrote:
So you are trying to build a custom Logger, is that right?
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Layout
Thanks jbonofre and Achim for helping me :)
jbonofre wrote
latest section: Custom appenders.
jbonofre Pax Logging provides log4j 1.2.15.
Indeed ! I have plugged it with the 1.2.15 but I still have the problem.
I have checked the latest section of
http://karaf.apache.org/manual/latest
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
jean-philippe.clem
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
Dear Karaf Team,
I would like to know if Karaf (v3) supports Log4J v2?
Cheers,
JP
[@@ OPEN @@]
:* 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
, Mar 21, 2013 at 11:47 PM, Jean-Baptiste Onofré j...@nanthrax.net
wrote:
Hi,
you can take a look on that:
http://blog.nanthrax.net/2012/12/create-custom-log4j-appender-for-karaf-and-pax-logging/
it may help.
Regards
JB
On 03/21/2013 10:43 AM, a_bouchama wrote:
Hello,
We want
Hi,
you can take a look on that:
http://blog.nanthrax.net/2012/12/create-custom-log4j-appender-for-karaf-and-pax-logging/
it may help.
Regards
JB
On 03/21/2013 10:43 AM, a_bouchama wrote:
Hello,
We want to monitor all logging messages of karaf, and push it to nagios (via
an SNMP).
Do you
to do, but log4j as slf4j and a
couple more logging framworks are supported by Karaf.
I am migrating some code to karaf.It turns out Pax Logging doesn't
allow
to access all log4j classes.
I removed code that is trying to access Appender. Problem solved.
--
View this message
Is it possible to use log4j in karaf ?
I have log4j classes in my bundle but I cant access them:
try {
Class? aClass = Class.forName(org.apache.log4j.Appender);
} catch (ClassNotFoundException e) {
throw new RuntimeException(e
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
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
at TRACE level.
Thanks for your help Guillaume. I know understand better how log4j filters
work. I think I will probably create my own filter that tries to match a
given MDC key to a certain value. This I think could be of value to others
as well.
/Bengt
2012/1/30 Guillaume Nodet gno...@gmail.com
are not preserved? I think that native log4j only supports filters when
using XML configuration and I assume that the Karaf filtering support has
been added on top of log4j (or is it in Pax-logging)? Has the ordering of
filters been taken into account?
I've been testing this on Karaf 2.2.0 with Pax
The filter support has been added in pax-logging.
Have a look at
https://github.com/ops4j/org.ops4j.pax.logging/blob/master/pax-logging-service/src/main/java/org/apache/log4j/PaxLoggingConfigurator.java
You may very well be right that the order isn't kept, which would
definitely be a bug
1 - 100 of 114 matches
Mail list logo
