IBM Support

Auto-Start and application restart behaviors

Troubleshooting


Problem

Disabling auto-start for an application and redeploying the application causes the 'auto-start' option back to default value and changing the application setting while it's running causes the application to restart

Symptom

Cause

Resolving The Problem

By default, 'Auto-Start' is enabled during application install and making any changes to an application while it's running causes the application to restart. These behaviors are expected and it's been implemented since WebSphere Application Server release 6.1. Specifically, this technote describes an example of an actual scenario occurred.

In this example, applications were installed on production environment. To prevent service interruption and for business reasons, the 'Auto-Start' option was set to disable. The task can be done as follows:

  1. Go to: Applications -> Enterprise Applications ->
  2. Select an app -> Target specific app status ->
  3. Check the check-box(es) on server ->
  4. Click "Disable Auto Start" button


Additionally, when the applications had to be redeployed after an update to pick up the changes, the Auto-Start once again became enabled by default at the install process. Because Auto-Start option was not wanted, the application configuration was modified to disable auto start. When doing so during the applications runtime caused the applications to restart because the dmgr needed to communicate to the nodeagents to process the binary changes.

Explanations:
According to the WebSphere Info Center, by default, an installed application starts automatically when the server on which the application resides starts. So, when automatic start is disabled, the application does not start when its server starts. Likewise, to enable the automatic starting of the application, select the target and click Enable Auto Start. For more information, see the 'Target specific application status' link below.

In general, making any changes to an application while it's running will result in an application restart. This has to be done in order to pick up the changes. For more information on the application restart, see the 'Enterprise application setting page'.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Administrative Console (all non-scripting)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.5;8.0;7.0;6.1","Edition":"Base;Express;Network Deployment;Single Server","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21509134