aakarsh 's Profile

recovering from a crash

server overload

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

="vuel491u"

cache ID, session ID, separator, clone ID, and partition ID

plug-in-cfg.xml

session.getId().

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

The session ID,

can be shared across Web applications.

Web application that created the session

user's session ID into static pages,

encoding with redirection

<% response.encodeURL ("/store/catalog"); %>

special encoding APIs

$jsessionid=DA32242SSGE2"
>
>

site page flow

URL rewriting

S
SL session
>

SL session identifiers

JSESSIONID, which is required by the Servlet 2.4

http://home.netscape.com/newsref/std/cookie_spec.html

age in seconds

LTPA token/cookie

ngle DNS domain specified when global security is configured

Restrict cookies to HTTPS sessions

disable them from within their browser.

JSESSIONID

HttpSession session = request.getSession(true);

Cookies

SSL ID tracking is the performance hit of using SSL

BM HTTP Server,

lifetime of an SSL session ID

SSLV3TIMEOUT

SSL tracking is supported only for the IBM HTTP Server

failure of an application server

it cannot survive an HTTP server failure.

SSL ID tracking

application server, enterprise application, or Web module

all three options

Cookies

SSL session identifiers

session object

Session identifiers

use the simplest form

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

can cause memory leak

size of the general cache.

no timeout,

persistent sessions,

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.

sess.isOverFlow())

IBM HttpSession extension

will be dummy sessions

Allow overflow

local sessions,

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,

first cache

1000 by default

erver failure takes down

unlimited number of sessions in memory

number of sessions

lacks a persistent store for the sessions

they return to the machine

Local sessions