Reducing HTTP session is functionality that continues request processing by using HTTP session on the J2EE server without interrupting the processing, if a failure described in the following table occurs in a database or on an EADs server.

Table 5-12 Contents of failures for which HTTP session reduction works

Failure occurrence location	Used functionality	Failure contents
Database	The database session failover functionality	Blank records do not exist in the database when creating global session information A database failure occurs while operating global session information
EADs server	The EADs session failover functionality	Fails to update data on the EADs server Successfully updates data on the EADs server, but fails to update data on all other replicated EADs servers

The table describes operations when reducing an HTTP session due to a failure, for each used functionality.

• The database session failover functionality
  

  Table 5-13 Operations when reducing an HTTP session (in the case of the database session failover functionality)

  Occurred failure	Reduction operation	Message output at the time of reduction#	Timing for releasing reduction	Inheriting a reduced HTTP session
  Blank records do not exist in the database when creating global session information.	Creates only HTTP sessions on the J2EE server.	KDJE34367-W	If there are blank records in the database in subsequent HTTP session operations and if you could create global session information.	Not inherited because global session information does not exist in the database.
  A database failure occurs while operating global session information.	Operates only HTTP sessions on the J2EE server.	KDJE34368-W	If you successfully access the database in subsequent HTTP session operations.	If global session information does not exist in the database: Not inherited. If global session information exists in the database: Old global session information might be inherited.

  #

  This message is output for each occurred failure when a session is reduced for the first time. Thereafter, the message is not output after all reduced sessions disappear until you perform session reduction once again. Note that KDJE34369-I message is output if all reduced HTTP sessions disappear.

  
  
• The EADs session failover functionality
  

  Table 5-14 Operations when reducing an HTTP session (in the case of the EADs session failover functionality)

  Occurred failure	Reduction operation	Message output at the time of reduction#1	Timing for releasing reduction	Inheriting a released HTTP session
  Fails to update data on global session information storage destination server.	Operates only HTTP sessions on the J2EE server.	KDJE34427-W	If you could create or update the global session information on the global session information storage destination server and all copy destination servers in subsequent HTTP session operations.	When creating global session information: Not inherited because global session information does not exist on the global session information storage destination server. When updating global session information: Old global session information on the global session information storage destination server is inherited.
  Successfully updates data on the global session information storage destination server, but fails to update data on the copy destination server.	Operates only HTTP sessions on the J2EE server.	KDJE34420-W		When creating global session information: Not inherited, if global session information does not exist on the global session information storage destination server. #2 When updating global session information: Old global session information on the global session information storage destination server might be inherited#3.

  #1

  This message is output for each occurred failure when a session is reduced for the first time. Thereafter, the message is not output after all reduced sessions disappear until you perform session reduction once again. Note that KDJE34428-I message is output if all reduced HTTP sessions disappear.

  #2

  If a failure occurs on the global session information storage destination server and if a copy destination server, on which global session information is not created, is set as the global session information storage destination server, thestate changes to the state where global session information does not exist.

  #3

  If a failure occurs on the global session information storage destination server and if a copy destination server, on which global session information is not updated, is set as the global session information storage destination server, the state changes to the state where old global session information exists.