Browse Prior Art Database

Collocation of HTTP Session Replicas and Stateful Session Bean Replicas Using a ThreadLocal Object

IP.com Disclosure Number: IPCOM000031129D
Original Publication Date: 2004-Sep-13
Included in the Prior Art Database: 2004-Sep-13
Document File: 1 page(s) / 36K

Publishing Venue

IBM

Abstract

Disclosed is a technique that may be used to collocate replicas of state information in a J2EE server context that may otherwise share no common element for unique identification. To be specific, this technique suggests the use of the ThreadLocal object to achieve collocation of replicas of HTTP session and Stateful session bean objects, when the original objects are created in the course of processing requests originating from the same client browser.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 58% of the total text.

Page 1 of 1

Collocation of HTTP Session Replicas and Stateful Session Bean Replicas Using a ThreadLocal Object

In an application server that is creating replicas of HTTP sessions and Stateful Session beans for failure recovery purpose, it is required that these replicas be collocated on the same backup application servers in order to provide hot failover function. For such collocation to be possible, it is required that the replication service instances responsible for creating these replicas communicate information regarding the location of backup replicas to one another.While there exists no commonality between the HTTP session being replicated and the stateful session bean being replicated,since the replication occurs in the same thread that processes the request, the ThreadLocal variable associated with the thread processing the HTTP request can be used to store information regarding the location of the backup store. This information can then be used by the replication service to collocate replicas of http sessions and stateful session beans.

When the request from the client browser is received by the Web container, it uses the information presented by the client browser in the cookie furnished to fetch the HTTP session object associated with this request, if one exists. If this session has been created and replicated previously, the web container puts information regarding the destination of the HTTP session replica(s) in the ThreadLocal object associated with the reque...