Recent Bookmarks and Annotations
-
System Management and Configuration on 2007-01-19
-
ese features are new with th
-
Session affinity on 2007-01-12
-
By sending cache overflow to a persistent session store, the administrator controls the number of sessions allowed in memory at any given time.
-
acklog queue where an entry is made for each request
-
-
-
-
retry timeout to a small value.
-
separately maintains its own retry timer value
-
Web server is multi-processed
-
failed cluster member is running again.
-
concurrent requests for the same session could end up in different cluster members
-
equests for the session go back to the failed cluster member when the failed cluster member restart
-
cluster member list in order and picks the cluster member next
-
single cluster member can control and access a given session at a time
-
cache ID and server ID will change in the cookie when there is a failover
-
-
cache ID, session ID, separator, clone ID, and partition ID
-
-
-
unique ID of the cluster member handling the session,
-
ession ID from the HTTP header, request.getHeader("Cookie"),
-
erver ID is appended to the session ID.
-
The exception to this rule is when the cluster member fails or has to be shut down.
-
single JVM for that application at any one time
-
-
can be shared across Web applications.
-
Web application that created the session
-
O'Reilly -- Safari Books Online - 0738492019 - WebSphere Application Server V6 System Management and Configuration Handbook on 2007-01-12
-
URL encoding from a servlet
-
protocol switch rewriting
-
-
user's session ID into static pages,
-
encoding with redirection
-
<% response.encodeURL ("/store/catalog"); %>
-
-
$jsessionid=DA32242SSGE2"
>
>
-
-
-
-
-
| Click OK to exit the session management settings. |
-
JSESSIONID, which is required by the Servlet 2.4
-
http://home.netscape.com/newsref/std/cookie_spec.html
-
-
-
ngle DNS domain specified when global security is configured
-
Restrict cookies to HTTPS sessions
-
disable them from within their browser.
-
-
HttpSession session = request.getSession(true);
-
-
SSL ID tracking is the performance hit of using SSL
-
-
lifetime of an SSL session ID
-
-
SSL tracking is supported only for the IBM HTTP Server
-
failure of an application server
-
it cannot survive an HTTP server failure.
-
-
application server, enterprise application, or Web module
-
-
-
-
-
-
-
General properties for session management on 2007-01-12
-
Local sessions on 2007-01-12
-
serialized access to the session in a given JVM.
-
ultiple threads could access the same session at the same time
-
-
orm-based login configured as the authentication method and the local operating system is the authentication mechanism.
-
session manager associates the identity of users with their HTTP sessions
-
-
size of the general cache.
-
-
-
unless explicit invalidation has been performed by the servlet
-
30 minutes, the invalidation process interval is around 300 seconds
-
t directly influences the amount of memory consumed by the JVM in order to cache the session information.
-
-
IBM HttpSession extension
-
-
-
-
Maximum in-memory session count
-
Each Web application will have its own base, or primary, in-memory session cache, and with overflow allowed, its own overflow, or secondary, in-memory session cache.
-
state of the session cache should be monitored closely
-
un-optimized hash table contains the overflow cache.
-
first cache for optimized retrieval,
-
-
-
-
-
unlimited number of sessions in memory
-
-
lacks a persistent store for the sessions
-
they return to the machine
-
-
Packages and directories for generated .java and .class files on 2007-01-12
-
JSP class file generation on 2007-01-12
-
JavaServer Pages on 2007-01-12
-
Web modules on 2007-01-12
-
autoRequestEncoding and autoResponseEncoding on 2007-01-12
Groups
Aakarsh havn't joined any group yet.