[PUBLISHING-314] Missing stack trace - difficulties tracking down publishing issues Created: 09/Nov/23  Updated: 10/Nov/23

Status: Open
Project: Publishing
Component/s: None
Affects Version/s: 1.3.13
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-11-07-11-47-55-466.png    
Issue Links:
relation
is related to PUBLISHING-74 Handle NullPointerException when publ... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 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?


Generated at Mon Feb 12 10:37:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.