You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/03/12 07:56:50 UTC

[jira] Assigned: (SLING-321) Log stops working after reconfiguration

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

Felix Meschberger reassigned SLING-321:
---------------------------------------

    Assignee: Felix Meschberger

> Log stops working after reconfiguration
> ---------------------------------------
>
>                 Key: SLING-321
>                 URL: https://issues.apache.org/jira/browse/SLING-321
>             Project: Sling
>          Issue Type: Bug
>          Components: Core
>            Reporter: Bertrand Delacretaz
>            Assignee: Felix Meschberger
>         Attachments: SLING-log.patch
>
>
> The log stops working after starting the launchpad, going to http://localhost:8888/sling/configMgr and save the LogbackManager configuration.
> This is due to a ClassCastException in LogbackManager.updated(), as the org.apache.sling.osgi.log.file.number parameter is an Integer.
> I'll attach a workaround patch, which is probably not the right way of fixing this.

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