InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.9: Administering servlets (overview) >
6.6.9.0: Servlet properties

6.6.9.0: Servlet properties

Current State
Indicates the state the servlet is currently in. The next time it is started, it will try to change to its desired state setting.
Debug Mode
Specifies whether to run the servlet code in debug mode.

Debug Mode in use
Indicates whether the servlet is now running in debug mode.

Description
Specifies a description of the servlet.

Desired State
Indicates the state the servlet is in, according to the administrative server.

Enabled
Indicates whether the servlet is available to handle requests.

Init Parameters
Specifies values for the parameters the servlet uses when it is initially loaded. The parameter names specified here must match the parameters known to the servlet class code.

Instead of a constructor, a servlet uses an init() method and a ServletConfig interface that specifies its initialization parameters. The parameter-value pairs you specify in Init Parameters are added to the servlet's ServletConfig object.

Init Parameters in use
The initial parameters (see above) now in use by the servlet.

Load at Startup
Specifies whether to load the servlet when the Web application containing it is started. If this value is false, the servlet will not be loaded until it is first requested.

Selecting to load at startup is a performance decision. It transfers the burden of the servlet load time to the Web application load time, instead of making the user wait for the servlet to load the first time it is requested.

  If one servlet in a Web application fails to load at startup, the entire Web application is considered invalid and cannot be accessed by users. The symptom is "Error 503: Application is currently unavailable for service."

Follow good practices to prevent the above condition:

  • If a servlet is known to throw exceptions at startup, make sure it has a try-catch statement in its init() method to prevent its failure.
  • If the servlet loads successfully, but you need to change its class file later, overwrite the class file. If you instead delete the class file and then add a new one, the Web application classloader will consider the servlet removed and declare the Web application invalid.

Load at Startup in use
Indicates whether the servlet is currently specified to load when the administrative server is started (see Load at Startup).

Servlet Class Name
Specifies the servlet class name. Specify the package, but do not include the .class extension. For example, com.ibm.server.MyClassName demonstrates a valid format.

Servlet Class Name in use
Indicates the name of the servlet class (see above) currently in use.

Servlet Name
Specifies a name for the servlet.

Servlet Web Path List
Specifies one or more Uniform Resource Identifiers (URIs) by which this servlet can be located and invoked.

This setting is affected by the servlet engine mode setting introduced with Version 3.5.2. See the Servlet Engine Mode field help description for details.

Servlet Web Path List in use
Indicates the servlet URI list (see above) now in use.

Start Time
Indicates the time at which the servlet was most recently loaded. A value of "--" indicates the servlet has not yet been loaded since the application server containing the servlet was started.

Web Application
Specifies the Web application with which the servlet is associated.

Go to previous article: Administering servlets (overview) Go to next article: Administering servlets with the Java administrative console

 

 
Go to previous article: Administering servlets (overview) Go to next article: Administering servlets with the Java administrative console