Thanks Keith,
as far as I see OrientDB only overwrites the
java.util.logging.ConsoleHandler. All other handlers can just be set in the
logging.properties file. No need to hardwire this in the code. On the other
hand setting the ConsoleLogger in the code would have no effect, because
again it would be removed and substituted by OrientDB.
Ciao
Gregor
On Wednesday, January 28, 2015 at 4:25:17 AM UTC+1, Keith Freeman wrote:
>
> Note too that you can completely replace orient's logging. We use code
> like this with some our orientdb java client apps to completely suppress
> orient's console logs:
>
> final java.util.logging.Logger ologger =
> java.util.logging.Logger.getLogger("");
> java.util.logging.Handler[] handlers = ologger.getHandlers();
> for (int i = 0; i < handlers.length; i++)
> ologger.removeHandler(handlers[i]);
> ologger.addHandler(new java.util.logging.StreamHandler());
>
>
> You could use similar code to replace formatting, etc.
>
> On Monday, January 26, 2015 at 9:21:38 AM UTC-7, Gregor Frey wrote:
>>
>> Hi,
>> actually I embed the OrientDB and have my own log-configuration file,
>> which is set with the system variable java.util.logging.config.file.
>> What happens is that as long as the OrientDB is not started, my Formatter
>> (actually the standard SimpleFormatter) is used, but as soon as the
>> dbserver is up, all logs on the console ignore my format. If I look into
>> the OLogManager I see that the OLogFormatter is set for each instance of
>> ConsoleLogger (line 65). That's why I said it is hard coded. At least my
>> log-configuration is overwritten. The orientdb-server-log.properties files
>> has no influence on this, because the system variable is set to my own
>> file.
>> Ciao
>> Gregor
>>
>>
>>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
