DS is up after kernel-cache pre-loading

Data Services
1

Since the upgrade to 2023.06 we see that our DS-Application is successfully up, until the Pre-Loading of the Kernel-Cache is done. It wasn’t the case in 2023.02

Is this intended ? I see that the EventListener-Method of the KernelCachesPreloader is @Async but some how it blocks the application be “up”

2023-10-10T11:08:13.395+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_3__Cockpit_Summenwerte_Verausserung_AT finished in 16233 ms
2023-10-10T11:08:13.772+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_1__FB_AT_Allgemeines finished in 377 ms
2023-10-10T11:08:13.975+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of WiedervorlageWithWorkflowsMetadata_1 finished in 203 ms
2023-10-10T11:08:14.887+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_3__FB_Allgemein finished in 911 ms
2023-10-10T11:08:15.492+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_3__FB_AT_Allgemeines finished in 605 ms
2023-10-10T11:08:15.640+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_3__FB_GJF_Festst_P33Abs2u4 finished in 147 ms
2023-10-10T11:08:15.786+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_1__Hinweise.row finished in 146 ms
2023-10-10T11:08:15.940+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_2__FB_AT.row finished in 153 ms
2023-10-10T11:08:16.190+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_2__InvSt1_Allgemeines finished in 250 ms
2023-10-10T11:08:21.104+02:00  INFO 77585 --- [S.HealthMonitor] c.h.internal.diagnostics.HealthMonitor   : [<INTERNAL_IP>]:5702 [dev] [5.2.4] processors=12, physical.memory.total=46.7G, physical.memory.free=4.6G, swap.space.total=0, swap.space.free=0, heap.memory.used=2.2G, heap.memory.free=242.6M, heap.memory.total=2.4G, heap.memory.max=2.4G, heap.memory.used/total=90.29%, heap.memory.used/max=90.29%, minor.gc.count=1557, minor.gc.time=22429ms, major.gc.count=6, major.gc.time=3785ms, load.process=0.00%, load.system=32.93%, load.systemAverage=6.25, thread.count=99, thread.peakCount=115, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=1, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=0, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
2023-10-10T11:08:29.113+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_3__Cockpit_Bescheid finished in 12922 ms
2023-10-10T11:08:29.783+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_3__FB_AT_EK_Eintragung_Aufteilung finished in 669 ms
2023-10-10T11:08:37.704+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_3__FB_GJF_Festst_NichtAusgAgE finished in 7920 ms
2023-10-10T11:08:38.030+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_3__FB_AT_EK_Eintragung.row finished in 326 ms
2023-10-10T11:08:38.373+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_1__FB_AT_NachrichtlicheAngaben finished in 342 ms
2023-10-10T11:08:38.705+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStNeuZuordnen_1 finished in 331 ms
2023-10-10T11:08:39.036+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_1__InvSt1_Allgemeines finished in 331 ms
2023-10-10T11:08:39.318+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_1__FB_AT_EK_Eintragung.row finished in 281 ms
2023-10-10T11:08:39.483+02:00  INFO 77585 --- [           main] c.m.a.d.s.util.KernelCachesPreloader     : Pre-loading of InvStG51Feststellung_2__FB.row finished in 164 ms
2023-10-10T11:08:39.610+02:00  INFO 77585 --- [           main] c.m.a.u.authorization.UAASecurityBypass  : Security bypass is disabled after application start-up
2023-10-10T11:08:39.611+02:00  INFO 77585 --- [           main] c.mgmtp.<PROJECT_NAME>.server.<PROJECT_NAME>BapServer    : Started <PROJECT_NAME>BapServer in 794.306 seconds (process running for 794.645)
2

Hello,

cache preloading was always async and DS up state never depended on it.

3

I dunno why, but somehow we had following dependency innit

  implementation "com.mgmtp.a12.dataservices:dataservices-server-init-app:${a12ServicesVersion}"

The init app overwrites the TaskExecutor which leads to the fact, that no async executor is used anymore
Here the code from the InitAppApplication

	 * We need to disable async processing for application to stop, Currently only cache preloading is being done asynchronously which does not make any
	 * sense to have in this init application
	 */
	@Bean
	@Primary
	public TaskExecutor taskExecutor() {
		return new SyncTaskExecutor();
	}

So it was a problem on our side :slight_smile: