CN107948224A - The timeout treatment method and apparatus of client request - Google Patents
The timeout treatment method and apparatus of client request Download PDFInfo
- Publication number
- CN107948224A CN107948224A CN201610890659.8A CN201610890659A CN107948224A CN 107948224 A CN107948224 A CN 107948224A CN 201610890659 A CN201610890659 A CN 201610890659A CN 107948224 A CN107948224 A CN 107948224A
- Authority
- CN
- China
- Prior art keywords
- task
- overtime
- time
- request
- server
- 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.)
- Granted
Links
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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Debugging And Monitoring (AREA)
Abstract
This application discloses a kind of timeout treatment method and apparatus of client request, method includes：The each connection request being currently received is packaged into task by server-side, and it is added in pending request task pond and time-out monitoring queue corresponding with the delay threshold of task, time-out monitoring queue in server-side is corresponded with the delay threshold supported, the task in each time-out monitoring queue is arranged according to overtime moment ascending order；Task is taken out in pending request task pond non-NULL, triggers the implementation procedure to task according to task status；For each time-out monitoring queue, according to the default overtime scan period, the overtime task in dequeue and deletion are searched, and overtime task is put into timeout treatment thread pool when overtime task is in untreated state；Overtime task is taken out in timeout treatment thread pool non-NULL, and triggers the timeout treatment process according to task status to task., can be with timely processing timeout request using the present invention.
Description
Technical field
The present invention relates to Computer Applied Technology, more particularly to the timeout treatment method and dress of a kind of client request
Put.
Background technology
With the fast development of internet, WEB application system quantity is continuously increased, thing followed distributed system
Occur, cause the intersection of business between various systems, can all be related to the mutual calling of the interface of system.More particularly to difference
Between the system of company, such as purchase system and warehouse system, purchase system and payment system.And external system and built-in system
Between interaction be typically all growing, the interaction times between interface of adjoint number of users using HTTP interface by the way of
Also it is being continuously increased, correspondingly, is also increasing the access pressure of system.In this case, after connection request reaches server-side, just
Can exist since the number of requests for reaching server-side is more, and appearance processing request time is long, cannot timely respond to client
The request timed out situation of request.
In the existing processing scheme for request timed out, for each request queue, have timed thread and scan the queue,
Judge whether the current request has timed out according to the timeout treatment time of the request for each request in queue, if so,
Then it is deleted from queue, meanwhile, give request processing time-out notification to corresponding client.Also, in order to keep asking
The continuity of queue, can be handled deleting the queue after timeout request.Specifically processing mode can be：To in former queue
Respectively ask into row position adjustment or, the request that has not timed out in former queue is copied to this and created by a newly-built queue
In queue, in this way, can make it that data have continuity in the queue after adjustment.As shown in Figure 1, request list 1 is time T1
When request queue, each data therein represent a request, by timeout request therein (data 3, data 4,8 and of data
Data 9) delete after, again to the data in 1 corresponding queue of request list into the adjustment of row position or using newly-built queue simultaneously
The mode of valid data, can obtain the queue result shown in request list 2 in the former queue of copy.
In above-mentioned timeout treatment scheme, since the overtime moment of different requests in queue is probably different and and is asked
Sequencing in queue is unrelated, that is to say, that the request of any one position in queue, which can all exist, reaches the overtime moment
Situation, therefore, timed thread needs to travel through whole request queue, when queue length reaches it is tens of thousands of when the traversal time meeting of one time
Very long, along with the judgement processing time of each data, the time-out that may result in a queue judges to take very much.In addition,
The length of each request queue is limited, if timeout request processing is not in time, it is impossible in time by the request of time-out from team
Delete in row, just occur：Queue is caused can not completely to have added new request to the feelings in queue due to the presence of timeout request
Condition, in this way, the request after may result in is rejected, in turn results in very poor user experience.
It can be seen from the above that existing timeout treatment scheme cannot get timely processing, shadow there are request is had timed out in request queue
The problem of ringing the receiving of subsequent request, and then influencing the service performance of system.
The content of the invention
In view of this, it is a primary object of the present invention to provide a kind of timeout treatment method and apparatus of client request,
Can be with timely processing timeout request.
In order to achieve the above object, technical solution proposed by the present invention is：
A kind of timeout treatment method of client request, including：
The each connection request being currently received is packaged into task by server-side, and the task is added to pending ask
Ask in task pool and time-out monitoring queue corresponding with the delay threshold of task, wherein, the time-out monitoring in server-side
Queue and the delay threshold supported correspond, and each time-out monitors ascending order of the task in queue according to the overtime moment
Arrangement；
The server-side is taken out task in the pending request task pond non-NULL, and triggers working as according to task
Implementation procedure of the pre-treatment state to taken out task；
For each time-out monitoring queue, the server-side searches dequeue according to the default overtime scan period
In overtime task and deletion, and the overtime task is put into timeout treatment when the overtime task is in untreated state
Thread pool；
The server-side is taken out in the timeout treatment thread pool non-NULL from for the timeout treatment thread pool to be surpassed
When task, and trigger the timeout treatment process according to the current processing status of task to taken out overtime task.
A kind of timeout treatment device of client request, including：
Processing unit is received, each connection request for server-side to be currently received is packaged into task, and by described in
Task is added in pending request task pond and time-out monitoring queue corresponding with the delay threshold of task, wherein, service
The time-out monitoring queue in end is corresponded with the delay threshold supported, the task in each time-out monitoring queue
Arranged according to the ascending order at overtime moment；
Task executing units, for being taken out task in the pending request task pond non-NULL, and trigger basis
Implementation procedure of the current processing status of task to taken out task；
Overtime monitoring unit, for for each time-out monitoring queue, according to the default overtime scan period, searching
Overtime task and deletion in dequeue, and when the overtime task is in untreated state be put into the overtime task super
When handle thread pool；
Timeout treatment unit, for being taken out overtime task in the timeout treatment thread pool non-NULL, and triggers root
According to the current processing status of task to the timeout treatment process of taken out overtime task.
In conclusion the timeout treatment method and apparatus of family end proposed by the present invention request, based on a variety of delay thresholds into
The corresponding task of the request is put into and its time delay threshold by the management of the more queue time-out of row, server-side after connection request is received
It is worth in corresponding time-out monitoring queue, also, the task in each time-out monitoring queue is the liter according to the overtime moment of task
Sequence arranges.For the task in pending request task pond and the task in time-out monitoring queue, server-side will independently root
Perform the process of being treated differently according to the current execution state of task, i.e., for the former by the implementation procedure of the task of triggering, for
The more queues for triggering time-out are concurrently monitored process by the latter.In this way, the overtime detection efficiency of task can be effectively improved, avoid surpassing
When task cannot get timely processing caused by system service performance it is impacted the problem of.In addition, to task execution processing and
Timeout treatment is independently to carry out parallel, and two kinds of processing procedures are required for the current processing status of consideration task, therefore, can be with
Ensure only once to perform a task or timeout treatment, so that both may insure the efficiency that server-side handles task,
Again can be to avoid reprocessing of the system to same task, and then waste that can be to avoid server-side process resource and client
The exception of side.
Brief description of the drawings
Fig. 1 is the schematic diagram adjusted in traditional scheme after request timed out to request queue；
Fig. 2 is the method flow schematic diagram of the embodiment of the present invention；
Fig. 3 is the apparatus structure schematic diagram of the embodiment of the present invention.
Embodiment
It is right below in conjunction with the accompanying drawings and the specific embodiments to make the object, technical solutions and advantages of the present invention clearer
The present invention is described in further detail.
The present invention core concept be：According to delay threshold (the i.e. receivable largest request processing delay of connection request
Length) time-out monitoring queue is established, after server-side receives connection request, the corresponding task of the request is put into and its time delay threshold
It is worth in corresponding time-out monitoring queue, also, the task in each time-out monitoring queue is the liter according to the overtime moment of task
Sequence arranges, in this way, when the time-out to task is monitored, it is not necessary to each time-out monitoring queue of traversal, as long as monitoring to surpass
When monitor a task in queue it is not overtime when avoid the need for carrying out overtime judgement to the task behind queue again, therefore, can
To effectively improve the overtime detection efficiency of task, avoid overtime task cannot get timely processing caused by system service performance by
The problem of influence.In addition, execution processing and timeout treatment of the server-side to task carry out parallel, and two processing procedures are all
The current processing status of consideration task is needed, in this way, not only may insure the efficiency that server-side handles task, but also can be to avoid being
The repetitive operation united to same task, and then can be to avoid the waste of server-side process resource and the exception of client-side.
Fig. 2 is the flow diagram of the embodiment of the present invention, as shown in Fig. 2, the client request that the embodiment is realized is super
When processing method mainly include：
The each connection request being currently received is packaged into task by step 201, server-side, and the task is added to
In pending request task pond and time-out monitoring queue corresponding with the delay threshold of task, wherein, it is described in server-side
Time-out monitoring queue and the delay threshold supported correspond, when the task in each time-out monitoring queue is according to time-out
The ascending order arrangement at quarter.
With existing scheme except that, it is necessary to that corresponding task will be asked to be put into is corresponding with its delay threshold in this step
Time-out monitoring queue in, and time-out monitoring queue in task according to the overtime moment ascending order arrange, so as to time-out monitor
When, only need to scan the part before each time-out monitoring queue in each overtime monitoring cycle, when scanning is to having not timed out
During task (i.e. current time is after the overtime moment of task), it is whether overtime that follow-up work can not be reexamined.
In addition, establish a time-out monitoring queue herein for every kind of delay threshold, and when each queue is according to time-out
The ascending order arrangement at quarter, being conducive to same delay threshold value of the task are sequentially placed into timeout treatment thread pool according to the morning and evening of receiving time
Timeout treatment is carried out, so as to while avoiding overtime task from cannot get timely processing, it is ensured that the fairness of task processing.
In practical applications, the value of delay threshold can have the numerical value such as 1s, 2s, 3s, 4s and 5s, specifically with the needs of actual user
Match.
Specifically, can according to overTime=createTime+timeout, to determine the overtime moment, wherein,
At the time of createTime receives connection request corresponding to task for the server-side, timeout is corresponding to the task
The delay threshold of connection request, overTime are the overtime moment.
Specifically, server-side can use the method identical with existing scheme to seal each connection request being currently received
Task is dressed up, details are not described herein.
It is preferred that the time-out monitoring queue uses ring data structure, i.e., time-out monitoring queue is a ring.It is this
Structure can recycle queue, without reconfiguring queue, so as to reduce data queue caused by queuing data changes
Reconstruct and copy.
Step 202, the server-side are taken out task in the pending request task pond non-NULL, and trigger basis
Implementation procedure of the current processing status of task to taken out task；
For each time-out monitoring queue, the server-side searches dequeue according to the default overtime scan period
In overtime task and deletion, and when the overtime task is in untreated state, the overtime task is put into overtime place
Manage thread pool；
The server-side is taken out overtime task in the timeout treatment thread pool non-NULL, and triggers according to task
Timeout treatment process of the current processing status to taken out overtime task.
In this step 202, server-side will carry out the task in pending request task pond and time-out monitoring queue respectively
Independent process, so in specific implementation, the execution and time-out monitoring of task will need different threads to realize, can improve clothes
The connection request treatment effeciency at business end.Especially since server-side is to establish an overtime monitoring team for every kind of delay threshold
Row, therefore, when reaching each overtime scan period, will realize above-mentioned overtime monitoring function, it is necessary to be each overtime monitoring team
Row configuration one time-out scanning thread, in this way, scanned using multi-thread concurrent, can improve the identification and processing of overtime task
Efficiency, it is ensured that be capable of the connection request task of timely processing time-out.
In addition, as described in step 201, the task in time-out monitoring queue is arranged according to the ascending order at overtime moment, i.e. team
The foremost of row is earliest time-out, and queue is backmost overtime the latest, and therefore, scanning every time is only needed before scan queue
A part, so as to increase substantially overtime monitoring efficiency.
The specifically chosen strategy that server-side takes out task from the pending request task pond can use existing method to realize,
Also can be by those skilled in the art according to setting is actually needed, details are not described herein.In addition, here, task bag is taken out from pond
Containing the implication for deleting task from pond.
It is preferred that the implementation procedure of taken out task can specifically be adopted according to the current processing status of task in this step
Realized with following methods：
If being taken out for task is in untreated state, perform the task, it is described perform complete and the task still
During in untreated state, the processing state of the task is arranged to processed, and the implementing result of the task is fed back into phase
The client answered.
In above-mentioned implementation procedure, need to judge whether it is in untreated state before execution task, if in not
Processing state, then illustrate that task without timeout treatment, can perform the task, if being in processed state, say at this time
Bright task has been subjected to timeout treatment, at this time, if perform again and result be returned to client will result in client processing it is abnormal,
It therefore, there is no need to perform the task again, the reduction of waste, task treatment effeciency to avoid server-side resource and client-side
Exception the problems such as.Likewise, after the completion of tasks carrying, it is also desirable to consider the current execution state of task, i.e., only at this
When task is still in untreated state, the implementing result of task is just fed back into corresponding client, to avoid task into
Implementing result is issued into the waste of server-side resource caused by client, the reduction of task treatment effeciency again after row timeout treatment
And client it is abnormal the problems such as.In addition, tasks carrying is complete return the result while also need to set the processing state of task
Be set to it is processed, so as to when carrying out overtime monitoring and processing, it is not necessary to further timeout treatment is carried out again, to avoid service
Hold and carry out that the wasting of resources caused by timeout treatment, treatment effeciency are low and client is abnormal again to the task of executed etc. and ask
Topic.
In step 202, time-out therein will periodically be found out for each time-out monitoring queue, server-side
Task, it is necessary to judge its current state after it is deleted from time-out monitoring queue, just will when untreated state at which
The overtime task is put into timeout treatment thread pool, to do further timeout treatment to it, and when it is in processed shape
Timeout treatment thread pool is no longer put it into during state, this way it is possible to avoid server-side carries out overtime place again to the task of executed
The caused wasting of resources of reason, treatment effeciency are low and the problems such as client is abnormal.
The specifically chosen strategy that server-side takes out overtime task from timeout treatment thread pool can use existing method to realize,
Also can be by those skilled in the art according to setting is actually needed, details are not described herein.In addition, here, task bag is taken out from pond
Containing the implication for deleting task from pond.
It is preferred that can to the timeout treatment process of taken out overtime task according to the current processing status of task in this step
To be realized using following methods：
If the overtime task taken out is in untreated state, which is had timed out into notice to corresponding client
End, and the processing state of the task is arranged to processed.
Need first to judge whether it is currently in untreated state when in the above-mentioned methods, at overtime task, such as
Fruit is then to illustrate that it has been performed completion, it is not necessary to is handled again, above-mentioned caused by avoid reprocessing many is asked
Topic；Otherwise, illustrate that it is not performed completion, at this time, it may be necessary to carry out timeout treatment to it, i.e., task is had timed out into notice to corresponding
Client, and the processing state of the task is arranged to processed, in this way, server-side takes from pending request task pond again
The task will not be performed when going out the task again, above-mentioned many is asked so as to avoid reprocessing caused by same task
Topic.
The time-out scan period, can set appropriate value according to being actually needed, for example, can be with by those skilled in the art
It is 200ms.
Fig. 3 is the timeout treatment device of client request corresponding with the above method, as shown in figure 3, the device includes：
Processing unit is received, each connection request for server-side to be currently received is packaged into task, and by described in
Task is added in pending request task pond and time-out monitoring queue corresponding with the delay threshold of task, wherein, service
The time-out monitoring queue in end is corresponded with the delay threshold supported, the task in each time-out monitoring queue
Arranged according to the ascending order at overtime moment；
Task executing units, for being taken out task in the pending request task pond non-NULL, and trigger basis
Implementation procedure of the current processing status of task to taken out task；
Overtime monitoring unit, for for each time-out monitoring queue, according to the default overtime scan period, searching
Overtime task and deletion in dequeue, and when the overtime task is in untreated state be put into the overtime task super
When handle thread pool；
Timeout treatment unit, for being taken out overtime task in the timeout treatment thread pool non-NULL, and triggers root
According to the current processing status of task to the timeout treatment process of taken out overtime task.
It is preferred that the task executing units, if be in for being taken out when carrying out the implementation procedure for task
Untreated state, then perform the task, when the execution is completed and the task is still in untreated state, by the place of the task
Reason state is arranged to processed, and the implementing result of the task is fed back to corresponding client.
It is preferred that it is characterized in that, the timeout treatment unit is used for when carrying out the timeout treatment process, if institute
The overtime task of taking-up is in untreated state, then the task is had timed out notice to corresponding client, and by the task
Processing state is arranged to processed.
It is preferred that the reception processing unit is used for according to overTime=createTime+timeout, determine described
The overtime moment, wherein, at the time of createTime receives connection request corresponding to task for the server-side, timeout is
The delay threshold of connection request corresponding to the task, overTime are the overtime moment.
It is preferred that the time-out monitoring queue uses ring data structure.
Pass through above-described embodiment, it can be seen that the present invention can not only handle application system high concurrent request, can with and
When, the situation of efficiently processing connection time-out, the response efficiency of lifting system and support substantial amounts of client request, and then lifted
The integrity service responding ability of system.
In conclusion the foregoing is merely a prefered embodiment of the invention, it is not intended to limit the scope of the present invention.
Within the spirit and principles of the invention, any modification, equivalent replacement, improvement and so on, should be included in the present invention's
Within protection domain.
Claims (10)
1. a kind of timeout treatment method of client request, it is characterised in that including：
The each connection request being currently received is packaged into task by server-side, and the task is added to pending request and is appointed
It is engaged in pond and time-out monitoring queue corresponding with the delay threshold of task, wherein, the time-out monitoring queue in server-side
Corresponded with the delay threshold supported, the task in each time-out monitoring queue is arranged according to the ascending order at overtime moment
Row；
The server-side is taken out task in the pending request task pond non-NULL, and triggers the current place according to task
Implementation procedure of the reason state to taken out task；
For each time-out monitoring queue, the server-side is searched in dequeue according to the default overtime scan period
Overtime task is simultaneously deleted, and the overtime task is put into timeout treatment thread when the overtime task is in untreated state
Pond；
The server-side is taken out overtime task in the timeout treatment thread pool non-NULL, and triggers according to the current of task
Timeout treatment process of the processing state to taken out overtime task.
2. according to the method described in claim 1, it is characterized in that, the implementation procedure includes：
If being taken out for task is in untreated state, perform the task, it is described perform complete and the task still in
During untreated state, the processing state of the task is arranged to processed, and the implementing result of the task is fed back to accordingly
Client.
3. according to the method described in claim 1, it is characterized in that, the timeout treatment process includes：
If the overtime task taken out is in untreated state, which is had timed out into notice to corresponding client, and
The processing state of the task is arranged to processed.
4. according to the method described in claim 1, it is characterized in that, according to overTime=createTime+timeout, really
The fixed overtime moment, wherein, at the time of createTime receives connection request corresponding to task for the server-side,
Timeout is the delay threshold of connection request corresponding to the task, and overTime is the overtime moment.
5. according to the method described in claim 1, it is characterized in that, the time-out monitoring queue uses ring data structure.
A kind of 6. timeout treatment device of client request, it is characterised in that including：
Processing unit is received, each connection request for server-side to be currently received is packaged into task, and by the task
It is added in pending request task pond and time-out monitoring queue corresponding with the delay threshold of task, wherein, in server-side
The time-out monitoring queue and the delay threshold supported correspond, the task in each time-out monitoring queue according to
The ascending order arrangement at overtime moment；
Task executing units, for being taken out task in the pending request task pond non-NULL, and are triggered according to task
Current processing status to the implementation procedure of taken out task；
Overtime monitoring unit, for for each time-out monitoring queue, according to the default overtime scan period, finding out team
Overtime task and deletion in row, and the overtime task is put into overtime place when the overtime task is in untreated state
Manage thread pool；
Timeout treatment unit, for being taken out overtime task in the timeout treatment thread pool non-NULL, and triggers basis and appoints
Timeout treatment process of the current processing status of business to taken out overtime task.
7. device according to claim 6, it is characterised in that the task executing units, for carrying out the execution
If being taken out during process for task is in untreated state, the task is performed, is completed in the execution and the task is still located
When untreated state, the processing state of the task is arranged to processed, and the implementing result of the task is fed back to accordingly
Client.
8. device according to claim 6, it is characterised in that the timeout treatment unit is used to carry out at the time-out
During reason process, if the overtime task taken out is in untreated state, which is had timed out into notice to corresponding client
End, and the processing state of the task is arranged to processed.
9. device according to claim 6, it is characterised in that the reception processing unit is used for according to overTime=
CreateTime+timeout, determines the overtime moment, wherein, it is right that createTime for the server-side receives task
At the time of answering connection request, timeout is the delay threshold of connection request corresponding to the task, when overTime is time-out
Carve.
10. device according to claim 6, it is characterised in that the time-out monitoring queue uses ring data structure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610890659.8A CN107948224B (en) | 2016-10-12 | 2016-10-12 | Timeout processing method and device for client request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610890659.8A CN107948224B (en) | 2016-10-12 | 2016-10-12 | Timeout processing method and device for client request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107948224A true CN107948224A (en) | 2018-04-20 |
| CN107948224B CN107948224B (en) | 2021-07-06 |
Family
ID=61928309
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610890659.8A Active CN107948224B (en) | 2016-10-12 | 2016-10-12 | Timeout processing method and device for client request |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107948224B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109308219A (en) * | 2018-08-23 | 2019-02-05 | 阿里巴巴集团控股有限公司 | Task processing method, device and Distributed Computer System |
| CN111538589A (en) * | 2020-04-14 | 2020-08-14 | 明见（厦门）技术有限公司 | Operation optimization method, device, terminal and medium for thread blocking queue of embedded OS (operating system) |
| CN113115138A (en) * | 2021-03-24 | 2021-07-13 | 烽火通信科技股份有限公司 | Message interaction timeout judgment method, device, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1412691A (en) * | 2001-10-21 | 2003-04-23 | 天象网络技术（上海）有限公司 | Network integrating centralized calculation and distributed calculation |
| CN1684424A (en) * | 2004-04-12 | 2005-10-19 | 英业达股份有限公司 | Verifying method for network file system service |
| CN101145116A (en) * | 2006-09-14 | 2008-03-19 | 国际商业机器公司 | Method and system for timing operation with different continual time |
| CN101887367A (en) * | 2010-06-22 | 2010-11-17 | 天津大学 | Multi-level parallel programming method |
| CN102129393A (en) * | 2011-03-09 | 2011-07-20 | 南京恩瑞特实业有限公司 | Universal timed task management realization method |
| US20150242254A1 (en) * | 2012-08-10 | 2015-08-27 | Samsung Techwin Co., Ltd. | Method and apparatus for processing message between processors |
| CN105809305A (en) * | 2014-12-30 | 2016-07-27 | 金蝶软件（中国）有限公司 | Method and device for realizing flow automatic approval |
-
2016
- 2016-10-12 CN CN201610890659.8A patent/CN107948224B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1412691A (en) * | 2001-10-21 | 2003-04-23 | 天象网络技术（上海）有限公司 | Network integrating centralized calculation and distributed calculation |
| CN1684424A (en) * | 2004-04-12 | 2005-10-19 | 英业达股份有限公司 | Verifying method for network file system service |
| CN101145116A (en) * | 2006-09-14 | 2008-03-19 | 国际商业机器公司 | Method and system for timing operation with different continual time |
| CN101887367A (en) * | 2010-06-22 | 2010-11-17 | 天津大学 | Multi-level parallel programming method |
| CN102129393A (en) * | 2011-03-09 | 2011-07-20 | 南京恩瑞特实业有限公司 | Universal timed task management realization method |
| US20150242254A1 (en) * | 2012-08-10 | 2015-08-27 | Samsung Techwin Co., Ltd. | Method and apparatus for processing message between processors |
| CN105809305A (en) * | 2014-12-30 | 2016-07-27 | 金蝶软件（中国）有限公司 | Method and device for realizing flow automatic approval |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109308219A (en) * | 2018-08-23 | 2019-02-05 | 阿里巴巴集团控股有限公司 | Task processing method, device and Distributed Computer System |
| CN109308219B (en) * | 2018-08-23 | 2021-08-10 | 创新先进技术有限公司 | Task processing method and device and distributed computer system |
| CN111538589A (en) * | 2020-04-14 | 2020-08-14 | 明见（厦门）技术有限公司 | Operation optimization method, device, terminal and medium for thread blocking queue of embedded OS (operating system) |
| CN111538589B (en) * | 2020-04-14 | 2023-05-05 | 明见（厦门）技术有限公司 | Operation optimization method, device, terminal and medium for embedded OS thread blocking queue |
| CN113115138A (en) * | 2021-03-24 | 2021-07-13 | 烽火通信科技股份有限公司 | Message interaction timeout judgment method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107948224B (en) | 2021-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110908788B (en) | Spark Streaming based data processing method and device, computer equipment and storage medium | |
| US11119911B2 (en) | Garbage collection method and device | |
| CN110825535B (en) | Job scheduling method and system | |
| CA3104806A1 (en) | Method for scheduling a task, resource sharing use method and system based on preemptive scheduling, scheduler, device, and storage medium | |
| EP2434401A1 (en) | Method and system for managing thread pool | |
| WO2019182670A1 (en) | Endpoint process state collector | |
| US8661441B2 (en) | Transaction load reduction for process completion | |
| CN106776829A (en) | A kind of data guiding system and its method of work | |
| CN105516086B (en) | Method for processing business and device | |
| CN104216768A (en) | Data processing method and device | |
| CN106843170A (en) | Method for scheduling task based on token | |
| CN107948224A (en) | The timeout treatment method and apparatus of client request | |
| CN113312165B (en) | Task processing method and device | |
| WO2019219005A1 (en) | Data processing system and method | |
| CN105653356B (en) | Handle the method and device of multiserver concurrent operations | |
| CN111026530A (en) | Task scheduling method and device, computer equipment and storage medium | |
| CN112000350A (en) | Dynamic rule updating method, device and storage medium | |
| CN104408110A (en) | Method, device and system for requesting data | |
| CN109597837A (en) | Storage method, querying method and the relevant device of time series data | |
| CN113393213A (en) | Method for creating group, computer equipment and storage medium | |
| CN106293911A (en) | Dispatching System, method | |
| CN109614241B (en) | Method and system for realizing multi-cluster multi-tenant resource isolation based on Yarn queue | |
| CN110737526A (en) | method and device for managing timed tasks under Redis-based distributed cluster | |
| CN111522630A (en) | Method and system for executing planned tasks based on batch dispatching center | |
| CN103970592B (en) | The single thread multi-task processing method and server of transaction middleware |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |