Abstract: Arrangements for autonomously re-initializing one or more applications after a detected change in device state are provided. In some examples, a configuration file may be received from one or more computing devices, such as a server, hosting one or more client-facing applications. In some examples, the configuration file may be modified. For instance, one or more properties or attributes may be modified or added to identify applications that have an always running status and identifying a custom class having automatic start enabled. A modified configuration file may be generated and transmitted to the one or more devices. Accordingly, upon detecting a change of device state (e.g., reboot, refresh, or the like) the modified configuration file may reboot and cause the identified applications to automatically or autonomously re-load, re-initialize and recompile prior to receiving a first request for access from a customer or user device.

Abstract: Arrangements for autonomously re-initializing one or more applications after a detected change in device state are provided. In some examples, a configuration file may be received from one or more computing devices, such as a server, hosting one or more client-facing applications. In some examples, the configuration file may be modified. For instance, one or more properties or attributes may be modified or added to identify applications that have an always running status and identifying a custom class having automatic start enabled. A modified configuration file may be generated and transmitted to the one or more devices. Accordingly, upon detecting a change of device state (e.g., reboot, refresh, or the like) the modified configuration file may reboot and cause the identified applications to automatically or autonomously re-load, re-initialize and recompile prior to receiving a first request for access from a customer or user device.