You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2013/11/13 06:28:17 UTC

[jira] [Commented] (KARAF-2572) Karaf does not start if there is no log appender named out

    [ https://issues.apache.org/jira/browse/KARAF-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820954#comment-13820954 ] 

Jean-Baptiste Onofré commented on KARAF-2572:
---------------------------------------------

Christian, it seems that your latest change breaks unit test on the main module:

Failed tests:   testGetLogManager(org.apache.karaf.main.util.BootstrapLogManagerTest): File should exist at target/log/karaf.log

Did you try to execute the utests on main ?

Anyway, I'm taking a look on that.

> Karaf does not start if there is no log appender named out
> ----------------------------------------------------------
>
>                 Key: KARAF-2572
>                 URL: https://issues.apache.org/jira/browse/KARAF-2572
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>            Reporter: Christian Schneider
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.0.0
>
>
> When using a org.ops4j.pax.logging.cfg that does not contain a File appender with name "out" karaf does not start with a message about could not aquire file lock.
> This message is confusing as the real problem was that the BootStrapLogManager failed to initialize.



--
This message was sent by Atlassian JIRA
(v6.1#6144)