Deployment Kubernetes: hazelcast session not getting acive - app is shutting down

Hello,

our JMIX application was configured according to the JMIX Kubernetes deployment documentation. However, the container will be shut down after the end. This message appears:

2022-11-09 14:54:21.945 WARN 1 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - canceling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eclipseLinkChannelSupplier' defined in class path resource [io/jmix/autoconfigure/eclipselink/JmixEclipseLinkChannelAutoConfiguration$HazelcastChannelConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [io.jmix.eclipselink.impl.support.EclipseLinkChannelSupplier]: Factory method 'eclipseLinkChannelSupplier' threw exception; nested exception is com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!
2022-11-09 14:54:22.032 INFO 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown initiated...
2022-11-09 14:54:22.038 INFO 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown completed.

Attached is the complete log file.

Regards,
Maik

jmix.topic.application.log (21.1 KB)

Hello Maik,

It is difficult to say something based on the log only.
Does this problem come up constantly or occur from time to time?

Could you please provide an example project to reproduce this problem?
Additional information about the environment (OS, memory size, versions of Jmix, Minikube and vm for it, Kubernetes, Docker, etc.) will be helpful too.

Regards,
Dmitry

Hello Dimitry,

In the course of creating the test case project, we found errors in the configuration of Kubernetes. Our JMIX app is now running in the Kubernetes cluster.

Many Thanks.

Regards,
Maik

1 Like