You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/01/31 17:49:00 UTC
[jira] [Commented] (SLING-10109) Exception is swallowed in
Bookkeeper.failure(...)
[ https://issues.apache.org/jira/browse/SLING-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275949#comment-17275949 ]
Konrad Windszus commented on SLING-10109:
-----------------------------------------
As the LogMessage does actually contain the full exception, probably just the logging at https://github.com/apache/sling-org-apache-sling-distribution-journal/blob/66cc5c4b867a6a66963a2ebdd5118f7de91adbee/src/main/java/org/apache/sling/distribution/journal/shared/DistributionLogEventListener.java#L62 should be improved..
> Exception is swallowed in Bookkeeper.failure(...)
> -------------------------------------------------
>
> Key: SLING-10109
> URL: https://issues.apache.org/jira/browse/SLING-10109
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
> Affects Versions: Content Distribution Journal Core 0.1.16
> Reporter: Konrad Windszus
> Priority: Major
>
> The exception passed to https://github.com/apache/sling-org-apache-sling-distribution-journal/blob/66cc5c4b867a6a66963a2ebdd5118f7de91adbee/src/main/java/org/apache/sling/distribution/journal/bookkeeper/BookKeeper.java#L195 is not logged completely.
> I have seen messages like this
> {code}
> 30.01.2021 23:21:45.646 [cm-p7802-e44859-aem-author-6df8bd79d7-q2jhs] *WARN* [EventAdminAsyncThread #4] org.apache.sling.distribution.journal.impl.publisher.DistributionPublisher [null] Error processing distribution package dstrpck-1612048904646-54e2c24c-d61e-4829-ba2a-eca44d01dbb4. Retry attempts 0/infinite. Message: Error trying to extract package at path /etc/packages/mypackage-1.0.0-SNAPSHOT.zip
> 30.01.2021 23:21:45.646 [cm-p7802-e44859-aem-author-6df8bd79d7-c9vdj] *WARN* [EventAdminAsyncThread #10] org.apache.sling.distribution.journal.impl.publisher.DistributionPublisher [null] Error processing distribution package dstrpck-1612048904646-54e2c24c-d61e-4829-ba2a-eca44d01dbb4. Retry attempts 0/infinite. Message: Error trying to extract package at path /etc/packages/mypackage-1.0.0-SNAPSHOT.zip
> 30.01.2021 23:21:50.826 [cm-p7802-e44859-aem-author-6df8bd79d7-c9vdj] *WARN* [EventAdminAsyncThread #6] org.apache.sling.distribution.journal.impl.publisher.DistributionPublisher [null] Error processing distribution package dstrpck-1612048904646-54e2c24c-d61e-4829-ba2a-eca44d01dbb4. Retry attempts 1/infinite. Message: Error trying to extract package at path /etc/packages/mypackage--1.0.0-SNAPSHOT.zip
> 30.01.2021 23:21:50.835 [cm-p7802-e44859-aem-author-6df8bd79d7-q2jhs] *WARN* [EventAdminAsyncThread #7] org.apache.sling.distribution.journal.impl.publisher.DistributionPublisher [null] Error processing distribution package dstrpck-1612048904646-54e2c24c-d61e-4829-ba2a-eca44d01dbb4. Retry attempts 1/infinite. Message: Error trying to extract package at path /etc/packages/mypackage-1.0.0-SNAPSHOT.zip
> {code}
> Although the message of the underlying exception is logged, this does not help much as its cause is swallowed.
> The message {{Error trying to extract package at path /etc/packages/mypackage-1.0.0-SNAPSHOT.zip}} is obviously just a wrapper exception around the actual root cause....
--
This message was sent by Atlassian Jira
(v8.3.4#803005)