5.9.4 Impact on servlet API

This subsection describes the following items as an impact on servlet API when using the session failover functionality.

Operating servlet API related to HttpSession objects after inheriting a session
Communicating with a database by invoking a servlet API

Organization of this subsection

(1) Operating servlet API related to HttpSession objects after inheriting a session
(2) Communicating with a database by invoking a servlet API

(1) Operating servlet API related to HttpSession objects after inheriting a session

The following table describes the notes on servlet API related to HttpSession objects after inheriting a session.

Table 5‒13: Notes on servlet API related to HttpSession objects
No.	API name	Notes
1	`getCreationTime()`	If an `HttpSession` object is created by inheriting, the information of the `HttpSession` object before inheriting is inherited.
2	`getLastAccessedTime()`
3	`getId()`	If an `HttpSession` object is created by inheriting, you can obtain the same ID as the `HttpSession` object before inheriting.
4	`isNew()`	Even if an `HttpSession` object is created by inheriting, return value true is not returned.

The servlet AIPs that are not described in this table are not impacted when the session failover functionality is used.

To Page Top

(2) Communicating with a database by invoking a servlet API

If you implement the servlet APIs described in the following table, communication with a database occurs as the extension of API invocation. As a result, performance is affected.

Table 5‒14: Communication with a database
No.	Class	Method
1	`javax.servlet.http.HttpServletRequest`	`getSession()`^#1
2	`javax.servlet.http.HttpServletRequest`	`getSession(boolean create)`^#1
3	`javax.servlet.http.HttpSession`	`invalidate()`^#2

#1: Performance is affected only if you create new HttpSession object.
#2: Performance is affected only if you invoke the invalidate() method in an enabled the HttpSession object.

To Page Top