felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Custine (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1180) Improve Karaf DefaultJDBCLock to use proper logging mechanism instead of System err prints.
Date Mon, 07 Sep 2009 07:06:58 GMT

    [ https://issues.apache.org/jira/browse/FELIX-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752027#action_12752027
] 

Chris Custine commented on FELIX-1180:
--------------------------------------

Added bootstrap logger using java.util.logging 
- Log file will be the default "out" file appender from log4j config 
- File location can be overridden by setting "karaf.bootstrap.log" in config.properties 
- There are probably better ways to do this, but this works reasonably well and gives a common
logging interface (juli) to work with.

> Improve Karaf DefaultJDBCLock to use proper logging mechanism instead of System err prints.
> -------------------------------------------------------------------------------------------
>
>                 Key: FELIX-1180
>                 URL: https://issues.apache.org/jira/browse/FELIX-1180
>             Project: Felix
>          Issue Type: Improvement
>          Components: Karaf
>            Reporter: Jamie goodyear
>            Assignee: Chris Custine
>             Fix For: karaf-1.0.0
>
>         Attachments: felix-1180.patch
>
>
> Currently DefaultJDBCLock is using System.err.println to log information and errors.
This class needs to be writing this information (along with full stack traces whenever an
exception is caught) to the servicemix.log file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message