AW: [riena-dev] Riena Logging

["Liebig, Stefan" <Stefan.Liebig@xxxxxxxxxxxx>]

Hi Ekke,

 

While logging is getting configured (extensions,services) components performing the configuration (service injector, extension injector,..)
may also log. These logging events can not be handled by the logging because it is getting configured. This situation is detected and the
log events get deferred and will be logged after the initialization is done.

In such a case the log event was also logged to console. I have removed that.

 

Stefan

 

 

Von: riena-dev-bounces@xxxxxxxxxxx [mailto:riena-dev-bounces@xxxxxxxxxxx] Im Auftrag von ekkehard
Gesendet: Dienstag, 11. November 2008 15:54
An: Riena Developers list
Betreff: Re: [riena-dev] Riena Logging

 

Liebig, Stefan schrieb:

Hi Ekke,

 

Ok, I got it. It is a while ago when I did this.

When we get log events and the logging is not yet fully initialized the events get buffered until the logging is ready.

what do you mean by 'fully initialized' ?

 

 

those three DEBUG log statements are printed to console for all 410 services

Those buffered events will also be written to the console with a ConsoleLogger (System.out/err).

Maybe this step is not really necessary. I guess you would like to have a clean console.

yes ;-)

ekke

 

Stefan

 

 

Von: riena-dev-bounces@xxxxxxxxxxx [mailto:riena-dev-bounces@xxxxxxxxxxx] Im Auftrag von ekkehard
Gesendet: Dienstag, 11. November 2008 10:24
An: Riena Developers list
Betreff: Re: [riena-dev] Riena Logging

 

hi stefan,

I'll debug this later.... (not today)

but did another test:

before I haven't used system property "riena.defaultlogging"
so I tried to run with set to false:
same happens as before

then I set it to true,
now there is a difference:

these outputs only appear if defaultlogging is set to true:

Tue Nov 11 10:13:45 CET 2008 WARNING [DeferredLoggingForwarder] org.eclipse.riena.internal.core.Activator Defered log event occured on Tue Nov 11 10:13:45 CET 2008 (1226394825556 ms) in thread [Start Level Event Dispatcher]:
LogLevel: 2,
Message: Forced <<lazy>> start(): 'org.eclipse.riena.communication.factory.hessian' failed but may succeed (bundle state is in transition):
        State change in progress for bundle "initial@reference:file:../../riena/plugins/org.eclipse.riena.communication.factory.hessian_1.0.0.M5.jar/" by thread "Start Level Event Dispatcher
......
Tue Nov 11 10:13:45 CET 2008 INFO [Start Level Event Dispatcher] org.eclipse.riena.communication.core.ssl.SSLConfiguration Configuring SSL protocol 'null' with keystore 'null'.
Tue Nov 11 10:13:45 CET 2008 INFO [Start Level Event Dispatcher] org.eclipse.riena.communication.core.ssl.SSLConfiguration No configuration given!.
...
and more

but the other output written for each Service registered with Riena remote properties happens always:

DEBUG - 10:18:54 [B: org.eclipse.riena.core] - published web service. protocol=hessian, url= ""> DEBUG - 10:18:54 [B: org.eclipse.riena.core] - web service count: 80.
DEBUG - 10:18:54 [B: org.eclipse.riena.core] - service endpoints count: 80.

the log output is formatted differently, so perhaps you have an idea why the first (Tue Nov 11.......) are not printed with riena.defaultlogging=false
but the other (DEBUG - 10:18:54....) are printed

ciao

ekke

Liebig, Stefan schrieb:

Hi Ekke,

 

To be honest I have no idea why this happens. Not yet!

If there are no extensions defining log listeners nothing should be logged.

Except when the system property "riena.defaultlogging" has been set to true.

Than as a default a log listener logging to the console will be created.

 

Could please set a breakpoint at

LoggerMill.bind(ExtendedLogReaderService logReaderService)

and check what happens there?

 

Thanks,

Stefan