CN108536613B - Data cleaning method and device and server - Google Patents
Data cleaning method and device and server Download PDFInfo
- Publication number
- CN108536613B CN108536613B CN201810191254.4A CN201810191254A CN108536613B CN 108536613 B CN108536613 B CN 108536613B CN 201810191254 A CN201810191254 A CN 201810191254A CN 108536613 B CN108536613 B CN 108536613B
- Authority
- CN
- China
- Prior art keywords
- data
- identification information
- service
- thread
- service request
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0253—Garbage collection, i.e. reclamation of unreferenced memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/366—Software debugging using diagnostics
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the specification provides a data cleaning method, a data cleaning device and a server. The method comprises the following steps: receiving a service request, and setting identification information of service data of the service request; creating an execution thread of the service request, and acquiring first thread context data of the execution thread; detecting whether the identification information of the first thread context data is consistent with the identification information of the service data; and when the detection result is negative, cleaning the first thread context data of the execution thread.
Description
Technical Field
The embodiment of the specification relates to the technical field of computer processing, in particular to a data cleaning method, a data cleaning device and a server.
Background
With the development of computer technology, some business systems often use thread variables to perform the passing of business parameters when task threads are running. However, the service system is often complex and changeable, and if a large number of thread variables cannot be cleaned in time during the operation processing process, a large amount of memory leakage is easily caused.
Currently, the cleaning of the thread variables in the memory generally needs to be handled by using a uniform thread cleaning code when the service is finished. In the existing thread variable cleaning mode, code nesting often occurs due to complex and changeable services, so that problems of untimely cleaning of thread variables or omission and the like caused by thread cleaning code nesting errors are easily caused, memory leakage accumulation is caused, and a system is crashed. Therefore, there is a need to provide a more reliable or efficient solution.
Disclosure of Invention
An object of the embodiments of the present specification is to provide a data cleaning method, apparatus, and server, which can ensure that a process variable is cleaned in time, and avoid a problem of accumulation of memory leakage.
The embodiment of the specification is realized by the following steps:
a method of data scrubbing, comprising:
receiving a service request, and setting identification information of service data of the service request;
creating an execution thread of the service request, and acquiring first thread context data of the execution thread;
detecting whether the identification information of the first thread context data is consistent with the identification information of the service data;
and when the detection result is negative, cleaning the first thread context data of the execution thread.
A data cleansing apparatus comprising:
a service request receiving module, configured to receive a service request;
the identification information setting module is used for setting the identification information of the service data of the service request;
the execution thread creating module is used for creating an execution thread of the service request;
a thread context data obtaining module, configured to obtain first thread context data of the execution thread;
an identification information detection module, configured to detect whether identification information of the first thread context data is consistent with identification information of the service data;
and the data cleaning module is used for cleaning the first thread context data of the execution thread when the detection result of the identification information detection module is negative.
A data cleansing server comprising a processor and a memory, the memory storing computer program instructions for execution by the processor, the computer program instructions comprising:
receiving a service request, and setting identification information of service data of the service request;
creating an execution thread of the service request, and acquiring first thread context data of the execution thread;
detecting whether the identification information of the first thread context data is consistent with the identification information of the service data;
and when the detection result is negative, cleaning the first thread context data of the execution thread.
As can be seen from the above, in one or more embodiments of the present disclosure, by setting identification information for service data of a currently received service request, whether thread context data that has been executed and is not cleaned in time exists in a memory can be detected through the identification information, and when it is detected that the thread context data that is not cleaned in time exists in the memory, the thread context data can be cleaned in time, so that a problem of accumulation of memory leakage during a thread running process is avoided.
Drawings
In order to more clearly illustrate one or more embodiments or prior art solutions of the present description, the drawings used in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the description below are only some embodiments described in the present description, and that other drawings may be obtained by those skilled in the art without inventive effort.
FIG. 1 is a schematic flow chart diagram illustrating one embodiment of a data cleansing method provided herein;
FIG. 2 is a schematic flow chart diagram illustrating another embodiment of a data cleansing method provided herein;
FIG. 3 is a schematic flow chart diagram illustrating another embodiment of a data cleansing method provided herein;
FIG. 4 is a schematic structural diagram of an embodiment of a data cleansing apparatus provided in the present specification;
FIG. 5 is a schematic structural diagram of another embodiment of a data cleansing apparatus provided in the present specification;
fig. 6 is a schematic block diagram of a data cleansing server according to an exemplary embodiment of the present description.
Detailed Description
The embodiment of the specification provides a data cleaning method, a data cleaning device and a server.
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort shall fall within the protection scope of the present specification.
An embodiment of a data cleansing method of the present specification is described below. FIG. 1 is a schematic flow chart diagram of one embodiment of a data cleansing method provided herein, which provides the method operation steps as described in the embodiments or flowcharts, but may include more or less operation steps based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of sequences, and does not represent a unique order of performance. In practice, the system or server product may be implemented in a sequential or parallel manner (e.g., parallel processor or multi-threaded environment) according to the embodiments or methods shown in the figures. Specifically, as shown in fig. 1, the method may include:
s102: receiving a service request, and setting identification information of service data of the service request.
In this embodiment of the present description, after receiving a service request, a service system may set identification information for service data of the service request. Specifically, the identification information may be used as a differential identification of different service data.
In practical application, the identification information may be identification information generated by a current service system, or identification information acquired from other interactive terminals. In a specific embodiment, the identification information may be a serial number generated according to a certain rule, or a request number of a service, which may mark data that is a unique identifier of service data requested at a time.
S104: and creating an execution thread of the service request.
In this embodiment, after receiving a new service request, the service system may create an execution thread for the service request.
S106: first thread context data of the execution thread is obtained.
In this embodiment, the first thread context data may be thread context data in a memory for storing a corresponding execution thread.
In this embodiment of the present specification, the thread context data may be data generated according to service data, and the identification information corresponding to the service data may be identification information of corresponding thread context data.
In other embodiments, the thread context data may be data generated according to the service data and the identification information of the service data.
In this embodiment of the present specification, generating the thread context data according to the service data may include using the service data as the thread context data, or using the service data as the thread context data after being packaged.
Correspondingly, generating the thread context data according to the service data and the identification information of the service data may include using the service data and the identification information of the service data as the thread context data, or packaging the service data and the identification information of the service data and then using the packaged service data and identification information of the service data as the thread context data.
In addition, in this embodiment of the present specification, the service data in the first thread context data may be service data of a current service request, or may also be service data of a service request that has been executed before.
S108: and detecting whether the identification information of the first thread context data is consistent with the identification information of the service data.
In this embodiment of the present specification, after obtaining the first thread context data, it may be detected whether the identification information of the first thread context data is consistent with the identification information of the service data of the current service request, so as to determine whether the service data corresponding to the first thread context data of the current execution thread is the service data of the service request that has been executed.
S110: and when the detection result is negative, cleaning the first thread context data of the execution thread.
Specifically, when the detection result in step S108 is negative, it may be determined that the service data corresponding to the first thread context data is the service data of the service request that has been executed; accordingly, it can be determined that the memory leaks, and the current thread context data (i.e., the first thread context data) can be directly cleared.
As can be seen from the above description, in the embodiment of the present specification, by setting identification information for service data of a currently received service request, based on the identification information, it can be detected whether the service data corresponding to thread context data of a currently executed thread is the service data of the current service request, and further, it can be determined whether thread context data exists that has been executed but is not cleaned in time.
In other embodiments, as shown in fig. 2, fig. 2 is a schematic flow chart diagram of another embodiment of a data cleansing method provided in the present specification. Specifically, when the detection result in step S108 is yes, it may be determined that the service data corresponding to the first thread context data is the service data of the current service request; correspondingly, on the basis of the embodiment shown in fig. 1, the method may further include:
s112: and executing the service request according to the service data of the current service request.
In other embodiments, the method may further comprise:
and generating second thread context data according to the service data of the service request.
In other embodiments, the method further comprises:
and generating context data of the third thread according to the service data of the service request and the corresponding identification information.
Specifically, in this embodiment of the present specification, the generating method of the second thread context data and the third thread context data may refer to the generating step of the thread context data, and is not described herein again.
In addition, the steps of generating the second thread context data according to the service data of the service request and generating the third thread context data according to the service data of the service request and the corresponding identification information may be before step S108 or after step S108.
In a specific embodiment, when the steps of generating the second thread context data according to the service data of the service request and generating the third thread context data according to the service data of the service request and the corresponding identification information are performed before step S108, the detecting whether the identification information of the first thread context data is consistent with the identification information of the service data may include:
detecting whether the identification information of the first thread context data is consistent with the identification information of the second thread context data;
and/or the presence of a gas in the gas,
detecting whether the identification information of the first thread context data is consistent with the identification information of the third thread context data.
After the current service request processing is finished, the second thread context data and the third thread context data may be used as the first thread context data of the corresponding execution thread.
In other embodiments, as shown in fig. 3, fig. 3 is a schematic flow chart diagram of another embodiment of a data cleansing method provided in the present specification. Specifically, in some scenarios, after the execution thread is created for the current service request, when thread context data corresponding to the current service data is not generated in the memory of the execution thread, and thread context data corresponding to the service data of the completed service request is not generated, the first thread context data of the execution thread acquired in step S106 may be null. Correspondingly, the method may further comprise:
s114: judging whether the first thread context data is empty or not;
s116: and when the judgment result is negative, executing detection to determine whether the identification information of the first thread context data is consistent with the identification information of the service data.
In still other embodiments, the method may further comprise:
and when the judgment result is yes, executing the service request according to the service data.
In practical applications, after the execution of the service request is completed, the context data of the corresponding service thread can be directly cleaned.
Therefore, in one or more embodiments of the data cleaning method in this specification, identification information is set for service data of a currently received service request, and it can be detected whether thread context data that has been executed and is not cleaned in time exists in a memory through the identification information, and when it is detected that the thread context data that is not cleaned in time exists in the memory, the thread context data can be cleaned in time, so that the problem of accumulation of memory leakage during a thread running process is avoided.
In another aspect of the present specification, a data cleansing apparatus is further provided, and fig. 4 is a schematic structural diagram of an embodiment of the data cleansing apparatus provided in the specification, and as shown in fig. 4, the apparatus 400 may include:
a service request receiving module 410, configured to receive a service request;
an identification information setting module 420, which may be configured to set identification information of service data of the service request;
an execution thread creating module 430, configured to create an execution thread of the service request;
a thread context data obtaining module 440, configured to obtain first thread context data of the execution thread;
an identification information detection module 450, configured to detect whether the identification information of the first thread context data is consistent with the identification information of the service data;
the data cleaning module 460 may be configured to clean the first thread context data of the execution thread when the result detected by the identification information detecting module is negative.
The present specification further provides another embodiment of a data cleansing apparatus, as shown in fig. 5, fig. 5 is a schematic structural diagram of another embodiment of the data cleansing apparatus provided in the present specification, and on the basis of the embodiment shown in fig. 4, the apparatus 400 may further include:
the first service request executing module 470 may be configured to, when the result detected by the identification information detecting module is yes, execute the service request according to the service data.
In another embodiment, the apparatus 400 may further include:
the first data generation module may be configured to generate second thread context data according to the service data of the service request.
In another embodiment, the apparatus 400 may further include:
the second data generating module may be configured to generate third thread context data according to the service data of the service request and the corresponding identification information.
In another embodiment, the apparatus 400 may further include:
the judging module can be used for judging whether the first thread context data is empty or not;
and the data processing module may be configured to, when the result of the determining module is negative, perform detection on whether the identification information of the first thread context data is consistent with the identification information of the service data.
In another embodiment, the apparatus 400 may further include:
the second service request execution module may be configured to execute the service request according to the service data when the result of the determination is yes.
The data cleaning method or apparatus provided in the embodiments of the present specification may be implemented in a computer by a processor executing corresponding program instructions, for example, implemented at a PC end using a c + + language of a windows operating system, or implemented at an intelligent terminal using android, iOS system programming languages, or implemented based on processing logic of a quantum computer. As shown in fig. 6, fig. 6 is a schematic configuration diagram of a data cleansing server according to an exemplary embodiment of the present specification. On the hardware level, the server may include a processor, an internal bus, a network interface, a memory, and a non-volatile memory, but may also include hardware required for other services. The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program to form the data cleaning device on the logic level. Of course, besides the software implementation, the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Specifically, another aspect of the present specification further provides a data cleansing server, including a processor and a memory, where the memory stores computer program instructions executed by the processor, and the computer program instructions may include:
receiving a service request, and setting identification information of service data of the service request;
creating an execution thread of the service request, and acquiring first thread context data of the execution thread;
detecting whether the identification information of the first thread context data is consistent with the identification information of the service data;
and when the detection result is negative, cleaning the first thread context data of the execution thread.
In the embodiment of the present disclosure, the processor may include a Central Processing Unit (CPU) or a Graphics Processing Unit (GPU), and may also include other single-chip microcomputers, logic gates, integrated circuits, and the like with logic processing capability, or a suitable combination thereof. The memory according to the embodiment of the present application may be a memory device for storing information. In a digital system, the device capable of storing binary data may be a memory; in an integrated circuit, a circuit without an actual form and with a storage function can also be a memory, such as a RAM, a FIFO and the like; in the system, the storage device in physical form may also be called a memory or the like. When the method is implemented, the memory can also be implemented in a cloud memory mode, and the specific implementation mode is not limited in this specification.
Therefore, in the embodiments of the data cleaning method, apparatus, or server in this specification, identification information is set for service data of a currently received service request, and it can be detected whether thread context data that has been executed and is not cleaned in time exists in a memory through the identification information, and when it is detected that the thread context data that is not cleaned in time exists in the memory, the thread context data can be cleaned in time, so that the problem of accumulation of memory leakage during a thread operation processing process is avoided.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical blocks. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The apparatuses, modules or units illustrated in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, apparatus or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the device and server embodiments, since they are substantially similar to the method embodiments, the description is simple, and the relevant points can be referred to the partial description of the method embodiments.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present specification should be included in the scope of the claims.
Claims (13)
1. A method of data scrubbing, comprising:
receiving a service request, and setting identification information of service data of the service request;
creating an execution thread of the service request, and acquiring first thread context data of the execution thread; wherein the first thread context data is generated according to corresponding service data;
detecting whether the identification information of the first thread context data is consistent with the identification information of the service data;
and when the detection result is negative, cleaning the first thread context data of the execution thread.
2. The method of claim 1, wherein the method further comprises:
and when the detection result is yes, executing the service request according to the service data.
3. The method according to claim 1 or 2, wherein the method further comprises:
and generating second thread context data according to the service data of the service request.
4. The method according to claim 1 or 2, wherein the method further comprises:
and generating context data of the third thread according to the service data of the service request and the corresponding identification information.
5. The method according to claim 1 or 2, wherein the method further comprises:
judging whether the first thread context data is empty or not;
and when the judgment result is negative, executing detection to determine whether the identification information of the first thread context data is consistent with the identification information of the service data.
6. The method of claim 5, wherein the method further comprises:
and when the judgment result is yes, executing the service request according to the service data.
7. A data cleansing apparatus comprising:
a service request receiving module, configured to receive a service request;
an identification information setting module, configured to set identification information of service data of the service request;
the execution thread creating module is used for creating an execution thread of the service request;
a thread context data obtaining module, configured to obtain first thread context data of the execution thread; wherein the first thread context data is generated according to corresponding service data; an identification information detection module, configured to detect whether identification information of the first thread context data is consistent with identification information of the service data;
and the data cleaning module is used for cleaning the first thread context data of the execution thread when the detection result of the identification information detection module is negative.
8. The apparatus of claim 7, wherein the apparatus further comprises:
and the first service request execution module is used for executing the service request according to the service data when the detection result of the identification information detection module is positive.
9. The apparatus of claim 7 or 8, wherein the apparatus further comprises:
and the first data generation module is used for generating second thread context data according to the service data of the service request.
10. The apparatus of claim 7 or 8, wherein the apparatus further comprises:
and the second data generation module is used for generating third thread context data according to the service data of the service request and the corresponding identification information.
11. The apparatus of claim 7 or 8, wherein the apparatus further comprises:
the judging module is used for judging whether the first thread context data is empty or not;
and the data processing module is used for detecting whether the identification information of the first thread context data is consistent with the identification information of the service data or not when the judgment result of the judging module is negative.
12. The apparatus of claim 11, wherein the apparatus further comprises:
and the second service request execution module is used for executing the service request according to the service data when the judgment result is yes.
13. A data cleansing server comprising a processor and a memory, the memory storing computer program instructions for execution by the processor, the computer program instructions comprising:
receiving a service request, and setting identification information of service data of the service request;
creating an execution thread of the service request, and acquiring first thread context data of the execution thread; wherein the first thread context data is generated according to corresponding service data;
detecting whether the identification information of the first thread context data is consistent with the identification information of the service data;
and when the detection result is negative, cleaning the first thread context data of the execution thread.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810191254.4A CN108536613B (en) | 2018-03-08 | 2018-03-08 | Data cleaning method and device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810191254.4A CN108536613B (en) | 2018-03-08 | 2018-03-08 | Data cleaning method and device and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108536613A CN108536613A (en) | 2018-09-14 |
| CN108536613B true CN108536613B (en) | 2022-09-16 |
Family
ID=63486645
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810191254.4A Active CN108536613B (en) | 2018-03-08 | 2018-03-08 | Data cleaning method and device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108536613B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109634845B (en) * | 2018-11-13 | 2022-05-17 | 微梦创科网络科技（中国）有限公司 | Method and device for generating context record text |
| CN109582685B (en) * | 2018-12-03 | 2023-01-10 | 武芮 | Method and device for recording context request execution process |
| CN110309172B (en) * | 2019-06-06 | 2023-08-22 | 创新先进技术有限公司 | Data calculation method, system, device and electronic equipment |
Family Cites Families (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1842770A (en) * | 2003-08-28 | 2006-10-04 | 美普思科技有限公司 | Integrated mechanism for suspension and deallocation of computational threads of execution in a processor |
| CN100456260C (en) * | 2006-12-21 | 2009-01-28 | 华为技术有限公司 | Interpreter language debugging method and device |
| CN101441560B (en) * | 2007-11-23 | 2012-09-26 | 国际商业机器公司 | Method for performing service-oriented architecture strategy based on context model and strategy engine |
| US7921195B2 (en) * | 2008-06-09 | 2011-04-05 | International Business Machines Corporation | Optimizing service processing based on business information, operational intelligence, and self-learning |
| CN101854311A (en) * | 2009-03-31 | 2010-10-06 | 国际商业机器公司 | Method and device for transmitting context information on web server |
| CN101710303B (en) * | 2009-12-01 | 2011-07-27 | 中国人民解放军国防科学技术大学 | Memory leakage detecting method based on flow sensitivity and context sensitivity directing picture |
| CN102209016B (en) * | 2010-03-29 | 2014-02-26 | 成都市华为赛门铁克科技有限公司 | Data processing method, device and data processing system |
| US9141526B2 (en) * | 2010-09-16 | 2015-09-22 | International Business Machines Corporation | Reclaiming units by searching units for a predetermined criterion and storing data from a valid subunit |
| CN102217357B (en) * | 2011-05-20 | 2013-10-09 | 华为技术有限公司 | Method, apparatus, and system for controlling business |
| US9075712B2 (en) * | 2011-11-30 | 2015-07-07 | International Business Machines Corporation | Scheduling requests in a solid state memory device |
| CN103188738B (en) * | 2011-12-27 | 2015-11-25 | 华为技术有限公司 | resource allocation method, device and system |
| WO2014000785A1 (en) * | 2012-06-27 | 2014-01-03 | Qatar Foundation | A method for cleaning data records in a database |
| CN105630512A (en) * | 2016-02-17 | 2016-06-01 | 北京高绎信息技术有限公司 | Method and system for implementing mobile device data tracking through software development toolkit |
| CN107368406A (en) * | 2016-05-11 | 2017-11-21 | 阿里巴巴集团控股有限公司 | The method, apparatus and equipment of test application program |
| CN106095689B (en) * | 2016-06-24 | 2019-02-12 | 北京奇虎科技有限公司 | A kind of detection method and device of application memory leakage |
| CN106899666B (en) * | 2017-02-21 | 2019-12-24 | 阿里巴巴集团控股有限公司 | Data processing method and device for service identification |
-
2018
- 2018-03-08 CN CN201810191254.4A patent/CN108536613B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108536613A (en) | 2018-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108536613B (en) | Data cleaning method and device and server | |
| CN107066519B (en) | Task detection method and device | |
| CN108268289B (en) | Parameter configuration method, device and system for web application | |
| TW201913449A (en) | Target image code recognition method and device | |
| CN109104327B (en) | Service log generation method, device and equipment | |
| CN109947643B (en) | A/B test-based experimental scheme configuration method, device and equipment | |
| CN110781016B (en) | Data processing method, device, equipment and medium | |
| TWI684916B (en) | Function selection method and server | |
| US20230367701A1 (en) | Code testing method and apparatus | |
| WO2024051270A1 (en) | Task execution method, apparatus, storage medium, and electronic device | |
| CN110635962A (en) | Abnormity analysis method and device for distributed system | |
| CN114115016A (en) | Data processing method, device, equipment and medium | |
| US11164056B2 (en) | Method and system for applying barcode, and server | |
| CN111753328B (en) | Private data leakage risk detection method and system | |
| CN108470242B (en) | Risk management and control method, device and server | |
| CN111078435A (en) | Service processing method and device and electronic equipment | |
| CN113902356B (en) | Regional flow data analysis method and device | |
| CN107645541B (en) | Data storage method and device and server | |
| CN107135137B (en) | Network group identification method and device | |
| CN108647113B (en) | Disaster recovery method and server | |
| CN110737524B (en) | Task rule management method, device, equipment and medium | |
| CN109325127B (en) | Risk identification method and device | |
| CN111967769A (en) | Risk identification method, device, equipment and medium | |
| CN116893663B (en) | Main control abnormality detection method and device, storage medium and electronic equipment | |
| CN112711539A (en) | Data processing method and device and data detection system |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200927 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200927 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: Greater Cayman, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |