-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 11.1
-
Fix Version/s: explorer-20.0.0, 11.3, 2021.0
-
Epic Link:
-
Impact type:API change
-
Upgrade notes:
-
Team:AT
-
Sprint:nxAT 11.1.23
-
Story Points:3
Nuxeo startup logs have been modified with a series of changes (NXP-20911, NXP-19326, NXP-22560, NXP-22749, NXP-23864).
The behaviour needs a review because, testing with faulty contributions at NXP-28948, the duplicate component name is not logged anymore at startup, apparently due to changes at NXP-22749.
Also, these errors should be logged at error level instead of warn level.
Need also to make sure it still behaves correctly in hot reload use case after changes.
Also, there is deprecated code for duplicate components, dropping the error/warn log for components whose name starts with "org.nuxeo.runtime". If i remember well, this weird behaviour was seen on jboss distributions, and does not seem to be visible anymore.
Update on this: this seems to still be valid, sadly:
2020-08-06T15:46:35,392 ERROR [ComponentManagerImpl] Duplicate component name: service:org.nuxeo.runtime.EventService 2020-08-06T15:46:35,394 ERROR [ComponentManagerImpl] Duplicate component name: service:org.nuxeo.runtime.RuntimeComponent 2020-08-06T15:46:35,395 ERROR [ComponentManagerImpl] Duplicate component name: service:org.nuxeo.runtime.services.resource.ResourceService 2020-08-06T15:46:35,396 ERROR [ComponentManagerImpl] Duplicate component name: service:org.nuxeo.runtime.LoginComponent 2020-08-06T15:46:35,397 ERROR [ComponentManagerImpl] Duplicate component name: service:org.nuxeo.runtime.LoginAsComponent 2020-08-06T15:46:35,398 ERROR [ComponentManagerImpl] Duplicate component name: service:org.nuxeo.runtime.model.persistence 2020-08-06T15:46:35,399 ERROR [ComponentManagerImpl] Duplicate component name: service:org.nuxeo.runtime.trackers.files 2020-08-06T15:46:35,401 ERROR [ComponentManagerImpl] Duplicate component name: service:org.nuxeo.runtime.ConfigurationService
- is duplicated by
-
NXP-16642 verify the following errors are reported in runtime statuses
- Resolved
-
NXP-18337 nuxeo-runtime bundles must not be registered twice
- Resolved
-
NXP-19331 Improve Runtime Contributions Error/Debug/Test management
- Resolved
- is related to
-
NXP-22560 Fix Studio snapshot hot reload in Admin Center
- Resolved
-
NXP-20911 Fix detection of contributions to missing target extension points at runtime startup
- Resolved
-
NXP-19326 Nuxeo Runtime Evolutions - Step 1
- Resolved
-
NXP-22749 Empty runtime warning messages at hot reload
- Resolved
-
NXP-23864 Fix startup logging thresholds
- Resolved
-
NXP-29547 Be more resilient to invalid XML runtime contributions
- Resolved
-
NXP-19331 Improve Runtime Contributions Error/Debug/Test management
- Resolved
-
NXP-28914 Log failure exception in BackingServiceConfigurator
- Resolved
- is required by
-
NXP-28948 Handle components in error in Explorer export
- Resolved
-
NXP-29573 Better track runtime errors and warnings
- Resolved
- Is referenced in