[MAGNOLIA-3844] NullPointerException in DefaultHierarchyManager.isExist() while calling from an EventListener Created: 23/Sep/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.4.4, 4.4.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Ronald Ten Berge Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: core, hierarchymanager
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Only tested FreeBSD and Windows XP platforms


Attachments: Text File BugTest.java     PNG File HierarchyManagerBug.png     XML File config.modules.observation.config.listenerConfigurations.nxpTestListener.xml    
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 using multiple event listeners to export data from Magnolia and we are seeing multiple NullPointerException in our logs.

The stacktrace for the exception:
Exception in thread "Thread-48" java.lang.NullPointerException
at info.magnolia.cms.core.DefaultHierarchyManager.isExist(DefaultHierarchyManager.java:399)
at trimm.nxp.wcm.test.BugTest.execute(BugTest.java:14)
at trimm.nxp.wcm.test.BugTest.onEvent(BugTest.java:20)
at info.magnolia.module.observation.util.ObservationUtil$ObservationBasedDelayedExecutor$1.run(ObservationUtil.java:361)
at info.magnolia.cms.util.DelayedExecutor$RunnableWrapper.run(DelayedExecutor.java:104)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
at java.lang.Thread.run(Thread.java:662)

The cause of this Exception lies in the "re.getCause()" call. This method tries to retrieve the rootCause, but the rootCause is null (see the attached screenshot).

The attached class uses the data workspace and triggers this bug when running using the observation module (configuration export attached).



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:50:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.