[OPENIDM-15898] Felix EventAdmin throws SEVERE exception upon shutdown Created: 02/Dec/20  Updated: 20/Apr/21  Resolved: 14/Dec/20

Status: Closed
Project: OpenIDM
Component/s: Module - Configuration
Affects Version/s: 7.1.0
Fix Version/s: 7.1.0

Type: Bug Priority: Major
Reporter: Chris Drake Assignee: Ben Apple
Resolution: Fixed Votes: 0
Labels: BONNEVILLE, regression
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Regression
is caused by OPENIDM-15587 Add waitForCompletion option to confi... Closed
Target Version/s:
Verified Version/s:
QA Assignee: Son Nguyen Son Nguyen
Story Points: 2
Sprint: 2020.16 - IDM
Epic Link: CI/CD: Reliable Ready State

 Description   

Upon shutdown OpenIDM often logs the following SEVERE exception to the console:

-> [29] Dec. 02, 2020 10:51:09.447 A.M. org.forgerock.openidm.config.logging.LogServiceTracker logEntry-> [29] Dec. 02, 2020 10:51:09.447 A.M. org.forgerock.openidm.config.logging.LogServiceTracker logEntrySEVERE: Bundle: org.apache.felix.eventadmin [53] FrameworkEvent ERRORorg.apache.felix.log.LogException: org.osgi.framework.ServiceException: Service factory returned null. (Component: org.forgerock.openidm.config.manage (96)) at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:381) at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:248) at org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350) at org.apache.felix.framework.Felix.getService(Felix.java:3954) at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:450) at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.obtain(EventHandlerProxy.java:286) at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:407) at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:70) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)

The above appears to be related to the introduction of the waitForCompletion flag on the config endpoint. See OPENIDM-15587.



 Comments   
Comment by Son Nguyen [ 20/Apr/21 ]

Verified successfully with OpenIDM: 7.1.0-SNAPSHOT af0d3cb, no regressions or new issues found

Generated at Sun May 09 07:43:16 UTC 2021 using Jira 8.16.0#816000-sha1:a455b91378454416b49bbc88d03e653cb9815ed5.