[MAGNOLIA-9232] JcrResourceOrigin never unregisters observation listener Created: 18/Dec/23  Updated: 01/Feb/24  Resolved: 01/Feb/24

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Bug Priority: Neutral
Reporter: Michael Duerig Assignee: Michael Duerig
Resolution: Fixed Votes: 0
Labels: dx-core-6.3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Throughput improvements
Work Started:
Approved:
Yes

 Description   

The listener registered in JcrResourceListner#initializeResourceChangeMonitoring is never unregistered.
This is used from DefaultMessageBundlesLoader, AbstractFileResourceConfigurationSource and YamlDecorationConfigurationSource. All of which (presumably) have the same lifecycle as the Magnolia instance, which makes not de-registering them less critical.



 Comments   
Comment by Michael Duerig [ 30/Jan/24 ]

Reopening since these listeners potentially block the timer thread introduced with MAGNOLIA-9181 from exiting.

Generated at Mon Feb 12 04:39:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.