search

gravitee-io / issues

Gravitee.io - API Platform - Issues
64 stars 26 forks source link

Security Domain may not be loaded on gateway startup #9496

Closed exalate-issue-sync[bot] closed 7 months ago

exalate-issue-sync[bot] commented 7 months ago

It may happen that the DefaultReactor service, which is responsible to manage the domains, can start after the SyncManager which is responsible to dispatch domain events. (see logs)

22:51:20.150 [sync-1] [] INFO i.g.a.g.r.i.DefaultSecurityDomainManager - Deployment of aa0fcc62-8e02-41c1-8fcc-628e02d1c18c
 22:51:20.151 [graviteeio-node] [] INFO i.g.n.m.monitor.NodeMonitorService - Node monitoring scheduled with fixed delay 5000 MILLISECONDS 
 22:51:20.156 [graviteeio-node] [] INFO i.g.n.m.h.v.e.ManagementEndpointManagerImpl - Register a new endpoint for Management API: GET /monitor [io.gravitee.node.monitoring.monitor.NodeMonitorManagementEndpoint]
 22:51:20.157 [graviteeio-node] [] INFO i.g.node.container.AbstractNode - Starting component: ReporterManager
 22:51:20.157 [graviteeio-node] [] INFO i.g.common.service.AbstractService - Initializing service Reporter service
 22:51:20.158 [graviteeio-node] [] INFO i.g.node.container.AbstractNode - Starting component: KeyStoreLoaderManager
 22:51:20.158 [graviteeio-node] [] INFO i.g.common.service.AbstractService - Initializing service io.gravitee.node.certificates.KeyStoreLoaderManager
 22:51:20.158 [graviteeio-node] [] INFO i.g.node.container.AbstractNode - Starting component: Reactor
 22:51:20.159 [graviteeio-node] [] INFO i.g.common.service.AbstractService - Initializing service io.gravitee.am.gateway.reactor.impl.DefaultReactor
 22:51:20.232 [graviteeio-node] [] INFO i.g.c.event.impl.EventManagerImpl - Register new listener DefaultReactor for event type class io.gravitee.am.common.event.DomainEvent

As a consequence, the Gateway may not load active domains during the startup.

exalate-issue-sync[bot] commented 7 months ago

This issue will be fixed in versions 4.1.14, 4.0.11, 4.2.4