Show TOC

 Application Startup ModesLocate this document in the navigation structure


To decrease the initial load on the AS Java and to minimize its startup time at each restart, you should use the most appropriate startup modes for your applications.


There are no additional requirements for the alwaysand manual startup modes.

Each application consists of one or more modules. Each container handles different types of modules. To implement lazy startup, a container must be able to start an application when the first request to it is made.


One application can use lazy startup mode, if it consists exclusively of modules that are handled by containers supporting lazy startup mode. Such an application is called a lazy enabled application.


Each application can be in one of the next startup modes:

  • always - application starts each time the AS Java is restarted.
  • lazy - if a lazy enabled application has not been started when the AS Java was stopped, containers are responsible for starting this application at the first request.
  • manual - application cannot be started automatically, and calls to startApplication() throw the applicationDisabled exception.

    Manual mode is not supported completely due to possible implications for other parties. Applications with manual mode do not initially, but can be started manually later on.

  • disabled - application cannot be started.

To specify the startup mode, you need to modify the application-j2ee-engine.xml to contain the element <start-up mode ="<startup_mode>">, where <startup_mode> stands for one of the possible startup modes.

If no value is specified, the default value is lazy.


Applications that are not lazy enabled, but have the startup option set to lazy, are treated automatically as if they have the always startup option.