Microservice startup delay

Forum
,
1

Hey guys
I have a simple microservice. Nothing fancy. The microservice takes too long to be up and running. Below you will find the details

	<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
		<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
		<java.version>17</java.version>
		<maven.compiler.source>17</maven.compiler.source>
		<maven.compiler.target>17</maven.compiler.target>
		<junit.version>4.13</junit.version>
		<spring-boot-dependencies.version>2.5.4</spring-boot-dependencies.version>
		<c8y.version>1018.0.261</c8y.version>
		<microservice.name>w2a-ms-charts-test</microservice.name>
		<c8y.docker.skip>false</c8y.docker.skip>

Logs:

2025-03-11 09:20:24,208 | INF | main     | c.c.m.s.TenantOptionPropertySource                 | 38   | Overriding application settings with tenant options is enabled. 
2025-03-11 09:20:25,209 | INF | main     | o.s.b.a.e.web.EndpointLinksResolver                | 58   | Exposing 4 endpoint(s) beneath base path '' 
2025-03-11 09:20:25,315 | INF | main     | o.s.b.w.e.tomcat.TomcatWebServer                   | 220  | Tomcat started on port(s): 80 (http) with context path '' 
2025-03-11 09:20:25,380 | INF | main     | c.c.m.s.s.i.MicroserviceSubscriptionScheduler      | 73   | Start; subscriptionDelay = 10000, subscriptionInitialDelay = 30000 
2025-03-11 09:20:25,386 | INF | main     | com.wika.c8y.settings.App                          | 61   | Started App in 11.464 seconds (JVM running for 12.975) 
2025-03-11 09:23:39,200 | INF | http-ni  | o.a.c.c.C.[Tomcat].[localhost].[/]                 | 173  | Initializing Spring DispatcherServlet 'dispatcherServlet' 
2025-03-11 09:23:39,200 | INF | http-ni  | o.s.web.servlet.DispatcherServlet                  | 525  | Initializing Servlet 'dispatcherServlet' 
2025-03-11 09:23:39,202 | INF | http-ni  | o.s.web.servlet.DispatcherServlet                  | 547  | Completed initialization in 1 ms

Notice the delay between started app and completed initialization.
The other microservice start almost immediately. This is deployed on the tenant directly and there are not subtenants (although is a multi tenant MS)

2

Can you check the “initialDelaySecond” in the cumulocity.json? Having values of 30 for the livenessProbe and 10 for the readinessProbe should normally be sufficient.

3

Would be interesting to know how your manifest cumulocity.json looks like.

Could be also related to lazy-loading of the DispatcherServlet configured so it will be initiallized on th first request which might occur 3 minutes after the application is up & running.

4 
	"livenessProbe": {
		"httpGet": {
			"path": "/health",
			"port": 80
		},
		"initialDelaySeconds": 200,
		"periodSeconds": 10
	},
	"readinessProbe": {
		"httpGet": {
			"path": "/health",
			"port": 80
		},
		"initialDelaySeconds": 220,
		"periodSeconds": 10
	}
5

Yes, this explains the delay. I think these are values that were provided in an older template. Unless your microservice is doing some very expensive operations on startup I suggest to reduce the “initialDelaySeconds” as suggested above.

1 Like
6

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.