[PUBLISHING-30] Wrong publishing storage object in use Created: 07/Nov/17 Updated: 29/Mar/22 Resolved: 10/Nov/17 |
|
| Status: | Closed |
| Project: | Publishing |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Sprint: | Kromeriz 121 | ||||||||
| Team: | |||||||||
| Description |
|
The code below holds the publishingStorage created at the time the monitor is created. So it's completely different object after the publishing module restart resulting in an empty activation monitor report.
@Inject
public PublishingMonitor(Provider<PublishingCoreModule> publishingCoreModuleProvider) {
MBeanUtil.registerMBean("PublishingMonitor", this);
this.publishingStorage = publishingCoreModuleProvider.get().getPublishingLogStorage();
}
This used to be an issue in the old activation as well, see info.magnolia.module.activation.monitor.ActivationMonitor#ActivationMonitor. But now there is high change to hit the issue, since we moved all the config under the module (it used to be only config for the activation storage itself). |