[
https://issues.apache.org/jira/browse/JCRVLT-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123471#comment-18123471
]
Konrad Windszus edited comment on JCRVLT-852 at 10/5/26 5:50 PM:
-----------------------------------------------------------------
I see your additional PR on JCRVLT-851 to also remove the temp files:
https://github.com/apache/jackrabbit-filevault/pull/434
I guess that's the better way to handle this, as it avoids the immediate
impact. For that JCRVLT-591 can be turned on selectively only when we actually
want to figure the reasons for all unclosed packages.
was (Author: joerghoh):
I see your additional PR on JCRVLT-851 to also remove the temp files:
https://github.com/apache/jackrabbit-filevault/pull/434
I guess that's the better way to handle this, as it avoids the immediate
impact. For that JCRVLT-851 can be turned on selectively only when we actually
want to figure the reasons for all unclosed packages.
> For unclosed packages log the stack when the package was opened
> ---------------------------------------------------------------
>
> Key: JCRVLT-852
> URL: https://issues.apache.org/jira/browse/JCRVLT-852
> Project: Jackrabbit FileVault
> Issue Type: Task
> Affects Versions: 4.1.4
> Reporter: Joerg Hoh
> Assignee: Joerg Hoh
> Priority: Major
>
> When a VaultPackage was opened but not closed, log not only log an ERROR, but
> also log the stack where this VaultPackage was opened.
> The functionality is alreadyd present (see JCRVLT-591), but logging the stack
> is disabled, which makes fixing this issue harder than it could be.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
