[EMAIL PROTECTED] wrote:
>
> Could the static Log class support a spare logging mechanism (System.err?)
> after shutdown of the primary logging service. When shutting down all
> services, some objects (at least the IDBroker thread) will stop themselves
> asynchronously after the shutdown method has been called and may try to log
> a shutdown message causing unnecessary exceptions to be thrown.
Please take a look at TurbineLoggingService.java, lines #124-134 and
#321.
During initialization a bootstrap logger is created and appointed to be
default
logger for the system. In case of Turbine it is a ServletLogger. Then
internalInit()
method instantiates 'real' loggers defined by ResourceService.
When the system shuts down, the bootstrap logger is set back to be the
default.
As I understand, this scheme was now working for you, because you
application works
outside the servlet container. The solution as I see right now would be
deriving
a class from TurbineLoggingService and overriding init(ServletConfig)
method, to
instantiate a bootstrap logger of proper type.
On the other hand, if you use the TurbineConfig class for initializing
services,
its log(...) methods write to System.out, so ServletLogger should work
well in
this regard.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
