You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2008/03/11 15:16:46 UTC
[jira] Created: (SLING-321) Log stops working after reconfiguration
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
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.
[jira] Updated: (SLING-321) Log stops working after reconfiguration
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated SLING-321:
--------------------------------------
Attachment: SLING-log.patch
> 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
> 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.
[jira] Assigned: (SLING-321) Log stops working after
reconfiguration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (SLING-321) Log stops working after
reconfiguration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-321.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks for supplying the patch. I applied it and also fixed the property uses now correclty assuming the properties are strings.
Fixed in Rev. 636226.
Please close if this fixes your issue. Thanks.
> 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
> Fix For: 2.0.0
>
> 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.