CN104753987B - A kind of distributed conversation management method and system - Google Patents
A kind of distributed conversation management method and system Download PDFInfo
- Publication number
- CN104753987B CN104753987B CN201310740730.0A CN201310740730A CN104753987B CN 104753987 B CN104753987 B CN 104753987B CN 201310740730 A CN201310740730 A CN 201310740730A CN 104753987 B CN104753987 B CN 104753987B
- Authority
- CN
- China
- Prior art keywords
- session
- data
- access request
- backup server
- terminal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 26
- 238000000034 method Methods 0.000 claims description 15
- 230000000052 comparative effect Effects 0.000 claims description 11
- 241001269238 Data Species 0.000 claims description 3
- 230000006835 compression Effects 0.000 claims description 3
- 238000007906 compression Methods 0.000 claims description 3
- 230000006837 decompression Effects 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 3
- 239000004744 fabric Substances 0.000 claims description 2
- PXFBZOLANLWPMH-UHFFFAOYSA-N 16-Epiaffinine Natural products C1C(C2=CC=CC=C2N2)=C2C(=O)CC2C(=CC)CN(C)C1C2CO PXFBZOLANLWPMH-UHFFFAOYSA-N 0.000 abstract description 6
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000004321 preservation Methods 0.000 description 2
- 230000018199 S phase Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 235000013399 edible fruits Nutrition 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Computer And Data Communications (AREA)
Abstract
The present invention provides a kind of distributed conversation management method and systems, comprising: judges whether the current sessions data of terminal access request need to back up;If necessary to back up, then the session backup server requests distributed lock corresponding with the terminal into session backup server cluster;After obtaining distributed lock, the session data of the terminal of the session backup server storage is updated using the current sessions data;Updated session data is backuped to other session backup servers in session backup server cluster.The present invention is by backing up session data, and the application for adding distributed lock can make application server both can guarantee session data consistency under non-affine mode, while improve the availability of session data.
Description
Technical field
The present invention relates to technical field of the computer network more particularly to a kind of distributed conversation management methods and system.
Background technique
In computer major term, session (session) refers to that a terminal user and interactive system carry out communication period
Between status information be often referred to enter system to the status information logged off system from registration.Simultaneously because webpage is one
The stateless linker of kind, application server needs to learn the browse state of user by session, so some user's phases
The information of pass is also saved in session.
The information industry of today's society develops rapidly, and many enterprise-level applications, which all suffer from, largely concurrently to be accessed, simultaneously
It is also required to stronger stability, an application server is no longer satisfied the needs of application, and needs to increase more services
Device.At this moment it just needs to dispose the application server for using two or more, externally provides service as a cluster.It is taken using application
Business device cluster then generally can all use load balancing, and many enterprises can be set as the configuration of load balancing non-affine mould
Non- viscous (Non-sticky Session) mode of formula, i.e. session, the effect of this mode is can be uniform point request
It is scattered on each node of application server cluster.
In Java EE application server cluster, the management of session can be more complicated, because to guarantee certain in cluster
After one node failure, session data can be obtained by other nodes so that other nodes take over failure node, realize cluster
It is fault-tolerant.Past technology has plenty of using memory replicanism, and this mode reaches certain in number of users and number of clusters
After scale, server performance will decline to a great extent, undesirable.It is using session shared mechanism, i.e. handle there are also a kind of mode
Session data backed up in synchronization is to cache server, and to improve the availability of session, but the prior art is either increased income
It is also that the implementation of non-open source all not can guarantee the data consistency under non-affine mode.Especially when user terminal simultaneously to
When two Java EE application servers initiate the request to same session, session data just will appear inconsistent.
Summary of the invention
The technical problem to be solved by the present invention is to how to guarantee user session data consistency under non-affine mode,
And improve session data availability.
In order to solve the above technical problems, the invention proposes a kind of distributed conversation management methods, comprising the following steps:
Judge whether the current sessions data of terminal access request need to back up;
If necessary to back up, then into session backup server cluster, session backup server corresponding with the terminal is asked
Seek distributed lock;
After obtaining distributed lock, updated described in the session backup server storage using the current sessions data
The session data of terminal;
Updated session data is backuped to other session backup servers in session backup server cluster.
Further it is proposed that another distributed conversation management method, comprising the following steps:
Receive terminal access request;
The session backup server requests distributed lock corresponding with the terminal into session backup server cluster;
When completing this session request, judge whether the current sessions data of terminal access request need to back up;
It such as needs to back up, then updates the terminal of the session backup server storage using the current sessions data
Session data;
Updated session data is backuped to other session backup servers in session backup server cluster.
Further, whether the current sessions data for judging terminal access request need to back up, and specifically include:
Judge whether the current sessions data are newly generated session datas:
If it is, the current sessions data of the access request need to back up;If it is not, then further described in judgement
Whether the current sessions data of access request are different from the session data of first access request, and the access is asked if different
The current sessions data asked need to back up;
When terminal access request is nullifies session request, then the current sessions data of the request need to back up;
When the session data of first access request is expired, then the current sessions data of the access request need to back up.
Further, which is characterized in that the session backup corresponding with the terminal into session backup server cluster
Server requests distributed lock, specifically includes:
Session backup server corresponding with the terminal is searched in the session backup server cluster;
Distributed lock request message is sent to the session backup server.
Further, the terminal that session backup server storage is updated using the current sessions data
Session data specifically includes:
Obtain the session data of the first access request of the terminal stored in the session backup server;
Compare the consistency of the session data of the current sessions data and the first access request;
If consistent, session backup server is written into the current sessions data;
If inconsistent, merge the session data of the current sessions data and the first access request, after merging
Session data be written session backup server.
Further, in the session of the first access request of the terminal for obtaining and being stored in the session backup server
After data, further includes:
Unserializing decompression is carried out to the session data of the first access request.
Further, before session backup server is written in the session data of the current access request, further includes:
Serializing compression is carried out to the session data of the current access request.
In addition, the present invention also provides a kind of distributed conversation management systems, comprising: judgment module, request module, update
Module and backup module;
Judgment module, for judging whether the current sessions data of terminal access request need to back up;
Request module, for when the judging result of the judgment module be need to back up when, to session backup server collection
Session backup server requests distributed lock corresponding with the terminal in group;
Update module updates the session using the current sessions data and backs up after getting distributed lock
The session data of the terminal of server storage;
Backup module, it is standby for updated session data to be backuped to other sessions in session backup server cluster
Part server.
Further, the judgment module includes: that the first judging submodule, second judgment submodule and third judge submodule
Block,
First judging submodule, for judging whether the current sessions data of terminal access request are newly generated session number
According to if it is, the current sessions data of the access request need to back up;If it is not, then further judging the access
Whether the current sessions data of request are different from the session data of first access request, if it is different, then the access request
Current sessions data need to back up.
Second judgment submodule, for judging whether terminal access request is to nullify session request, when terminal access is requested
When to nullify session request, the current sessions data of the access request need to back up;
Third judging submodule, whether the session data for judging the first access request is expired, when described first
When the session data of access request is expired, the current sessions data of the access request need to back up.
Further, the update module include: acquisition submodule, Comparative sub-module, first write-in submodule and second write
Enter submodule,
Acquisition submodule, for obtaining the meeting of the first access request of the terminal stored in the session backup server
Talk about data;It is also used to obtain distributed lock according to distributed lock response message;
Comparative sub-module, it is consistent with the session data of the first access request for the current sessions data
Property;
First write-in submodule, for when the comparison result of the Comparative sub-module is consistent, by this access request
Session backup server is written in session data;
Second write-in submodule, for merging the current meeting when the comparison result of the Comparative sub-module is inconsistent
Session backup server is written in session data after merging by the session data for talking about data and the first access request.
By using a kind of distributed conversation management method disclosed in this invention and system, so that application server is non-
Not only it can guarantee session data consistency under affine mode, but also session data availability can be improved.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of invention for those of ordinary skill in the art without creative efforts, can be with
It obtains other drawings based on these drawings.
Fig. 1: being a kind of flow chart of distributed conversation management method in the embodiment of the present invention one;
Fig. 2: being a kind of flow chart of distributed conversation management method in the embodiment of the present invention two;
Fig. 3: being a kind of module map of distributed conversation management system in the embodiment of the present invention three.
Specific embodiment
Below in conjunction with attached drawing of the invention, technical scheme in the embodiment of the invention is clearly and completely described,
Obviously described embodiments are some of the embodiments of the present invention, instead of all the embodiments.Based on the implementation in the present invention
Example, every other embodiment obtained by those of ordinary skill in the art without making creative efforts belong to
The scope of protection of the invention.
In the present invention, when user terminal initiates access request, the session storage management in application server is read
Preset configuration item, configuration item content are that individual event selection uses Pessimistic Locking conversation managing method or optimistic locking conversation managing method.
A kind of distributed conversation management method is proposed in the embodiment of the present invention one, as shown in Figure 1, comprising the following steps:
Step S101, judges whether the current sessions data of terminal access request need to back up;
If necessary to back up, then step S1021 is carried out, if it is not required, then carrying out step S1022;
Step S1021, the session backup server requests corresponding with the terminal point into session backup server cluster
Cloth lock;
Step S1022 terminates;
Step S103 after obtaining distributed lock, updates the session backup server using the current sessions data
The session data of the terminal of storage;
Updated session data is backuped to the backup clothes of other sessions in session backup server cluster by step S104
Business device.
The above method be optimistic locking implementation, be exactly web application handle request after, backup session this
Add distributed lock in a operation, used the session data with version, it will be able to which guarantee can be distinguished correctly in current memory
Whether the session data of preservation fails, and ensure that the basic consistency of session data.
The embodiment of the present invention two also proposed another distributed conversation management method, as shown in Fig. 2, including following step
It is rapid:
Step S201 receives terminal access request;
Step S202, the session backup server requests distribution corresponding with the terminal into session backup server cluster
Formula lock;
Step S203 judges whether the current sessions data of terminal access request need when completing this session request
Backup;
Step S204 such as needs to back up, then carries out step S2041, do not need such as, then carries out step S2042;
Step S2041 updates the terminal of the session backup server storage using the current sessions data
Session data;
Step S2042 terminates;
Updated session data is backuped to the backup clothes of other sessions in session backup server cluster by step S205
Business device.
The above method is the implementation method of Pessimistic Locking, is able to achieve session data in the operation cycle of entire session data
It is exclusive, same session data is caused to cover so as to avoid nodes different under non-affine mode, has reached session data
Strong consistency.
The distributed conversation management method proposed in the embodiment of the present invention apply provide web page service several
Java EE application server side, for managing the session data session in the affiliated memory of Java EE application server, and
Operation requests are initiated to session backup server cluster as needed;Session backup server cluster, for backing up session number
According to can guarantee that data possess high reliability.
In the embodiment of the present invention, multiple application servers can be existed simultaneously, the application server can be Java EE
Application server, or the corresponding other application server of function.
Several Java EE application servers initiate the write-in of session data to session backup server cluster in the present invention
When request, corresponding session backup server can receive corresponding session data in session backup server cluster, in preservation
It states session data simultaneously, then backs up n parts into session backup server cluster in other session backup servers.If in this way
Java EE application server breaks down and session data is caused to be lost, and can get from corresponding backup server cluster
Session data is simultaneously restored in Java EE application server memory;If Java EE application server and a session backup clothes
Business device have failed simultaneously, can get the backup of session data from other session backup servers also to restore number
According to.To greatly improve the availability of session data.
Further, whether the current sessions data for judging terminal access request need to back up, and specifically include:
Step S301 judges whether the current sessions data are newly generated session datas:
If it is, the current sessions data of the access request need to back up;
If it is not, then carrying out step S302;
Not whether the session data of step S302, the current sessions data for judging the access request and first access request
Together, the current sessions data of the access request need to back up if different;
Step S303 judges whether terminal access request is to nullify session request, when terminal access request is cancellation session
When request, then the current sessions data of the request need to back up;
Step S304 judges whether the session data of first access request is expired, when the session data of first access request
When expired, then the current sessions data of the access request need to back up.
In network application, each request of the user to the web application in Java EE application server all may shadow
It rings and arrives session data.Application server judges whether to need to back up according to the variation of session data, is broadly divided into following three kinds of feelings
Condition:
When newly creation session data, then the current sessions data of the access request need to back up.Usually current
When user and web application establish connection for the first time.As long as newly creating session data, then determine that the session data needs to back up.
And when the session data of the first access request and current sessions data difference, then the access request is current
Session data needs to back up;Specifically, after having created session data, and session data be normally it is no expired or
In the case where failure, again the same session data is initiated to request, it is possible to modify session data.It is corresponding in request
After web application is processed, check whether session data is modified, if be modified, current this part of modified session
Data need to back up;When the storage state message is expired, then the session data of the current access request needs to back up;
Specifically, then determining that session data needs are disposed from backup when time is up for the life cycle of session data itself.
The session backup server requests distributed lock corresponding with the terminal into session backup server cluster,
It specifically includes:
Step S401 searches session backup services corresponding with the terminal in the session backup server cluster
Device;
Step S402, Xiang Suoshu session backup server sends distributed lock request message
After session backup server cluster receives distributed lock request message, this request can be assigned to terminal sheet
On the corresponding session backup server of the session data of secondary operation, connect by the data spot lock management device in the session backup server
Request is received, and is handled.
The specific processing mode of data spot lock management device is, using the data storage device in session backup server to same
The mechanism of the 2nd write-in failure of one key, to determine whether can be written into lock object to realize distribution by the way of CAS
The effect of lock, if lock cannot be obtained, is always maintained at trial and obtains the distribution to judge this whether available lock
The state of lock, until getting the distributed lock.It is current to send out in the state that this holding is attempted to obtain distributed lock
The thread for playing the Java EE application server of request also one can be in blocked state together.
Once this request has arrived distributed lock, if other request application be the same data distribution
Lock, then before this request discharges the lock, can all obtain failure, hence into blocked state, wait the lock.The present invention passes through
The application of distributed lock further ensures the consistency of the session data of same web application.
When the access request for receiving terminal, read-write is initiated to session backup server cluster in session memory management part is asked
When asking, it is also responsible for that it is corresponding to calculate current access request to be which of session backup server cluster session backup services
Device, so that solicited message be sent.
Further, the terminal that session backup server storage is updated using the current sessions data
Session data specifically includes:
Step S501 obtains the session number of the first access request of the terminal stored in the session backup server
According to;
The consistency of the session data of step S502, the current sessions data and the first access request;
If consistent, step S5031 is carried out;
Session backup server is written in the current sessions data by step S5031;
If inconsistent, step S5032 is carried out;
Step S5032 merges the session data of the current sessions data and the first access request, after merging
Session backup server is written in session data.
Namely write-once request is initiated from application server to session backup server cluster.This request can be divided
It is fitted on the corresponding defeated backup server of meeting of session data of this operation, stores dress by the data in the session backup server
It sets and receives request, and carry out back-up processing.
Further, in the session of the first access request of the terminal for obtaining and being stored in the session backup server
After data, further includes:
Unserializing decompression is carried out to the session data of the first access request.
Further, before session backup server is written in the session data of the current access request, further includes:
Serializing compression is carried out to the session data of the current access request.
When the access request for receiving terminal, read-write is initiated to session backup server cluster in session memory management part is asked
When asking, it is also responsible for the serializing and unserializing of session data.
After session data backup server has handled current data write request, data spot lock management device will discharge
The distributed lock of the data, to allow other requests lock.
In addition, the embodiment of the present invention three also proposed a kind of distributed conversation management system, as shown in Figure 3, comprising: judgement
Module, request module, update module and backup module;
Judgment module, for judging whether the current sessions data of terminal access request need to back up;
Request module, for when the judging result of the judgment module be need to back up when, to session backup server collection
Session backup server requests distributed lock corresponding with the terminal in group;
Update module updates the session using the current sessions data and backs up after getting distributed lock
The session data of the terminal of server storage;
Backup module, it is standby for updated session data to be backuped to other sessions in session backup server cluster
Part server.
Further, the judgment module includes: that the first judging submodule, second judgment submodule and third judge submodule
Block,
First judging submodule, for judging whether the current sessions data of terminal access request are newly generated session number
According to if it is, the current sessions data of the access request need to back up;If it is not, then further judging the access
Whether the current sessions data of request are different from the session data of first access request, if it is different, then the access request
Current sessions data need to back up.
Second judgment submodule, for judging whether terminal access request is to nullify session request, when terminal access is requested
When to nullify session request, the current sessions data of the access request need to back up;
Third judging submodule, whether the session data for judging the first access request is expired, when described first
When the session data of access request is expired, the current sessions data of the access request need to back up.
In network application, each request of the user to the web application in Java EE application server all may shadow
It rings and arrives session data.Application server judges whether to need to back up according to the variation of session data, is broadly divided into following three kinds of feelings
Condition:
When newly creation session data, then the current sessions data of the access request need to back up;Specifically, new creation
Session data.Usually when active user and web application establish connection for the first time.As long as newly creating session data, then determine
The session data needs to back up.When the storage state message be it is normal, and the session data of the first access request with work as
When preceding session data difference, then the current sessions data of the access request need to back up;Specifically, having created session
After data, and session data normally be it is no expired or failure in the case where, again to the same session initiation request, just
It is possible that modification session data.After requesting to be processed by corresponding web application, check whether session data is modified, such as
Fruit is modified, then current this part of modified session data needs to back up;When the storage state message is expired, then institute
The current sessions data for stating access request need to back up;Specifically, then sentencing when time is up for the life cycle of session data itself
Fixed session data needs are disposed from backup.
Further, the update module include: acquisition submodule, Comparative sub-module, first write-in submodule and second write
Enter submodule,
Acquisition submodule, for obtaining the meeting of the first access request of the terminal stored in the session backup server
Talk about data;It is also used to obtain distributed lock according to distributed lock response message;
Comparative sub-module, it is consistent with the session data of the first access request for the current sessions data
Property;
First write-in submodule, for when the comparison result of the Comparative sub-module is consistent, by this access request
Session backup server is written in session data;
Second write-in submodule, for merging the current meeting when the comparison result of the Comparative sub-module is inconsistent
Session backup server is written in session data after merging by the session data for talking about data and the first access request.
By using a kind of distributed conversation management method disclosed in this invention and system, make application server in non-parent
Not only it can guarantee session data consistency under the mode of sum, but also the availability of session data can be improved.
The above embodiments are merely illustrative of the technical solutions of the present invention and it is non-limiting, reference only to preferred embodiment to this hair
It is bright to be described in detail.Those skilled in the art should understand that can modify to technical solution of the present invention
Or equivalent replacement should all cover in scope of the presently claimed invention without departing from the spirit and scope of the technical solution of the present invention
In the middle.
Claims (8)
1. a kind of distributed conversation management method characterized by comprising
Session storage management reads preset configuration item, and configuration item content is that individual event selection uses Pessimistic Locking conversation managing method
Or optimistic locking conversation managing method;
If selecting Pessimistic Locking conversation managing method, S201-S205 is thened follow the steps;
Step S201, terminal access request is received;
Step S202, into session backup server cluster, session backup server requests corresponding with the terminal are distributed
Lock;
Step S203, when completing this session request, judge whether the current sessions data of terminal access request need to back up;
Step S204, it such as needs to back up, then updates the institute of the session backup server storage using the current sessions data
State the session data of terminal;
Step S205, updated session data is backuped to other session backup services in session backup server cluster
Device;
If selecting optimistic locking conversation managing method, judge whether the current sessions data of terminal access request need to back up;
If necessary to back up, then into session backup server cluster, session backup server requests corresponding with the terminal are divided
Cloth lock;
After obtaining distributed lock, the terminal of the session backup server storage is updated using the current sessions data
Session data;
Updated session data is backuped to other session backup servers in session backup server cluster.
2. the method according to claim 1, wherein the current sessions data of the judgement terminal access request are
It is no to need to back up, it specifically includes:
Judge whether the current sessions data are newly generated session datas:
If it is, the current sessions data of the access request need to back up;If it is not, then further judging the access
Whether the current sessions data of request are different from the session data of first access request, and the access request works as if different
Preceding session data needs to back up;
When terminal access request is nullifies session request, then the current sessions data of the request need to back up;
When the session data of first access request is expired, then the current sessions data of the access request need to back up.
3. the method according to claim 1, wherein it is described into session backup server cluster with the terminal
Corresponding session backup server requests distributed lock, specifically includes:
Session backup server corresponding with the terminal is searched in the session backup server cluster;
Distributed lock request message is sent to the session backup server.
4. the method according to claim 1, wherein described update the session using the current sessions data
The session data of the terminal of backup server storage, specifically includes:
Obtain the session data of the first access request of the terminal stored in the session backup server;
Compare the consistency of the session data of the current sessions data and the first access request;
If consistent, session backup server is written into the current sessions data;
If inconsistent, merge the session data of the current sessions data and the first access request, by the meeting after merging
It talks about data and session backup server is written.
5. according to the method described in claim 4, it is characterized in that, being stored in the session backup server in described obtain
After the session data of the first access request of terminal, further includes:
Unserializing decompression is carried out to the session data of the first access request.
6. according to the method described in claim 4, it is characterized in that, meeting is written in the session data of the current access request
Before words backup server, further includes:
Serializing compression is carried out to the session data of the current access request.
7. a kind of distributed conversation management system characterized by comprising receiving module, judgment module, request module, update
Module, backup module, the first judging submodule, second judgment submodule and third judging submodule;
The receiving module, for receiving terminal access request;
The request module, for the session backup server requests corresponding with the terminal into session backup server cluster
Distributed lock;
The judgment module judges whether is current sessions data that terminal access is requested for when completing this session request
It needs to back up;
The update module then updates the session backup server using the current sessions data for such as needing to back up
The session data of the terminal of storage;
The backup module, it is standby for updated session data to be backuped to other sessions in session backup server cluster
Part server;
First judging submodule, for judging whether the current sessions data of terminal access request are newly generated session number
According to if it is, the current sessions data of the access request need to back up;If it is not, then further judging the access
Whether the current sessions data of request are different from the session data of first access request, if it is different, then the access request
Current sessions data need to back up;
The second judgment submodule, for judging whether terminal access request is to nullify session request, when terminal access is requested
When to nullify session request, the current sessions data of the access request need to back up;
The third judging submodule, whether the session data for judging the first access request is expired, when described first
When the session data of access request is expired, the current sessions data of the access request need to back up.
8. system according to claim 7, which is characterized in that the update module includes: acquisition submodule, compares submodule
Block, the first write-in submodule and the second write-in submodule,
Acquisition submodule, for obtaining the session number of the first access request of the terminal stored in the session backup server
According to;It is also used to obtain distributed lock according to distributed lock response message;
Comparative sub-module, the consistency for the current sessions data and the session data of the first access request;
First write-in submodule, for when the comparison result of the Comparative sub-module is consistent, by the session of this access request
Session backup server is written in data;
Second write-in submodule, for merging the current sessions number when the comparison result of the Comparative sub-module is inconsistent
According to the session data with the first access request, session backup server is written into the session data after merging.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310740730.0A CN104753987B (en) | 2013-12-26 | 2013-12-26 | A kind of distributed conversation management method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310740730.0A CN104753987B (en) | 2013-12-26 | 2013-12-26 | A kind of distributed conversation management method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN104753987A CN104753987A (en) | 2015-07-01 |
CN104753987B true CN104753987B (en) | 2019-03-01 |
Family
ID=53593085
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201310740730.0A Active CN104753987B (en) | 2013-12-26 | 2013-12-26 | A kind of distributed conversation management method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN104753987B (en) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106027677A (en) * | 2016-07-13 | 2016-10-12 | 浪潮通用软件有限公司 | Distributed Web application program session management method |
CN106484321A (en) * | 2016-09-08 | 2017-03-08 | 华为数字技术(成都)有限公司 | A kind of date storage method and data center |
CN106603713B (en) * | 2016-12-29 | 2020-09-22 | 深圳Tcl新技术有限公司 | Session management method and system |
CN107948276A (en) * | 2017-11-22 | 2018-04-20 | 用友金融信息技术股份有限公司 | Distributed conversation update method, device, computer equipment and readable storage medium storing program for executing |
CN112035446B (en) * | 2019-06-03 | 2024-04-19 | 北京沃东天骏信息技术有限公司 | Data extraction method, device and storage medium |
CN111385356B (en) * | 2020-03-04 | 2023-06-23 | 平安科技(深圳)有限公司 | Distributed session processing method, device and system |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101196829A (en) * | 2007-12-27 | 2008-06-11 | 电子科技大学 | Locking Method of Data Conflict Module in Collaborative Editing |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2453073A1 (en) * | 2001-07-06 | 2003-01-16 | Computer Associates Think, Inc. | Systems and methods of information backup |
CN100432940C (en) * | 2006-10-19 | 2008-11-12 | 华为技术有限公司 | Method for distributing shared resource lock in computer cluster system and cluster system |
CN101252603B (en) * | 2008-04-11 | 2011-03-30 | 清华大学 | Cluster Distributed Lock Management Method Based on Storage Area Network SAN |
CN101488924B (en) * | 2009-02-16 | 2011-11-16 | 成都市华为赛门铁克科技有限公司 | Metadata modification method and metadata server |
CN102387204B (en) * | 2011-10-21 | 2014-12-10 | 中国科学院计算技术研究所 | Method and system for maintaining consistency of cluster caching |
CN102523234B (en) * | 2011-12-29 | 2015-12-02 | 山东中创软件工程股份有限公司 | A kind of application server cluster implementation method and system |
CN103188110B (en) * | 2013-03-29 | 2016-01-06 | 汉柏科技有限公司 | Based on the heat backup method that the cloud platform of zookeeper is served |
-
2013
- 2013-12-26 CN CN201310740730.0A patent/CN104753987B/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101196829A (en) * | 2007-12-27 | 2008-06-11 | 电子科技大学 | Locking Method of Data Conflict Module in Collaborative Editing |
Non-Patent Citations (1)
Title |
---|
Java EE多层软件架构的安全构建;郭文龙,任进军;《宜宾学院学报》;20131030 |
Also Published As
Publication number | Publication date |
---|---|
CN104753987A (en) | 2015-07-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN104753987B (en) | A kind of distributed conversation management method and system | |
US8688773B2 (en) | System and method for dynamically enabling an application for business continuity | |
CN110990200B (en) | A method and device for traffic switching based on a multi-active data center | |
US20140108532A1 (en) | System and method for supporting guaranteed multi-point delivery in a distributed data grid | |
CN106487486B (en) | Service processing method and data center system | |
CN112380072B (en) | Multi-data center access method and system | |
CN105337780B (en) | A kind of server node configuration method and physical node | |
CN101136728A (en) | Cluster system and method for backing up a replica in a cluster system | |
CN105338078A (en) | Data storage method and device used for storing system | |
JP6615761B2 (en) | System and method for supporting asynchronous calls in a distributed data grid | |
CN110442610A (en) | The method, apparatus of load balancing calculates equipment and medium | |
CN105357042B (en) | A kind of highly available cluster system and its host node and from node | |
CN104038376A (en) | Method and device for managing real servers and LVS clustering system | |
CN107038192B (en) | Database disaster tolerance method and device | |
CN108614728A (en) | Virtual machine service providing method, device, equipment and computer readable storage medium | |
CN113946276A (en) | Disk management method and device in cluster and server | |
CN106385330B (en) | Implementation method and device of a network function virtualization orchestrator | |
US8812632B2 (en) | Arrangement for operating a computer cluster | |
US7519855B2 (en) | Method and system for distributing data processing units in a communication network | |
US20050234919A1 (en) | Cluster system and an error recovery method thereof | |
CN112631756B (en) | A distributed control method and device for aerospace measurement and control software | |
US20080250421A1 (en) | Data Processing System And Method | |
CN117692500A (en) | Operation method, device, equipment and storage medium | |
CN106534758A (en) | Conference backup method and conference backup device | |
CN116455920A (en) | Data storage method, system, computer equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |