Details
-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
1.3.13
-
None
Description
We are running into support issues where we cannot track down exactly went wrong during a publishing issue. The only information received is a vague message in the UI. The logs don't have any useful information or trace.
Observed issues are:
- javax.jcr.ItemNotFoundException
- java.lang.IllegalStateException --> RepositoryException
Reproduce
- Publish a page
- Delete the page
- Try to approve and publish the original task
Actual
When trying to publish the original task after the deletion we see this message in the UI (i.e. failed task):
javax.jcr.ItemNotFoundException: af4cd608-2dda-4535-a5e0-703ef92fd45a
In the log we have only:
INFO info.magnolia.module.scheduler.CommandJob 09.11.2023 12:42:19 -- Starting job [asyncCommand1699533739622]... ERROR info.magnolia.module.scheduler.CommandJob 09.11.2023 12:42:19 -- Cannot execute command [personalizationActivation] for job [asyncCommand1699533739622] in catalog [null] INFO info.magnolia.module.workflow.jbpm.workitem.handler.AsyncWorkItemHandler 09.11.2023 12:42:19 -- WorkItem [asyncCommand] was aborted.
Expected
We need to handle this a little more elegantly in the UI. Can we improve the UI feedback with possible root cause(s)? Can we avoid this issue altogether with some kind of conflict detection. Meaning, upon deletion can we check there are no pending tasks?
Notes
I believe that when a page is scheduled we need to have some metadata on the page node itself. I have outline a possible solution for an incubator module here INCUBATOR-50.
Further more we have seen issues like:
This seems to indicate a save happened around the same time as publish. Can we add a check on the publish which can detect if someone is currently working on the page?
Checklists
Attachments
Issue Links
- is related to
-
PUBLISHING-74 Handle NullPointerException when publishing an already deleted node
-
- Open
-