[
https://issues.apache.org/jira/browse/JCR-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164321#comment-17164321
]
Julian Reschke edited comment on JCR-4609 at 2/15/21, 1:24 PM:
---------------------------------------------------------------
trunk: (2.21.3) [r1879583|http://svn.apache.org/r1879583]
2.20: (2.20.2) [r1880253|http://svn.apache.org/r1880253]
2.16: (2.16.7) [r1883998|http://svn.apache.org/r1883998]
2.14: [r1886528|http://svn.apache.org/r1886528]
was (Author: reschke):
trunk: (2.21.3) [r1879583|http://svn.apache.org/r1879583]
2.20: (2.20.2) [r1880253|http://svn.apache.org/r1880253]
2.16: [r1883998|http://svn.apache.org/r1883998]
> Improve logging in case of exception in JcrUtils.getRepository()
> ----------------------------------------------------------------
>
> Key: JCR-4609
> URL: https://issues.apache.org/jira/browse/JCR-4609
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons
> Affects Versions: 2.21.2
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Labels: candidate_jcr_2_12
> Fix For: 2.14.9, 2.22, 2.16.7, 2.20.2, 2.21.3
>
> Attachments: JCR-4609-v1.patch
>
>
> Neither full stack traces nor suppressed exceptions are logged in
> https://github.com/apache/jackrabbit/blob/0f0807d25283b8786d800dcc41821443f43c2f82/jackrabbit-jcr-commons/src/main/java/org/apache/jackrabbit/commons/JcrUtils.java#L206
> which makes it hard to debug issues.
> Instead of manually constructing error messages one should rely on
> {{Throwable.printStacktrace()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
