Response to an unresponsive Add-on service
You can configure what happens when a client fails to connect to the Add-on service. By default, the service responds by killing the JVM, forcing the container to recycle.
The response behavior to an unresponsive Add-on service is configurable through an environment variable called addonunavailablekillservice. This defaults to true if not set. If your client is a Content Delivery microservice, you can set this environment variable using a -D switch in your microservice installation or startup script.
addonunavailablekillservice is as follows:
addonunavailablekillservicehas the valuetrue- When the client-side service starts, it attempts to connect to the Add-on service. If it fails to do so, it removes all existing Extensions before loading.
addonunavailablekillservicehas the valuefalse- When the client-side service starts, it attempts to connect to the Add-on service. If it fails to do so, it loads all previously loaded Extensions.