[
https://issues.apache.org/jira/browse/SLING-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888121#comment-15888121
]
Konrad Windszus edited comment on SLING-6482 at 2/28/17 2:39 PM:
-----------------------------------------------------------------
The log file being empty must be treated as valid as the Apache Sling OSGi
Logging Logger Configuration states for {{org.apache.sling.commons.log.file}}:
bq. The name and path of the log file. If this is empty, logging goes to
standard output (the console). If this path is relative it is resolved below
${sling.home}. (org.apache.sling.commons.log.file)
was (Author: kwin):
The log file being empty must be treated as valid as the Apache Sling OSGi
Logging Logger Configuration states
bq. The name and path of the log file. If this is empty, logging goes to
standard output (the console). If this path is relative it is resolved below
${sling.home}. (org.apache.sling.commons.log.file)
> Commons Log WebConsole: Exception when creating logger without log file
> -----------------------------------------------------------------------
>
> Key: SLING-6482
> URL: https://issues.apache.org/jira/browse/SLING-6482
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Log 5.0.0
> Reporter: Bjoern Weide
> Priority: Minor
> Fix For: Commons Log 5.0.2
>
>
> When creating a new logger via WebConsole specifying an empty logfile it
> causes an StringIndexOutOfBoundsException when (re-)opening the WebConsole.
> {noformat}
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1931)
> at
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.getPath(SlingLogPanel.java:791)
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
