Traces on the screen (stdout) look like :
            10:03:55 [FelixStartLevel] DEBUG – manage client XXX
            10:03:56 [Blueprint Extender: 3] DEBUG – Initializing XXX
            10:03:56 [Blueprint Extender: 2] DEBUG – Allocating XXX

JP

[@@ OPEN @@]

De : Achim Nierbeck [mailto:[email protected]]
Envoyé : mardi 26 août 2014 10:02
À : [email protected]
Objet : RE: Early logs


If it's on the console it might well be a sysout? I'd try to check that.

Regards, achim

sent from mobile device
Am 26.08.2014 09:46 schrieb "CLEMENT Jean-Philippe" 
<[email protected]<mailto:[email protected]>>:
Karaf is started with the console (bin/karaf) but at startup some logs are 
displayed on the screen instead of being directed to the karaf.log file.

There is no tweak to the logging configuration file and the logger used is 
Log4J. Those logs come from a bundle which wraps a library coming from another 
team, so I'm not too sure what is happening.

I guess Karaf logging is ready before the first user bundle is started, correct?

Regards,
JP

[@@ OPEN @@]


-----Message d'origine-----
De : Jean-Baptiste Onofré [mailto:[email protected]<mailto:[email protected]>]
Envoyé : mardi 26 août 2014 08:55
À : [email protected]<mailto:[email protected]>
Objet : Re: Early logs

Hi JP,

don't you use bin/start to run Karaf ?

If so, stdout is redirect to data/karaf.out. Is it what you talk about ?

What's the logger you use in your bundle and did you tweak 
etc/org.ops4j.pax.logging.cfg ?

Regards
JB

On 08/26/2014 08:51 AM, CLEMENT Jean-Philippe wrote:
> Dear Karaf,
>
> I'm beginning to investigate on a logging issue. It seems early logs sent 
> (from our bundles) when Karaf starts are redirected to the stdout instead of 
> the log file.
>
> Is this behavior possible and, if so, how to fix it?
>
> JP
>
> [@@ OPEN @@]
>

--
Jean-Baptiste Onofré
[email protected]<mailto:[email protected]>
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to