You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The startup process of a Spring Boot application that uses Spring-zeebe fails if it cannot reach zeebe.
Wanted behavior
Spring Boot application starts and throws a ConnectException every few seconds.
Reason for this feature
Our workers also have a UI and other functionalities. For local development, we want to launch only the services we need. Currently, at least zeebe and elasticsearch would always have to start, even if we only want to make changes to the worker's UI, for example. With this feature, we wouldn't have to do that anymore.
The text was updated successfully, but these errors were encountered:
I have also run in to this limitation. Allowing the spring boot application to start when Zeebe is unreachable would be very welcome. Perhaps with a configurable number of retry attempts, a back off multiplier and some sensible default values.
Current behavior
The startup process of a Spring Boot application that uses Spring-zeebe fails if it cannot reach zeebe.
Wanted behavior
Spring Boot application starts and throws a ConnectException every few seconds.
Reason for this feature
Our workers also have a UI and other functionalities. For local development, we want to launch only the services we need. Currently, at least zeebe and elasticsearch would always have to start, even if we only want to make changes to the worker's UI, for example. With this feature, we wouldn't have to do that anymore.
The text was updated successfully, but these errors were encountered: