karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Pieber (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KARAF-1064) BootstrapLogManager does not reuse the instantiated Handler
Date Wed, 30 Nov 2011 08:01:41 GMT

     [ https://issues.apache.org/jira/browse/KARAF-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andreas Pieber updated KARAF-1064:

    Affects Version/s:     (was: cave-3.0.0)
        Fix Version/s:     (was: cave-3.0.0)
> BootstrapLogManager does not reuse the instantiated Handler
> -----------------------------------------------------------
>                 Key: KARAF-1064
>                 URL: https://issues.apache.org/jira/browse/KARAF-1064
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Álvaro Alda
>             Fix For: 2.2.5, 2.2.6, 3.0.0
>         Attachments: patchfile.txt
> When running Karaf in Master/Slave mode, the method getDefaultHandler() in class org.apache.karaf.main.BootstrapLogManager
is being invoked twice, one time in org.apache.karaf.main.Main and another one in the lock
file class (SimpleFileLock or DefaultJDBCLock), but the object instance of the Handler class
is created without closing the previous one. 
> I have created a patch which completes the singleton pattern, returning the previous
handler if the instance is not null. The patch has been created against the trunk, but you
can apply it to branch karaf-2.2.x.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message