CN105357222B - A kind of distribution Session management middleware - Google Patents

Abstract

This application discloses a distributed session management middleware, including a session lifecycle management module and a session memory; the session lifecycle management module is used when the session request sent by the user to the server cluster system through the browser is the first session request , create the Session information corresponding to this session request, and send the Session information to the Session memory; the Session memory is used to store the Session information sent by the Session life cycle management module each time, and when a new node server is added When entering the server cluster system, send all the session information stored by itself to the new node server through the central node server. This application improves the management efficiency of Session information and avoids a large amount of information synchronization.

Description

A Distributed Session Management Middleware

technical field

The invention relates to the technical field of session management, in particular to a distributed session management middleware.

Background technique

With the development of the Internet, people require the server system to have higher performance and stability, which makes the server cluster system more and more widely used, and the Session management mode in the server cluster system has gradually changed from a stand-alone management mode to a The expansion of the cluster management mode, and the synchronization and storage of Session among cluster nodes have become its core technical issues.

At present, the synchronization of sessions based on Tomcat or WebLogic middleware adopts the multicast method, and session replication is performed on each cluster node, which requires a large amount of session information to be replicated. After the number of users and the number of clusters reach a certain scale, The copy operation of Session information becomes the performance bottleneck of the system, thereby reducing the management efficiency of Session information.

From the above, it can be seen that how to improve the management efficiency of Session information and avoid the synchronization of a large amount of information is an urgent problem to be solved at present.

Contents of the invention

In view of this, the object of the present invention is to provide a distributed session management middleware, which improves the management efficiency of session information and avoids the synchronization of a large amount of information. The specific plan is as follows:

A distributed session management middleware, applied to a server cluster system, the server cluster system includes N node servers, N is a positive integer, wherein, the N node servers include a central node server; the distributed The session management middleware includes session life cycle management module and session storage; among them,

The Session lifecycle management module is used to create session information corresponding to this session request when the session request sent by the user to the server cluster system through the browser is the first session request, and send the Session information to To the Session memory; when the session request sent by the user to the server cluster system through the browser is not the first session request, read the first session request sent by the user through the current browser from the Session memory Corresponding Session information;

The Session memory is used to store the Session information sent by the Session lifecycle management module each time, and when a new node server is added to the server cluster system, through the central node server, the Send all the Session information stored by itself to the new node server.

Preferably, the Session memory includes a Session buffer pool and a MongoDB database; wherein,

The Session buffer pool is used for caching the Session information after receiving the Session information sent by the Session life cycle management module each time, and forwarding the Session information to the MongoDB database;

The MongoDB database is used for persistently storing the Session information after receiving the Session information sent by the Session buffer pool each time, and when a new node server is added to the server cluster system, Send all the Session information stored by itself to the new node server through the central node server.

Preferably, the central node server includes:

An instruction receiving unit, configured to obtain the Session information request instruction sent by the new node server when a new node server is added to the server cluster system;

The information transmission unit is configured to transmit all the Session information stored in the MongoDB database to the new node server when the instruction receiving unit receives the Session information request instruction.

Preferably, the Session lifecycle management module includes:

The request interception unit is used to intercept the current session request sent by the user to the server cluster system through the browser;

Request judging unit, for judging whether the current session request intercepted by the request interception unit carries SessionID, if not, then judging that this session request is the first session request, if yes, then judging that this session request is not the first session ask;

The Session creating unit is used to create the Session information corresponding to the session request when the session request does not carry the SessionID, and send the Session information to the Session buffer pool, wherein each Session information includes its corresponding sessionID;

The Session reading unit is used to determine whether the Session information corresponding to the SessionID is stored in the current Session buffer pool by utilizing the SessionID when the current session request carries the SessionID, and if so, from the Session buffer pool Read out the Session information corresponding to the SessionID, if not, then read the Session information corresponding to the SessionID from the MongoDB database.

Preferably, the distributed session management middleware also includes a timeout session destruction module, wherein,

The overtime Session destruction module is used to judge whether each Session information in the Session buffer pool is overtime, and when it is judged that any Session information in the Session buffer pool is overtime, the Session information is destroyed;

The Session buffer pool is also used to send corresponding instructions to the MongoDB database when the overtime Session destruction module destroys any Session information in the Session buffer pool to notify the MongoDB database to The corresponding Session information is destroyed.

Preferably, the overtime Session destruction module includes:

The overtime monitoring unit is used to scan each Session information in the Session buffer pool, and calculate the time difference between the current moment and the time of the last session request corresponding to each Session information, and determine the corresponding session information of each Session information. Whether the time difference is greater than or equal to the preset value;

Destruction instruction sending unit, used to send the Session destruction instruction corresponding to the Session information to the Session buffer pool when the timeout monitoring unit judges that the time difference corresponding to any Session information is greater than or equal to the preset value, so that The Session buffer pool destroys the corresponding Session information according to the Session destruction instruction.

Preferably, the distributed session management middleware also includes:

The session attribute updating unit is used for updating the attribute of the corresponding Session information in the Session buffer pool and the MongoDB database simultaneously when the attribute of any created Session information needs to be updated.

Preferably, the distributed session management middleware also includes:

The session time changing unit is configured to change only the session time of the corresponding Session information in the Session buffer pool when the session time of any created Session information needs to be changed.

Preferably, the distributed session management middleware also includes:

The Session monitoring module is used to monitor the quantity of the Session information in the Session buffer pool and the occupied memory situation, and monitor the running status of the MongoDB database.

Preferably, the distributed session management middleware also includes:

The MongoDB replica set is used for backing up the data stored in the MongoDB database.

In the present invention, the distributed Session management middleware includes a Session lifecycle management module and a Session memory; wherein, the Session lifecycle management module is used for when the session request sent by the user to the server cluster system through the browser is the first session request, Create the Session information corresponding to this session request, and send the Session information to the Session memory; the Session memory is used to store the Session information sent by the Session lifecycle management module each time, and when a new node server is added to When the server is in a cluster system, send all the session information stored by itself to the new node server through the central node server. It can be seen that in the present invention, when the user sends the first session request to the server cluster system through the browser, the corresponding Session information is created by the Session life cycle management module, and the Session information created by the Session life cycle management module is stored by the Session memory , when a new node server is added to the server cluster system, all the Session information stored in the Session memory can be sent to the new node server through the central node server, which is equivalent to storing all the Session information in the Session memory information, when it is necessary to synchronize Session information to a new node server, it is only necessary to send the Session information stored in the Session memory to the new node server through the central node server, thus avoiding the problem of using multicast in the prior art Synchronization of session information in a different way causes the problem that a large amount of information needs to be synchronized, thereby improving the management efficiency of session information.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

Fig. 1 is a schematic diagram of a distributed session management middleware application structure disclosed by an embodiment of the present invention;

FIG. 2 is a schematic diagram of a specific distributed session management middleware application structure disclosed by an embodiment of the present invention;

FIG. 3 is a schematic diagram of another specific distributed session management middleware application structure disclosed by the embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

The embodiment of the present invention discloses a distributed session management middleware, which is applied to a server cluster system. The server cluster system includes N node servers, where N is a positive integer, wherein the above N node servers include a central node server; Referring to Fig. 1, in the present embodiment, the distributed Session management middleware includes a Session lifecycle management module 11 and a Session memory 12; wherein,

Session lifecycle management module 11 is used to create session information corresponding to this session request when the session request sent by the user to the above-mentioned server cluster system through the browser is the first session request, and send the Session information to the Session Memory 12; when the session request sent by the user to the above-mentioned server cluster system through the browser is not the first session request, read out from the Session memory 12 the Session information corresponding to the first session request sent by the user through the current browser ;

Session memory 12 is used to store the Session information sent by the Session life cycle management module 11 each time, and when a new node server is added to the above-mentioned server cluster system, through the central node server of the above-mentioned server cluster system, the All the session information stored by itself is sent to the above new node server.

In the embodiment of the present invention, the distributed session management middleware includes a session lifecycle management module and a session memory; wherein, the session lifecycle management module is used for the first session request when the session request sent by the user to the server cluster system through the browser , create the Session information corresponding to this session request, and send the Session information to the Session memory; the Session memory is used to store the Session information sent by the Session life cycle management module each time, and when a new node server is When added to the server cluster system, all the session information stored by itself will be sent to the new node server through the central node server.

It can be seen that in the embodiment of the present invention, when the user sends the first session request to the server cluster system through the browser, the corresponding Session information is created by the Session life cycle management module, and the Session information created by the Session life cycle management module is passed through the Session memory. When a new node server is added to the server cluster system, all the Session information stored in the Session memory can be sent to the new node server through the central node server, which is equivalent to storing all the session information in the Session memory. Session information, when it is necessary to synchronize the Session information to a new node server, it is only necessary to send the Session information stored in the Session memory to the new node server through the central node server, thereby avoiding the use of Synchronization of session information in a multicast manner causes the problem that a large amount of information needs to be synchronized, thereby improving the management efficiency of session information.

The embodiment of the present invention also discloses a specific distributed session management middleware. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. specific:

Referring to Fig. 2, the Session memory 12 in this embodiment specifically includes a Session buffer pool 121 and a MongoDB database 122; wherein,

The Session buffer pool 121 can be used to cache the Session information after receiving the Session information sent by the Session life cycle management module 11 each time, and forward the Session information to the MongoDB database 122;

The MongoDB database 122 can be used to persistently store the Session information after receiving the Session information sent by the Session buffer pool 121 each time, and when a new node server is added to the server cluster system, through the server cluster system The central node server sends all the session information stored by itself to the above-mentioned new node server.

In this embodiment, since the MongoDB database has access speed, insertion speed and read speed compared with other types of databases, the synchronization speed and storage speed of Session information are greatly improved.

In addition, in this embodiment, the central node server of the server cluster system may include an instruction receiving unit and an information transmission unit, wherein,

The instruction receiving unit can be used to obtain the Session information request instruction sent by the above-mentioned new node server when a new node server is added to the server cluster system;

The information transmission unit may be configured to transmit all the Session information stored in the MongoDB database 122 to the above-mentioned new node server when the instruction receiving unit receives the Session information request instruction.

In this embodiment, the Session lifecycle management module 11 may specifically include a request interception unit 111, a request judgment unit 112, a Session creation unit 113, and a Session reading unit 114; wherein,

The request interception unit 111 can be used to intercept the current session request sent by the user to the server cluster system through the browser;

The request judgment unit 112 can be used to judge whether the session request intercepted by the request interception unit 111 carries the SessionID, if not, then determine that the session request is the first session request, and if so, determine that the session request is not the first session request ;

Session creation unit 113 can be used for when this session request does not carry SessionID, create the Session information corresponding to this session request, and send this Session information to Session buffer pool 121, wherein, each Session information all includes its corresponding SessionID;

Session reading unit 114 can be used for when this session request carries SessionID, utilizes this SessionID, determines whether to store the Session information corresponding to this SessionID in the current Session buffer pool 121, if yes, then reads from Session buffer pool 121 Take out the Session information corresponding to the SessionID, if not, read the Session information corresponding to the SessionID from the MongoDB database 122 . It can be seen that in this embodiment, when it is necessary to read the corresponding Session information from the Session memory 12, try to choose to read from the Session buffer pool 121, only when there is no relevant Session information in the Session buffer pool 121, select Read from the MongoDB database 122, thereby greatly reducing the number of times to read the MongoDB database 122, reducing the daily burden of the MongoDB database 122.

Referring to shown in Fig. 3, in the present embodiment, the distributed Session management middleware can also further include an overtime Session destruction module 13, which is used to judge whether each Session information of the Session buffer pool 121 is timed out, and when it is judged that the Session buffer pool After any session information of 121 times out, the session information is destroyed.

Correspondingly, the Session buffer pool 121 can also be used to send corresponding instructions to the MongoDB database 122 after the overtime Session destruction module 13 destroys any Session information in the Session buffer pool 121, to notify the MongoDB database 122 to perform corresponding Session information The destruction process is to notify the MongoDB database 122 to destroy the Session information stored in itself corresponding to the Session information destroyed in the Session buffer pool 121 .

Specifically, the above-mentioned overtime Session destruction module 13 may include a timeout monitoring unit 131 and a destruction instruction sending unit 132; wherein,

The timeout monitoring unit 131 can be used to scan each Session information in the Session buffer pool 121, and calculate the time difference between the current time and the time of the last session request corresponding to each Session information, and determine the time difference corresponding to each Session information Whether it is greater than or equal to a preset value, wherein the last session request corresponding to any Session information is the latest session request among all session requests currently corresponding to the Session information;

Destruction instruction sending unit 132 can be used for when timeout monitoring unit 131 judges that the time difference corresponding to any Session information is greater than or equal to preset value, sends the Session destruction instruction corresponding to this Session information to Session buffer pool 121, so that Session buffer pool 121 The corresponding Session information is destroyed according to the Session destruction instruction.

Further, in this embodiment, the distributed session management middleware also includes a session attribute updating unit, a session session time changing unit, and/or a session monitoring module; wherein,

The session attribute update unit can be used to update the attributes of the corresponding Session information in the Session buffer pool 121 and the MongoDB database 122 at the same time when the attribute of any created Session information needs to be updated.

The session time changing unit can be used to only change the session time of the corresponding session information in the session buffer pool 121 when the session time of any created session information needs to be changed. It should be noted that, in the process of a large number of daily session requests, usually only the session time change operation of the Session information is involved, and the creation, attribute change and destruction operations of the Session information are seldom involved. In this embodiment, When the Session session time change unit needs to change the session time of the Session information, only the session time of the corresponding Session information in the Session buffer pool 121 is changed, and the session time of the corresponding Session information in the MongoDB database 122 is not changed , thereby greatly reducing the number of daily operations on the MongoDB database 122 and reducing the daily burden on the MongoDB database 122 .

The Session monitoring module can be used to monitor the number of Session information in the Session buffer pool 121 and the memory usage, and monitor the running status of the MongoDB database 122 .

In order to improve the continuous and reliable operation of the database, the distributed Session management middleware in the present embodiment can further include: a MongoDB replica set, which is used to backup the data stored in the MongoDB database 122. When the MongoDB database 122 fails, The MongoDB replica set can be used to take over the work of the MongoDB database 122, thereby improving the reliability of the system.

Finally, it should also be noted that in this document, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements not only includes those elements, but also other elements not expressly listed, or elements inherent in the process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

The above is a detailed introduction to a distributed session management middleware provided by the present invention. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only used to help understand the present invention. method and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and application scope. Invention Limitations.

Claims (10)

1. A distributed Session management middleware is characterized in that the distributed Session management middleware is applied to a server cluster system, wherein the server cluster system comprises N node servers, N is a positive integer, wherein the N node servers comprise a central node server; the distributed Session management middleware comprises a Session life cycle management module and a Session memorizer; wherein,

the Session life cycle management module is used for creating Session information corresponding to the Session request when the Session request sent to the server cluster system by the user through the browser is a first Session request, and sending the Session information to the Session memory; when the Session request sent to the server cluster system by a user through a browser is not a first Session request, reading Session information corresponding to the first Session request sent by the user through the current browser from a Session memory;

the Session memory is used for storing the Session information sent by the Session life cycle management module each time, and when a new node server is added into the server cluster system, all the Session information stored by the central node server is sent to the new node server through the central node server.

2. The distributed Session management middleware of claim 1 wherein the Session store comprises a Session buffer pool and a MongoDB database; wherein,

the Session buffer pool is used for caching the Session information after receiving the Session information sent by the Session life cycle management module each time, and forwarding the Session information to the MongoDB database;

and the MongoDB is used for persistently storing the Session information after the Session information sent by the Session buffer pool is received each time, and issuing all the Session information stored by the MongoDB to a new node server through the central node server when the new node server is added into the server cluster system.

3. The distributed Session management middleware of claim 2, wherein the central node server comprises:

the instruction receiving unit is used for acquiring a Session information request instruction sent by a new node server when the new node server is added into the server cluster system;

and the information transmission unit is used for transmitting all the Session information stored in the MongoDB database to the new node server when the instruction receiving unit receives the Session information request instruction.

4. The distributed Session management middleware of claim 3, wherein the Session lifecycle management module comprises:

the request intercepting unit is used for intercepting the session request sent by the user to the server cluster system through the browser;

the request judging unit is used for judging whether the session request intercepted by the request intercepting unit carries the Session ID or not, if not, the session request is judged to be a first session request, and if so, the session request is judged not to be the first session request;

a Session creating unit, configured to create Session information corresponding to the Session request when the Session request does not carry a Session id, and send the Session information to the Session buffer pool, where each Session information includes a Session id corresponding to the Session information;

and the Session reading unit is used for determining whether Session information corresponding to the Session ID is stored in the Session buffer pool or not by using the Session ID when the Session request carries the Session ID, reading the Session information corresponding to the Session ID from the Session buffer pool if the Session information is stored in the Session buffer pool, and reading the Session information corresponding to the Session ID from the MongoDB database if the Session information is not stored in the Session buffer pool.

5. The distributed Session management middleware of claim 4, further comprising a timeout Session destruction module, wherein,

the Session destroying module is used for judging whether each Session information in the Session buffer pool is overtime, and destroying the Session information when any Session information in the Session buffer pool is judged to be overtime;

the Session buffer pool is further configured to send a corresponding instruction to the montgodb database to notify the montgodb database of performing destruction processing on the corresponding Session information after the timeout Session destruction module destroys any Session information in the Session buffer pool.

6. The distributed Session management middleware of claim 5, wherein the timeout Session destruction module comprises:

the timeout monitoring unit is used for scanning each Session information in the Session buffer pool, calculating the time difference between the current time and the time of the last Session request corresponding to each Session information, and judging whether the time difference corresponding to each Session information is greater than or equal to a preset value;

and the destruction instruction sending unit is used for sending a Session destruction instruction corresponding to the Session information to the Session buffer pool when the overtime monitoring unit judges that the time difference corresponding to any Session information is greater than or equal to the preset value, so that the Session buffer pool can process the corresponding Session information according to the Session destruction instruction.

7. The distributed Session management middleware of claim 6, further comprising:

and the Session attribute updating unit is used for updating the attributes of the Session information corresponding to the Session buffer pool and the MongoDB database when the attributes of any created Session information need to be updated.

8. The distributed Session management middleware of claim 7, further comprising:

and the Session time changing unit is used for changing the Session time of the corresponding Session information in the Session buffer pool only when the Session time of any created Session information needs to be changed.

9. The distributed Session management middleware of claim 8, further comprising:

and the Session monitoring module is used for monitoring the number of Session information in the Session buffer pool and the memory occupation condition and monitoring the running state of the MongoDB database.

10. The distributed Session management middleware of any of claims 2 to 9, further comprising:

and the MongoDB copy set is used for carrying out backup processing on the data stored in the MongoDB database.