Currently the different client instances like EventStoreDBClient or EventStoreDBProjectionManagementClient will automatically shutdown if they are not able to establish a connection to the Event Store, the download of the server features fails fatally or after a manual shutdown.
The client does not support a way for a user of a client instance to determine if the client has been shutdown or is still "up and running".
This means, that currently the only way to determine if client instance is checking for a ConnectionShutdownException inside the ExecutionException of the CompletableFuture when executing a command. This is quite cumbersome and cannot be "centralized", i.e. done in a central place to check the healthyness of the client instance.
The API should provide a simple method for checking the status of the client like:
public boolen isShutdown() or public boolean isRunning(), isActive() etc.
dpasek-senacor
commented
2 years ago
Currently the different client instances like
EventStoreDBClientorEventStoreDBProjectionManagementClientwill automatically shutdown if they are not able to establish a connection to the Event Store, the download of the server features fails fatally or after a manual shutdown. The client does not support a way for a user of a client instance to determine if the client has been shutdown or is still "up and running". This means, that currently the only way to determine if client instance is checking for aConnectionShutdownExceptioninside theExecutionExceptionof theCompletableFuturewhen executing a command. This is quite cumbersome and cannot be "centralized", i.e. done in a central place to check the healthyness of the client instance.The API should provide a simple method for checking the status of the client like:
public boolen isShutdown()orpublic boolean isRunning(),isActive()etc.