TheKeep-Alive subsystem periodically polls such idle connections and queues those
connectionswith activity into the connection queue for future processing. From there, a request
processingthread again retrieves the connection and processes its request. The Keep-Alive
subsystemis multi-threaded, as it manages potentially tens of thousands of connections.
Ecientpolling techniques are used, by dividing the number of connections into smaller
subsets,to determine which connections are ready with requests and which of those
connectionshave idled for sucient time to deem them closed (beyond a maximum
permissibleKeep-Alive timeout).
TheHTTP listener’s server name is the host name that appears in the URLs the server sends to
theclient as part of a redirect. This attribute aects URLs the server automatically generates; it
doesnot aect the URLs for directories and les stored in the server. This name is normally the
aliasname if the server uses an alias. If a client sends a Host: header, that host name supersedes
theHTTP listener’s server name value in redirects.
Specifya redirect port to use a dierent port number from that specied in the original request.
Aredirectoccurs in one of these situations:
■Ifa client tries to access a resource that no longer exists at the specied URL (that is, the
resourcehas moved to another location), the server redirects the client to the new location
(insteadof returning a 404), by returning a designated response code and including the new
locationin the response’s Location header.
■Ifa client tries to access a resource that is protected (for example, SSL) on the regular HTTP
port,the server redirects the request to the SSL-enabled port. In this case, the server returns
anew URL in the Location response header, in which the original insecure port has been
replacedwith the SSL-enabled port. The client then connects to this new URL.
Specifyalso whether security is enabled for an HTTP listener and what kind of security is used
(forexample, which SSL protocol and which ciphers).
Toaccess a web application deployed on the Enterprise Server, use the URL
http://localhost:8080/(or https://localhost:8181/ if it is a secure application), along
withthe context root specied for the web application. To access the Admin Console, use the
URLhttps://localhost:4848/ or http://localhost:4848/asadmin/ (its default context
root).
Becausea virtual server must specify an existing HTTP listener, and because it cannot specify an
HTTPlistener that is already being used by another virtual server, create at least one HTTP
listenerbefore creating a new virtual server.
HTTPListeners
SunGlassFishEnterprise Ser ver2.1 Administration Guide • December 2008152