[
https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909679#action_12909679
]
Michael Dürig commented on JCR-2749:
------------------------------------
I'm generally fine with lowering to debug level. However I fear this will also
hide potential problems during development instead on forcing us to fix them.
This is why I proposed to throw an AssertionError in dev mode. I think we have
a system property for integration testing already which could be used here.
Jukka?
> Closing a session twice shouldn't write a warning in the log
> ------------------------------------------------------------
>
> Key: JCR-2749
> URL: https://issues.apache.org/jira/browse/JCR-2749
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Affects Versions: 2.2.0
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: sessionClose.txt
>
>
> When closing a session twice the following warning is written to the log file
> as of JCR-2741:
> "This session has already been closed. See the chained exception for a trace
> of where the session was closed."
> I think the second "close()" should simply be ignored, without warning.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
