[
https://issues.apache.org/jira/browse/SLING-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870707#comment-15870707
]
Bjoern Weide commented on SLING-6482:
-------------------------------------
Stacktrace:
{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)
at
org.apache.sling.commons.log.logback.internal.SlingLogPanel.appendOsgiConfiguredLoggerData(SlingLogPanel.java:221)
at
org.apache.sling.commons.log.logback.internal.SlingLogPanel.render(SlingLogPanel.java:110)
at
org.apache.sling.commons.log.webconsole.internal.LogWebConsolePlugin.renderContent(LogWebConsolePlugin.java:79)
at
org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:194)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:618)
{noformat}
It can be reproduced by adding a new logger with an empty log file entry.
> 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)
