General properties are as follows:
Description An optional text description of the Web application.
Distributable Specifies whether multiple instances of the Web application can run in a distributed server environment on different servers. If you do not select this option and run the Web application in an EAServer cluster, all requests for the Web application must go to one server in the cluster. Further configuration is required for distributed Web applications, as described in “Deploying Web applications to a cluster” in the EAServer System Administration Guide.
Timeout This option specifies how long the server should wait for each servlet’s init method to return. For any value, no client requests are serviced while the init method is running. Service requests that arrive while init is running are blocked until init returns. Clients receive browser timeout errors when attempting to execute the servlet while init is running. You can set the Timeout value to control how the server treats servlets if the init method is still running when you shut down the server or refresh the servlet. Table 21-1 describes the possible values.
Value |
To indicate |
|---|---|
-1 |
(The default.) init can run indefinitely, unless the server is shutdown or refreshed. If the init method is still running when the server is shutdown or refreshed, the server does not wait for init to complete before shutting down or refreshing the servlet. |
0 |
init can run indefinitely. Sybase does not recommend this setting, because deadlocks or other hangs in the init method can cause the server to hang when shutting down or refreshing the servlet. |
A positive integer. |
The number of seconds to wait for init to return. If the init method is still running when the server is shutdown or refreshed, the server waits the specified time for init to return. |
You can override the application-wide default for individual servlets. Display the Advanced tab in the Servlet Properties window, then set the com.sybase.jaguar.servlet.init.timeout property using the syntax in Table 21-1.
Destroy Timeout EAServer calls each servlet’s destroy method before shutting down or after you have refreshed or stopped the servlet using EAServer Manager. If service calls are still active, the Destroy Timeout setting specifies the number of seconds that the server should wait for the service calls to return before calling the destroy method. The default is 0, which specifies that EAServer calls destroy immediately.
You can override the application-wide default for individual servlets. Display the Advanced tab in the Servlet Properties window, then set the com.sybase.jaguar.servlet.destroy.wait-time property to the desired number of seconds.
Session Timeout This option specifies an application-wide default for the servlet Session Timeout property. Session timeouts are specified in minutes; the default is 30. A value of -1 indicates that sessions never expire. You cannot override the session timeout for individual servlets.
Context Path The request-path prefix that clients use in URLs to access your Web application’s static content, servlets, and JSPs. For example, if you enter “estore,” users access your Web application with the prefix:
http://host:port/estore/
The default context path is the name of your Web application.
Client Session Persistent This property determines whether the cookies used to store servlet and JSP session data is stored in persistent or temporary cookies. By default, session data is stored in temporary cookies that expire when the browser is shut down. When you select this option, EAServer sends a persistent cookie that expires when the Web application session-timeout setting expires. This property affects only the cookies that EAServer creates to store session data for the Web application (available to servlets and JSPs via request.getSession). It does not affect cookies created explicitly by servlets and JSPs.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
