[
https://issues.apache.org/jira/browse/SLING-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226229#comment-16226229
]
Chetan Mehrotra commented on SLING-6482:
----------------------------------------
Thanks [~kwin] for the details. Fixed this with
[commit|https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-commons-log.git;a=commitdiff;h=eb3a92d8eb454ff8091e24408d35802006ebba94].
Now an empty fileName is mapped to "console" appender. This works fine post
edits also.
[~kwin] Can you validate the behaviour once with trunk to check it addresses
your concerns.
> Commons Log WebConsole: Exception when creating logger with an empty 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.4
>
> Attachments: SLING-6482-v01.patch
>
>
> 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.4.14#64029)
