JP2007156775A - Session information management method, system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide technology allowing reduction of consumption of a resource by duplication of session information, while maintaining reliability of continuation of a session. <P>SOLUTION: This session information management method storing the session information in a plurality of computers and managing has a step for reading the definition of an importance level showing the importance level of the session information from a storage device, when request is received from the computer on a client side, acquiring an attribute of the importance level, corresponding to the session information of the received request from the definition of the importance level, adding the acquired attribute of the importance level to the session information of the received request, and storing it into the storage device; a step for reading the definition of a transfer destination, showing the computer that is the transfer destination of the session information from the storage device, acquiring information showing the computer of the transfer destination from the definition of the transfer destination, and transferring the session information of the importance level, corresponding to the computer to the acquired computer of the transfer destination by a communication device; and a step for storing and registering the transferred session information into the storage device of the computer of the transfer destination. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to session information management technology for storing and managing session information such as user IDs in a plurality of computers.

  Conventionally, a plurality of application servers that process requests from client machines are installed in a cluster configuration, and requests from client machines are distributed to arbitrary application servers by a load balancer or the like.

  Further, when a failure occurs in an application server that is processing a request from a client machine, it is necessary for another application server to take over the session information and continue processing. As a method for taking over the session information, there is a method for creating a copy of the session information in the session information management server for holding the session information.

  This method can guarantee consistency by centralized management of session information, easy system construction, automatic deletion of expired session information, etc., but the session information management server is down (stopped due to failure etc.) The session information held in the session information management server is lost, and the session cannot be continued.

In the case of a system that places importance on the reliability of continuation of a session, as another method, there is a method in which a copy of session information is created on the memory in all application servers constituting the cluster.
There are no documents describing known examples of this method. See Patent Document 1 for the closest known example.

JP 2004-78552 A

  However, the method of creating a copy of session information on the memory in all application servers that make up the cluster increases the consumption of resources such as memory usage, communication amount, and processing time in copying session information. There was a problem.

  An object of the present invention is to provide a technique capable of solving the above-described problems and reducing resource consumption due to duplication of session information while maintaining reliability of continuation of the session.

  According to the present invention, in a session information management system that stores and manages session information in a plurality of computers, the session information is transferred to a transfer destination computer and registered in accordance with its importance.

  In the session information management system of the present invention, when a request is received from a computer on the client side, the definition of importance indicating the importance of session information is referred to, and the importance of session information of the received request is defined as the definition of importance. The attribute of the read importance is added to the session information of the received request and stored in the storage device.

  For example, if the information is deleted, the session information such as login information that requires the login operation again at the client is added with a high attribute as the importance, and the information is deleted. However, it does not affect the client, and a low attribute is added to session information such as a database search result that can be regenerated by performing a re-search in the application server.

  Then, after processing the request by the application program and updating the value of the session information, refer to the transfer destination definition indicating the name of the transfer destination computer and the importance of the session information to be transferred, The name of the computer corresponding to the importance added to the session information is read from the definition of the transfer destination, and the session information is transferred to the transfer destination computer. After receiving the transferred session information, the transfer destination computer registers the received session information in the storage device of the transfer destination computer.

  For example, if a failure occurs, the computer that is the next delivery destination of the request is transferred and registered with high and low importance session information, and the importance is low for other computers. Transfer and register the session information.

  After that, if a failure occurs in the computer that is processing the request from the client, the computer that failed is switched to the computer that will be the next delivery destination of the request. When processing a request from the client side, read the attribute of importance added to the session information of the request, check which importance session information is registered for the session, If session information with a high degree of importance and session information with a low degree of importance are registered, the session information is continued using the session information with a high degree of importance and the session information with a low degree of importance.

  In addition, if a failure occurs in the computer that is the next delivery destination of the request, the next computer is switched to the delivery destination, and the request from the client side is processed in the changed computer. When reading, the importance level attribute added to the session information of the request is read, and the level of importance level session information is registered for that session, and only the high level importance session information is registered. If it is, the session information with the higher importance is used, and the session information with the lower importance is generated by the computer and the session is continued.

  According to the present invention, it is possible to reduce resource consumption due to duplication of session information while maintaining reliability of continuation of a session.

  Hereinafter, a session information management system according to an embodiment that stores and manages session information in a plurality of computers will be described in the order of the overall configuration, data configuration, and processing procedure with reference to the drawings.

<< Overall structure >>
FIG. 1 is a diagram showing the overall configuration of the session information management system of this embodiment. As shown in FIG. 1, the session information management system 100 according to this embodiment includes client machines 110 to 112, a network 120, a load balancer 130, and computers 1 to n.

The client machines 110 to 112 are machines used by clients (users), for example, PCs (Personal Computers).
The network 120 is a wide area communication network, for example, the Internet. The client machines 110 to 112 are connected to the load balancer 130 via the network 120.
The load balancer 130 distributes accesses from the client machines 110 to 112 to the computers 1 to n via the communication line 140, and is a so-called load balancer.

<Computer 1 to n (application server computer)>
The computers 1 to n have a cluster configuration, and are computers that receive and process access from the client machines 110 to 112 by distribution from the load balancer 130. Since the computers 1 to n have the same configuration for both hardware and software, the computer 1 will be described as an example.

The computer 1 includes a CPU (Central Processing Unit) 151 and a storage device 152.
The CPU 151 is a central processing unit, and performs various arithmetic processes based on data received from the load balancer 130, a program in the storage device 152, and the like.
The storage device 152 includes a memory, a RAM (Random Access Memory), a ROM (Read Only Memory), a hard disk, and the like, and stores various types of information. The storage device 152 stores an application server 153 that is a program.

The application server 153 includes an application program 155, an HTTP session information management unit 154, and an HTTP session ID 158 that holds HTTP session information 159.
The application program 155 is a program that processes requests from the client machines 110 to 112.

  The HTTP session information management unit 154 is a program for managing session information of HTTP (Hyper Text Transfer Protocol), and receives a request from a client and returns a response, creates an HTTP session ID, and creates HTTP session information for the HTTP session ID. Acquisition, deletion of an HTTP session ID and session information, processing request for a request to an application program and reception of a response return request from the application program, transfer of an HTTP session information update request and HTTP session information to another application server, A request for deleting an HTTP session ID and HTTP session information to another application server, and an update request and a deletion request from another application server are received.

The HTTP session information management unit 154 has an “importance definition” 156 that defines an attribute of importance in order to add importance to the HTTP session information when creating an HTTP session ID. This “importance level definition” 156 defines the same contents in all the application servers constituting the cluster.
In addition, when an HTTP session information update request and HTTP session information is transferred to another application server, and an HTTP session ID and HTTP session information deletion request is sent to another application server, the application that is the transmission destination of the request It has a “transfer destination definition” 157 that defines a server. This “definition of transfer destination” 157 defines a transfer destination for each application server constituting the cluster.

  In this embodiment, a program for causing each computer to function as the HTTP session information management unit is recorded on a recording medium such as a CD-ROM and stored in a magnetic disk or the like, and then loaded into a memory and executed. And The recording medium for recording the program may be a recording medium other than the CD-ROM. The program may be used by installing it from the recording medium into the information processing apparatus, or the program may be used by accessing the recording medium through a network.

  In addition, the computer stores a program for causing the computer to function as the HTTP session information management unit, a CPU that executes processing of an application program, an application server, and the like, and loads the program or temporarily stores data at the time of execution. In addition to a magnetic disk device that stores such programs and the session information, an input device that receives input of operation instructions and data, an output device that outputs various information, and communication that communicates with other computers Assume that hardware resources such as devices are provided.

  When a failure occurs in the application server, the session information management system 100 can continue the session even when the request distribution destination is changed by the load balancer 130 and the application server that processes the request is switched. Therefore, a copy of the HTTP session ID and HTTP session information is created on all application servers that constitute the cluster (S101).

<< Data structure >>
<Data structure of definition of importance level of HTTP session information>
Next, the data structure of the definition of the importance level of the HTTP session information used for creating the HTTP session ID in the HTTP session information management unit in FIG. 1 will be described with reference to FIG.

  FIG. 2 is a diagram showing a data configuration of the importance level definition 156 of the HTTP session information according to this embodiment. The key 201 indicates the type of information constituting the session information. The importance level 202 represents an attribute of the importance level of each piece of information represented as the key 201. There are two types of importance attributes, high and low.

  The attribute with high importance represents information with high importance in continuing the session. For example, when the information is deleted, such as login information, the information that requires the login operation again at the client, that is, when the information is deleted, the data from the client is required again. Session information.

  An attribute with a low importance represents information with a low importance in continuing the session. For example, database search results using login information, etc. Even if the information is deleted, if there is login information, the client is not affected and the search is performed again within the application server. Information that can be regenerated by the client, that is, session information that does not require data from the client again even if the information is deleted.

<Data structure of definition of transfer destination of HTTP session information>
Subsequently, the HTTP session information management unit in FIG. 1 updates the HTTP session information to another application server, transfers the HTTP session information, and deletes the HTTP session ID and the HTTP session information to the other application server. The data structure of the definition of the transfer destination of the HTTP session information used when making a request will be described with reference to FIG.

  FIG. 3 is a diagram showing a data configuration of the transfer destination definition 157 of the HTTP session information according to this embodiment. The server name 301 in FIG. 3A is the name of all application servers that constitute the cluster.

  The importance 302 of the HTTP session information to be transferred indicates the importance of the HTTP session information to be transferred when the HTTP session information update request and the HTTP session information are transferred to another application server. This indicates that HTTP session information with high and low importance is transferred to an application server with the importance 302 of the HTTP session information to be transferred being “high, low”. Further, it indicates that HTTP session information having a high importance level is transferred to an application server having a high importance level 302 of the HTTP session information to be transferred. Further, it indicates that HTTP session information is not transferred to an application server whose importance 302 of the transferred HTTP session information is “−”.

  The importance 302 of the HTTP session information to be transferred is defined as “high, low” for the application server that is the next delivery destination of the request when the application server is switched due to a failure or the like. This is defined for an application server that is set in advance in the load balancer 130 of FIG.

“High” in the importance 302 of the HTTP session information to be transferred is defined for the application server that defines “high, low” and the application servers other than its own application server.
“−” Of the importance 302 of the HTTP session information to be transferred is defined for the own application server.

  FIG. 3A shows the contents of the definition of the transfer destination of the HTTP session information in the HTTP session information management unit of the application server 1 of FIG. In the setting of the load balancer 130, the application server that is the next delivery destination of the request when a failure occurs in the application server 1 is “application server 2”. As a result, “high, low” is defined for the importance 302 of the HTTP session information transferred from the application server 1 to the application server 2 with the application server name 301.

  FIG. 3B shows the definition contents of the transfer destination of the HTTP session information in the HTTP session information management unit of the application server 2 of FIG. In the setting of the load balancer 130, the application server that is the next delivery destination of the request when a failure occurs in the application server 2 is “application server 3”. Thus, “high, low” is defined for the importance 304 of the HTTP session information transferred from the application server 2 to the application server 3 with the application server name 303.

<Data structure of HTTP session ID>
Next, the data structure of the HTTP session ID in the application server of FIG. 1 will be described with reference to FIG.

  FIG. 4 is a diagram illustrating a data configuration of the HTTP session ID according to the present embodiment. In FIG. 4, one session information includes five items of an HTTP session ID 401, an expiration date 402, a key 403, a value 404, and an importance 405.

  The HTTP session ID 401 is an identifier that uniquely identifies a session within the application server. The expiration date 402 is the expiration date of the session information. As described with reference to FIG. 2, the key 403 indicates the type of information constituting the session information, and is generated according to the contents of the request processing such as login processing and database search processing. To do. A value 404 is an actual value corresponding to the key 403. The importance 405 represents an attribute of importance to which each piece of information represented as the key 403 belongs. As the importance, the importance corresponding to the key 403 is set according to the definition of the importance of the HTTP session information in FIG.

<< Processing procedure >>
Subsequently, a specific processing procedure of the session information management system 100 will be described.
<HTTP session information replication processing>
FIG. 5 is a diagram showing a processing flow of HTTP session information duplication processing of this embodiment. First, HTTP session information duplication processing will be described in detail with reference to FIG. The HTTP session information duplication process is a process for duplicating the HTTP session information to another application server, and FIG. 5 is a flowchart of the process.

  In this case, the initial request from the client is delivered to the application server 1 (153) by the load balancer 130, or the initial request from the client is sent to the application server 1 (153 by the load balancer 130. ) Will be described as an example in which processing is started from a state in which the second and subsequent requests from the client are distributed to the application server 1 (153).

  First, the HTTP session information management unit 154 of the application server 1 (153) receives a request 1501 from the client (S501).

The HTTP session information management unit 154 creates an HTTP session ID 158 on the application server 1 when the HTTP session ID 1502 is not included in the request. In accordance with the contents of the definition of importance 156, an attribute of importance is added to each HTTP session information key in the HTTP session information 159 for the created HTTP session ID 158. If the HTTP session ID 1502 is included in the request, reference information (pointer) to the HTTP session ID 158 registered on the application server 1 for the HTTP session ID is acquired (S502).
Then, reference information for the created or acquired HTTP session ID is passed to the application program 155 to request processing for the request (S503).

The application program 155 that has received the request for processing the request performs processing for the request, and updates the content of the HTTP session information 159 by using the reference information to the HTTP session ID passed from the HTTP session information management unit 154 ( S504).
Then, a response response is requested to the HTTP session information management unit 154 (S505).

The HTTP session information management unit 154 that has received the response return request, in accordance with the contents of the transfer destination definition 157, the application server 2 (163) that is the next delivery destination of the request when a failure occurs in the application server 1 (153). The HTTP session information management unit 164 of () is requested to update HTTP session information with high and low importance (S506).
Then, HTTP session information with high and low importance is transferred to the HTTP session information management unit 164 of the application server 2 (163).

  The HTTP session information management unit 164 of the application server 2 (163) that has received the update request for HTTP session information with high and low importance receives the transferred HTTP session information with high and low importance and receives the received HTTP session information. Session information is registered on the application server 2 (163) (S507).

Next, in accordance with the contents of the transfer destination definition 157, the HTTP session information management unit 154 requests the HTTP session information management unit of the application servers 3 to n to update the HTTP session information with high importance.
Then, the HTTP session information with high importance is transferred to the HTTP session information management unit of the application servers 3 to n (S508).

  The HTTP session information management unit of the application servers 3 to n that has received the update request for the HTTP session information with the high importance receives the transferred HTTP session information with the high importance, and receives the received HTTP session information for each application. Registration on the server (S509).

  When the transfer of the HTTP session information to another application server is completed, the HTTP session information management unit 154 returns a response 1503 to the client (S510).

  This process requires the memory capacity for storing HTTP session information, the amount of communication for transferring the HTTP session information to other application servers, and the overhead required for such processing. Resources can be reduced.

<Processing when a failure occurs>
FIG. 6 is a diagram illustrating processing when a failure according to the present embodiment occurs. Next, a process when a failure occurs will be described in detail with reference to FIG. The processing when a failure occurs is processing when the request delivery destination is changed and the application server that processes the request is switched when a failure occurs in the application server. FIG. FIG.

  Here, an example will be described in which processing is started from a state where a failure has occurred in the application server 1 (153) when a request from a client is distributed to the application server 1 (153). .

  The request delivery destination is changed to the application server 2 (163) due to the occurrence of a failure in the application server 1 (153), and the request received by the HTTP session information management unit 154 of the application server 1 (153) is changed to the application server. 2 (163) is received by the HTTP session information management unit 164 (S601).

  The HTTP session information management unit 164 acquires reference information for the HTTP session ID 168 registered on the application server with respect to the HTTP session ID 1602 included in the request 1601 (S602).

Since the HTTP session information 169 registered in the reference information to the acquired HTTP session ID 168 has been transferred from the application server 1 (153), all the HTTP session information with high and low importance is transferred. All the HTTP session information with high and low importance can be read out by the storage device using, and the session can be continued using the read HTTP session information.
Then, reference information to the acquired HTTP session ID 168 is passed to the application program 165 to request processing for the request (S603).

The application program 165 that has received the processing request for the request performs the processing for the request, reads the HTTP session information 169 from the storage device using the reference information to the HTTP session ID 168 passed from the HTTP session information management unit 164, and HTTP The content of the session information 169 is updated (S604).
Then, a response response is requested to the HTTP session information management unit 164 (S605).

The HTTP session information management unit 164 that has received the response reply request, in accordance with the contents of the transfer destination definition 167, the application server 3 (173) that is the next delivery destination of the request when a failure occurs in the application server 2 (163). ) Of the HTTP session information management unit 174 of) is requested to update the HTTP session information with high and low importance (S606).
Then, HTTP session information with high and low importance is transferred to the HTTP session information management unit 174 of the application server 3 (173).

  The HTTP session information management unit 174 of the application server 3 (173) that has received the update request for HTTP session information with high and low importance receives the transferred HTTP session information with high and low importance and receives the received HTTP session information. Session information is registered on the application server 3 (S607).

Next, the HTTP session information management unit 164 updates the HTTP session information with high importance to the HTTP session information management units of the application server 1 and the application servers 4 to n according to the contents of the transfer destination definition 167. Request.
Then, the HTTP session information with high importance is transferred to the HTTP session information management unit of the application server 1 and the application servers 4 to n (S608).

  The HTTP session information management unit of the application server 1 and the application servers 4 to n receives the transferred HTTP session information having a high importance level, and registers the received HTTP session information on each application server (S609).

  When the transfer of the HTTP session information to another application server is completed, the HTTP session information management unit 164 returns a response 1603 to the client (S610).

<Processing when a double failure occurs>
FIG. 7 is a diagram showing processing when a double failure occurs according to the present embodiment. Next, a process when a double failure occurs will be described in detail with reference to FIG. When a double failure occurs, processing is performed simultaneously on two application servers: the application server that is receiving the request, and the application server that is the next delivery destination of the request when the failure occurs on that application server. Is a process when the request delivery destination is changed and the application server that processes the request is switched, and FIG. 7 is a process flow diagram thereof.

  Here, when a request from a client is distributed to the application server 1 (153), a failure occurs simultaneously in the two application servers, the application server 1 (153) and the application server 2 (163). An example in which processing is started from the above state will be described.

  Due to the occurrence of a failure in the application server 1 (153) and the application server 2 (163), the delivery destination of the request is changed to the application server 3 (173) and is received by the HTTP session information management unit 154 of the application server 1 (153). The received request is received by the HTTP session information management unit 174 of the application server 3 (173) (S701).

  The HTTP session information management unit 174 acquires reference information for the HTTP session ID 178 registered on the application server for the HTTP session ID 1702 included in the request 1701 (S702).

Since the HTTP session information 179 registered in the reference information to the acquired HTTP session ID 178 is transferred with high importance HTTP session information from the HTTP session information management unit 154 of the application server 1 (153). Using the reference information, HTTP session information with high importance is read from the storage device, and the session is continued using the HTTP session information.
Then, reference information to the acquired HTTP session ID 178 is passed to the application program 175 to request processing for the request (S703).

When the application program 175 that has received the processing request for the request requires HTTP session information of low importance that is not transferred from the HTTP session information management unit 154 of the application server 1 (153) in order to continue the session. Regenerates HTTP session information of low importance using HTTP session information of high importance.
Then, processing for the request is performed, and the content of the HTTP session information 179 is updated using the reference information to the HTTP session ID 178 passed from the HTTP session information management unit 174 (S704).
Then, a response response is requested to the HTTP session information management unit 174 (S705).

The HTTP session information management unit 174 that has received the response reply request, in accordance with the contents of the transfer destination definition 177, provides the HTTP of the application server 4 that is the next delivery destination of the request when a failure occurs in the application server 3 (173). The session information management unit is requested to update HTTP session information with high and low importance (S706).
Then, HTTP session information with high and low importance is transferred to the application server 4.

Next, the HTTP session information management unit 174 updates the HTTP session information with high importance to the HTTP session information management units of the application servers 1, 2, and 5 to n in accordance with the contents of the transfer destination definition 177. Request.
Then, the HTTP session information with high importance is transferred to the HTTP session information management units of the application servers 1, 2 and 5 to n (S707).

  The HTTP session information management units of the application servers 1, 2, and 5 to n that have received the update request for the HTTP session information with the high importance receive the transferred HTTP session information with the high importance, and the received HTTP session information Registration is performed on each application server (S708).

  When the transfer of the HTTP session information to another application server is completed, the HTTP session information management unit 174 returns a response 1703 to the client (S709).

<HTTP session information deletion process>
FIG. 8 is a diagram showing a processing flow of HTTP session information deletion processing according to this embodiment. Next, HTTP session information deletion processing will be described in detail with reference to FIG. The HTTP session information deletion process is performed when a request from a client is processed, when the end of the session is specified in the request, and when the expiration date of the session has expired. FIG. 8 is a flowchart of the process when deleting an ID and its HTTP session information.

  Here, an example is described in which processing is started from a state in which a request from a client is distributed to the application server 1 (153).

  First, the HTTP session information management unit 154 of the application server 1 (153) receives a request 1501 from the client (S801).

  The HTTP session information management unit 154 acquires reference information for the HTTP session ID 158 registered on the application server with respect to the HTTP session ID 1502 included in the request 1501 (S802).

Here, the expiration date set in the HTTP session ID is checked from the acquired reference information to the HTTP session ID 158. If the expiration date has passed, the HTTP session ID 158 on the application server 1 (153) and its The HTTP session information 159 is deleted.
Then, the HTTP session information management unit of all the application servers 2 to n except the self application server set in the transfer destination definition 157 is requested to delete the HTTP session ID (S806).

  The HTTP session information management unit of the application server 2 to n that has received the HTTP session ID deletion request deletes the HTTP session ID and the HTTP session information on the application server (S807).

  When deletion of the HTTP session IDs of the application servers 2 to n is completed, a response 1503 is returned to the client (S808).

  In S <b> 802, when the reference information for the HTTP session ID 158 is acquired, and the validity period set in the HTTP session ID is checked from the reference information for the HTTP session ID, the validity period of the HTTP session ID 158 has not passed. The HTTP session information management unit 154 requests the application program 155 to process the request, and updates the content of the HTTP session information 159. For the contents of this process, refer to (S503) to (S505) in FIG. 5 ((S803), (S804), (S805)).

  The HTTP session information management unit 154 that has received a response return request from the application program 155 transfers the updated HTTP session information 159 to another application server. For the contents of this process, refer to (S506) to (S509) in FIG. 5 ((S806), (S807)).

After completing the transfer of the HTTP session information to another application server, the HTTP session information management unit 154 checks whether an HTTP session ID deletion request is specified in the request, and deletes the HTTP session ID in the request. If the request is specified, the HTTP session ID 158 and the HTTP session information 159 on the application server 1 are deleted.
Then, the HTTP session information management unit 154 requests the HTTP session information management units of all the application servers 2 to n except the self application server set in the transfer destination definition 157 to delete the HTTP session ID. (S806).

The HTTP session information management unit of the application server 2 to n that has received the HTTP session ID deletion request deletes the HTTP session ID and the HTTP session information on the application server (S807).
Finally, a response 1503 is returned from the HTTP session information management unit 154 to the client (S808).

Next, a flowchart of the HTTP session information management unit will be described.
<Flowchart when a request is received from a client>
FIG. 9 is a flowchart showing a processing procedure of request reception processing of this embodiment. First, a flowchart when a request is received from a client by the HTTP session information management unit will be described with reference to FIG.

  The HTTP session information management unit that has received the request from the client by the communication apparatus determines whether the HTTP session ID is included in the request received from the client (step 901).

If the HTTP session ID is not included in the request, an HTTP session ID is created on the application server (step 902), and the HTTP session information in the created HTTP session ID is in accordance with the content of the definition of importance. An attribute of importance is added for each key of HTTP session information (step 903). That is, the definition of importance is read from the storage device, and a record having a key that matches the key of the HTTP session information in the created HTTP session ID is searched with the attribute of the importance, and the corresponding key is searched. The importance is acquired from the definition of importance, and the attribute of the acquired importance is added to the HTTP session information in the created HTTP session ID and stored in the storage device.
Then, the reference information to the created HTTP session ID is passed to the application program, and the processing for the request is requested (step 904).

  When the HTTP session ID is included in the request received from the client, reference information to the HTTP session ID registered on the application server for the HTTP session ID is acquired (step 905).

  From the reference information to the acquired HTTP session ID, it is determined whether or not the expiration date of the HTTP session ID has passed (step 906). If the expiration date has not passed, the application program refers to the created HTTP session ID. Information is passed to request processing for the request (step 904).

If the expiration date has passed, the HTTP session information and HTTP session ID on the application server are deleted from the storage device (step 907), and the own application server set in the transfer destination definition read from the storage device is excluded. The communication device requests all application servers to delete the HTTP session ID (step 908).
Then, the communication device returns a response indicating that the session has expired (step 909).

<Flowchart when response reply request is received from application program>
FIG. 10 is a flowchart showing the processing procedure of the response reply request receiving process of this embodiment. Next, a flowchart when the HTTP session information management unit receives a response return request from the application program will be described with reference to FIG.

The HTTP session information management unit that has received the response return request from the application program sends an HTTP session to the application server that is the transfer destination of high and low importance HTTP session information according to the contents of the transfer destination definition. An update of information is requested (step 1001). That is, the definition of the transfer destination is read out from the storage device, a record in which the importance of the HTTP session information to be transferred is high and low is searched from the definition of the transfer destination, and the server name corresponding to the importance is found in the transfer destination And requests the computer with the acquired server name to update the HTTP session information by the communication device.
Then, HTTP session information with high and low importance is transferred by the communication device to the application server that made the update request (step 1002).

Subsequently, in accordance with the contents of the definition of the transfer destination, the communication device requests the application server that is the transfer destination of the HTTP session information with high importance to update the HTTP session information (step 1003). That is, the definition of the transfer destination is read from the storage device, a record having a high importance level of the HTTP session information to be transferred is searched from the definition of the transfer destination, and the server name corresponding to the importance level is defined as the definition of the transfer destination. And requesting the computer having the acquired server name to update the HTTP session information by the communication device.
Then, the HTTP session information with high importance is transferred by the communication device to the application server that made the update request (step 1004).

  When transfer of the HTTP session information to another application server is completed, it is determined whether an HTTP session ID deletion request is specified in the request (step 1005).

  If an HTTP session ID deletion request is not specified in the request, the communication device returns a response to the client as it is (step 1006).

  If a request to delete an HTTP session ID is specified in the request, the HTTP session information and the HTTP session ID on the application server are deleted (step 1007), and the transfer destination definition read from the storage device is set. The communication device requests all application servers other than its own application server to delete the HTTP session ID (step 1008). After deleting the HTTP session ID of the other application server, the communication device returns a response to the client ( Step 1006).

<Flowchart when a request is received from the HTTP session information management unit of another application server>
FIG. 11 is a flowchart showing a processing procedure of other application server request reception processing of this embodiment. Next, a flowchart when the HTTP session information management unit receives a request from the HTTP session information management unit of another application server will be described with reference to FIG.

  The HTTP session information management unit that has received the request from the HTTP session information management unit of the other application server by the communication apparatus determines the content of the request (step 1101).

If the content of the request is an HTTP session ID update request, the HTTP session information management unit of the application server that made the update request sends HTTP session information with high and low importance or high importance to the communication device. (Step 1102).
The received HTTP session information is stored in the storage device and registered on the application server (step 1103).

  If the content of the request is an HTTP session ID deletion request, the HTTP session ID registered on the application server and the HTTP session information are deleted from the storage device for the HTTP session ID requested to be deleted (step 1105). ).

  When the update process or the delete process is completed, the communication apparatus notifies the HTTP session information management unit of the application server that made the request that the process for the update request or the delete request has been completed (step 1104).

  As described above, according to the session information management system of the present embodiment, session information is transferred to a transfer destination computer according to its importance and registered, so that the session information is maintained while maintaining the reliability of continuation of the session. It is possible to reduce resource consumption due to duplication.

It is a figure which shows the whole structure of the session information management system of this embodiment. It is a figure which shows the data structure of the definition 156 of the importance of the HTTP session information of this embodiment. It is a figure which shows the data structure of the definition 157 of the transfer destination of the HTTP session information of this embodiment. It is a figure which shows the data structure of HTTP session ID of this embodiment. It is a figure which shows the processing flow of the duplication process of the HTTP session information of this embodiment. It is a figure which shows a process when the failure of this embodiment generate | occur | produces. It is a figure which shows a process when the double failure generate | occur | produces of this embodiment. It is a figure which shows the processing flow of the deletion process of the HTTP session information of this embodiment. It is a flowchart which shows the process sequence of the request reception process of this embodiment. It is a flowchart which shows the process sequence of the response reply request reception process of this embodiment. It is a flowchart which shows the process sequence of the other application server request | requirement reception process of this embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 ... Session information management system, 110-112 ... Client machine, 120 ... Network, 130 ... Load balancer, 140 ... Communication line, 151 ... CPU, 152 ... Storage device, 153 ... Application server, 154 ... HTTP session information management part 155 ... application program, 156 ... definition of importance, 157 ... definition of transfer destination, 158 ... HTTP session ID, 159 ... HTTP session information, 201 ... key, 202 ... importance, 301 ... server name, 302 ... transfer Importance of HTTP session information, 303 ... Server name, 304 ... Importance of HTTP session information to be transferred, 401 ... HTTP session ID, 402 ... Expiration date, 403 ... Key, 404 ... Value, 405 ... Importance, 163 ... Application Server, 164 ... HTT Session information management unit, 173 ... application server, 174 ... HTTP session information management unit, 183 ... application server, 184 ... HTTP session information management unit, 1501 ... request, 1502 ... HTTP session ID, 1503 ... response, 165 ... application program, 166 ... Definition of importance, 167 ... Definition of transfer destination, 168 ... HTTP session ID, 169 ... HTTP session information, 1601 ... Request, 1602 ... HTTP session ID, 1603 ... Response, 175 ... Application program, 176 ... Importance of importance Definition, 177 ... Definition of transfer destination, 178 ... HTTP session ID, 179 ... HTTP session information, 1701 ... Request, 1702 ... HTTP session ID, 1703 ... Response.

Claims (10)

In a session information management method for storing and managing session information in a plurality of computers,
When a request is received from a computer on the client side, a definition of importance indicating the importance of session information is read out by a storage device, and an attribute of importance corresponding to the session information of the received request is defined as the definition of importance. Storing the attribute of the acquired importance level in the storage device by adding it to the session information of the received request;
The transfer destination definition indicating the computer that is the session information transfer destination is read from the storage device, information indicating the transfer destination computer is acquired from the transfer destination definition, and the acquired transfer destination computer corresponds to the computer. Transferring the session information of the importance level to be transmitted by the communication device;
Storing the transferred session information in a storage device of a transfer destination computer and registering the transferred session information.   When a computer is switched due to a failure and a request from the client side is processed by the switched computer, the session information transferred to the computer is read by the storage device and is important for the session of the request. When the session information with high importance and the session information with low importance are registered, the session information is continued using the session information with high importance and the session information with low importance. 1. The session information management method described in 1.   When a computer is switched due to a failure and a request from the client side is processed by the switched computer, the session information transferred to the computer is read by the storage device and is important for the session of the request. When only high-level session information is registered, the session is continued using the high-level importance session information and the session information generated by the computer. Session information management method.   The storage device deletes session information of a session whose end is specified from a computer on the client side or a session whose expiration date has expired, and a copy of the session information registered in the transfer destination computer. The session information management method according to any one of claims 1 to 3, further comprising a step of deleting.   5. The session information of all the importance levels is transferred by a communication device to a computer that is a next delivery destination of a request when a computer is switched due to a failure. 5. Session information management method.   The communication apparatus transfers only session information having a specific importance level to a computer other than a computer that is a next delivery destination of a request when a computer is switched due to a failure. Session information management method described in the section.   The session according to any one of claims 1 to 6, wherein the attribute of importance is set according to whether or not data from a computer on a client side is necessary session information. Information management method.   A high-importance attribute is added to session information in login operations that require data from a client-side computer, and a low-importance attribute is added to session information that indicates database search results that do not require data from a client-side computer. The session information management method according to claim 7, further comprising: In a session information management system that stores and manages session information in multiple computers,
When a request is received from a computer on the client side, a definition of importance indicating the importance of session information is read out by a storage device, and an attribute of importance corresponding to the session information of the received request is defined as the definition of importance. And the attribute of the obtained importance is added to the session information of the received request and stored in the storage device, and the definition of the transfer destination indicating the computer that is the transfer destination of the session information is read by the storage device, A first session information management unit for acquiring information indicating a transfer destination computer from the definition of the transfer destination, and transferring session information of importance corresponding to the computer to the acquired transfer destination computer by a communication device;
A session information management system comprising: a second session information management unit that stores and registers the transferred session information in a storage device of a transfer destination computer. In a program for causing a computer to execute a session information management method for storing and managing session information in a plurality of computers,
When a request is received from a computer on the client side, a definition of importance indicating the importance of session information is read out by a storage device, and an attribute of importance corresponding to the session information of the received request is defined as the definition of importance. Storing the attribute of the acquired importance level in the storage device by adding it to the session information of the received request;
The transfer destination definition indicating the computer that is the session information transfer destination is read from the storage device, information indicating the transfer destination computer is acquired from the transfer destination definition, and the acquired transfer destination computer corresponds to the computer. Transferring the session information of the importance level to be transmitted by the communication device;
A program for causing a computer to execute the step of storing and registering the transferred session information in a storage device of a transfer destination computer.

Images