CN116578618A - Method, device, storage medium and electronic device for generating target reflow instances - Google Patents

Abstract

This application discloses a method, device, storage medium, and electronic device for generating a target return instance, and relates to the field of smart home technology. The method for generating a target return instance includes: when it is determined that a service message that fails to process a service is detected, Determine the initial reflow instance corresponding to the business message, wherein the initial reflow instance is a reflow instance without reflow configuration; in response to the configuration instruction of the target object, determine from the preset configuration library for configuring the reflow instance instance configuration information, and use the configuration information to configure the initial reflow instance to generate a target reflow instance, wherein the target reflow instance is used to determine a reflow processing result after reflow processing is performed on the business message.

Description

Method, device, storage medium and electronic device for generating target reflow instances

technical field

The present application relates to the technical field of smart home, in particular, to a method, device, storage medium and electronic device for generating a target reflow instance.

Background technique

At present, as the level of intelligence of home appliances in the field of smart home appliances is getting higher and higher, the home appliance functions provided by home appliances are becoming more and more diversified. Correspondingly, the number of home appliance business messages is also increasing. In the scheme, due to the order dependence of the messages of the ETL real-time stream, when processing the messages of different ETL real-time streams of home appliances, the out-of-order input messages may cause data processing failure, and the data that fails to be processed needs to be reflowed. Currently, for various reflow data that fail to be processed, the reflow instance is generally manually configured for each type of reflow data that fails to process. However, this manually configured reflow instance can only adapt to a single data type and is limited by labor costs. Data reflow processing is inefficient.

Therefore, in the related art, there is a technical problem that manually configured reflow instances lead to low efficiency of data reflow processing.

In the related art, how to solve the technical problem of inefficiency in data reflow processing caused by manually configured reflow instances has not yet been proposed an effective solution.

Contents of the invention

Embodiments of the present application provide a method, device, storage medium, and electronic device for generating a target reflow instance, so as to at least solve the technical problem in the related art of how to solve the low efficiency of data reflow processing caused by manually configured reflow instances.

According to an embodiment of the embodiment of the present application, a method for generating a target return instance is provided, including: determining the initial return instance corresponding to the service message when it is determined that a business message that fails to process the service is detected, wherein , the initial reflow instance is a reflow instance without reflow configuration; in response to the configuration instruction of the target object, the configuration information used to configure the reflow instance is determined from the preset configuration library, and the configuration information is used to configure the reflow instance The initial reflow instance is configured to generate a target reflow instance, wherein the target reflow instance is used to determine a reflow processing result after reflow processing is performed on the business message.

In an exemplary embodiment, after using the configuration information to configure the initial reflow instance to generate a target reflow instance, the method further includes: after determining that the instance status of the target reflow instance indicates that the target When the reflow instance has been enabled, create the first client corresponding to the target reflow instance; respond to the query instruction of the first client, obtain the instance name contained in the query instruction; If the instance names of the target reflow instances are the same, send the reflow parameters of the target reflow instance to the first client.

In an exemplary embodiment, after sending the reflow parameter of the target reflow instance to the first client, the method further includes: if receiving the first If a notification message is received, it is determined that the result of the reflow processing is not completed; if a second notification message from the first client indicating to end the reflow is received, it is determined that the result of the reflow processing is completed.

In an exemplary embodiment, sending the reflow parameter of the target reflow instance to the first client includes: determining a first message middleware interface corresponding to the target reflow instance; The software interface establishes a first message channel for transmitting the backflow parameters; the backflow parameters are sent to the first client through the first message channel; wherein, the first message middleware interface allows docking with different Middleware type client.

In an exemplary embodiment, after using the configuration information to configure the initial reflow instance to generate a target reflow instance, the method further includes: after determining that the instance status of the target reflow instance indicates that the target When the reflow instance has been enabled, create a second client corresponding to the target reflow instance; obtain the query result of the second client for the business message; determine that the query result indicates that the business message exists In the case of a service message to be reflowed, if it is determined that there is a corresponding relationship between the service message to be reflowed and the target reflow instance, it is determined that the reflow processing result is not completed.

In an exemplary embodiment, obtaining the query result of the service message from the second client includes: determining the second message middleware interface corresponding to the target reflow instance; based on the second message middleware interface Establishing a second message channel for transmitting the query result; receiving the query result transmitted through the second message channel; wherein, the second message middleware interface allows docking with clients of different middleware types.

In an exemplary embodiment, after using the configuration information to configure the initial reflow instance to generate a target reflow instance, the method further includes: after determining that the instance status of the target reflow instance indicates that the target reflow instance When the instance is terminated, the first client corresponding to the target reflow instance is destroyed; if a third notification message indicating that the first client is destroyed successfully is received, it is determined that the reflow processing result is completed.

In an exemplary embodiment, after using the configuration information to configure the initial reflow instance to generate a target reflow instance, the method further includes: after determining that the instance status of the target reflow instance indicates that the target reflow instance When the instance is terminated, the second client corresponding to the target reflow instance is destroyed; if a fourth notification message indicating that the second client is destroyed successfully is received, it is determined that the reflow processing result is completed.

In an exemplary embodiment, using the configuration information to configure the initial reflow instance includes: determining the preset reflow times of the initial reflow instance from the preset configuration library, and the initial reflow instance The initial backflow time interval; in the case of determining that the preset number of backflows is not greater than the preset threshold, set the incremental time of the backflow interval based on the difference between the preset number of backflows and the preset threshold, and according to the initial The sum of the backflow time interval and the increment time determines the backflow time interval of the target backflow instance; when it is determined that the preset number of backflow times is greater than a preset threshold, the backflow interval is set as the default increment time , and determine the reflow time interval of the target reflow instance according to the sum of the initial reflow time interval and the default increment time.

According to another aspect of the embodiment of the present application, there is also provided a device for generating a target return instance, which is characterized in that it includes: a determining module, configured to determine the out of the The initial reflow instance corresponding to the above business message, wherein, the initial reflow instance is a reflow instance without reflow configuration; the configuration module is used to determine from the preset configuration library in response to the configuration instruction of the target object. configuration information of the reflow instance described above, and use the configuration information to configure the initial reflow instance to generate a target reflow instance, wherein the target reflow instance is used to determine the reflow processing after the reflow processing is performed on the business message result.

According to yet another aspect of the embodiments of the present application, a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the above-mentioned target reflow instance when running generation method.

According to yet another aspect of the embodiments of the present application, there is also provided an electronic device, including a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the above-mentioned processor executes the above-mentioned Generate method for target reflow instance.

In the embodiment of the present application, when it is determined that a business message that fails to process a business is detected, the initial reflow instance corresponding to the business message can be determined; then, in response to the configuration instruction of the target object, it can be determined from the preset configuration library Obtain configuration information for configuring the reflow instance, and use the configuration information to configure the initial reflow instance, so as to generate a target reflow instance for determining a reflow processing result after reflow processing is performed on the business message; By adopting the above technical solution, the technical problem of low efficiency of data reflow processing caused by manually configured reflow instances is solved, thereby improving the efficiency of data reflow processing.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application.

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, In other words, other drawings can also be obtained from these drawings without paying creative labor.

FIG. 1 is a schematic diagram of a hardware environment of a method for generating a target reflow instance according to an embodiment of the present application;

FIG. 2 is a flowchart of a method for generating a target reflow instance according to an embodiment of the present application;

FIG. 3 is a schematic flow diagram of processing a reflow message using a target reflow instance according to an embodiment of the present application;

FIG. 4 is a schematic diagram of the number of retries according to an embodiment of the present application;

FIG. 5 is a structural block diagram (1) of a generating device for a target reflow example according to an embodiment of the present application;

Fig. 6 is a structural block diagram (2) of a device for generating a target reflow example according to an embodiment of the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiment of the application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiment of the application. Obviously, the described embodiment is only It is an embodiment of a part of the application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

It should be noted that the terms "first" and "second" in the description and claims of the present application and the above drawings are used to distinguish similar objects, but not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the application described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device comprising a sequence of steps or elements is not necessarily limited to the expressly listed instead, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus.

Next, some technical terms of the embodiments of the present application are explained by the following examples:

MQ: The full name is Message Queue, message queue middleware, used to provide message subscription, storage, publishing and other functions, such as Kafka, RocketMQ, etc. Among them, some types of MQ clients only support a limited number of repeated delivery.

A real-time computing framework that performs data ETL processing on real-time consumption messages, such as Flink and Spark.

ETL: Used to describe the process of extracting, transforming, and loading data from the source to the destination.

According to an aspect of the embodiments of the present application, a method for generating a target reflow instance is provided. The generation method of the target reflow instance is widely used in smart home (Smart Home), smart home, smart home equipment ecology, smart house (Intelligence House) ecology and other intelligent digital control application scenarios in the whole house. Optionally, in this embodiment, the above-mentioned method for generating a target reflow instance may be applied to a hardware environment composed of a terminal device 102 and a server 104 as shown in FIG. 1 . As shown in Figure 1, the server 104 is connected to the terminal device 102 through the network, and can be used to provide services (such as application services, etc.) for the terminal or the client installed on the terminal. To provide data storage services for the server 104, cloud computing and/or edge computing services may be configured on the server or independently of the server to provide data computing services for the server 104.

The foregoing network may include but not limited to at least one of the following: a wired network and a wireless network. The above-mentioned wired network may include but not limited to at least one of the following: wide area network, metropolitan area network, and local area network, and the above-mentioned wireless network may include but not limited to at least one of the following: WIFI (Wireless Fidelity, Wireless Fidelity), Bluetooth. The terminal device 102 is not limited to PC, mobile phone, tablet computer, smart air conditioner, smart hood, smart refrigerator, smart oven, smart stove, smart washing machine, smart water heater, smart washing device, smart dishwasher, smart projection device , smart TV, smart drying rack, smart curtain, smart video, smart socket, smart audio, smart speaker, smart fresh air equipment, smart kitchen and bathroom equipment, smart bathroom equipment, smart sweeping robot, smart window cleaning robot, smart mopping robot, Smart air purification equipment, smart steamer, smart microwave oven, smart kitchen treasure, smart purifier, smart water dispenser, smart door lock, etc.

In this embodiment, a method for generating a target reflow instance is provided, which is applied to the above-mentioned terminal device. FIG. 2 is a flowchart of a method for generating a target reflow instance according to an embodiment of the present application. The process includes the following steps:

Step S202, if it is determined that a business message that fails to process a service is detected, determine an initial reflow instance corresponding to the business message, wherein the initial reflow instance is a reflow instance that has not been configured for reflow;

Step S204, in response to the configuration instruction of the target object, determine configuration information for configuring the reflow instance from the preset configuration library, and use the configuration information to configure the initial reflow instance to generate a target reflow instance , wherein the target reflow instance is used to determine a reflow processing result after reflow processing is performed on the service message.

Through the above steps, in the case of detecting a business message that fails to process the business, determine the initial reflow instance corresponding to the business message; then, in response to the configuration instruction of the target object, determine from the preset configuration library for Configure the configuration information of the reflow instance, and use the configuration information to configure the initial reflow instance, so as to generate a target reflow instance for determining the reflow processing result after reflow processing the business message; adopt the above technology The solution solves the technical problem of low efficiency of data reflow processing caused by manually configured reflow instances, thereby improving the efficiency of data reflow processing.

In an exemplary embodiment, after the configuration information is used to configure the initial reflow instance in the above step S204 to generate the scheme of the target reflow instance, the instance status indication of the target reflow instance may also be determined When the target reflow instance has been enabled, create the first client corresponding to the target reflow instance; respond to the query instruction of the first client, obtain the instance name contained in the query instruction; determine the instance If the name is consistent with the instance name of the target reflow instance, send the reflow parameters of the target reflow instance to the first client.

Wherein, it should be noted that, the above-mentioned reflow parameters may include, for example, the number of reflow times, the time interval of reflow, etc., but are not limited thereto.

In an exemplary embodiment, after the reflow parameter of the target reflow instance is sent to the first client, the following technical solution is further proposed: For the first notification message, it is determined that the result of the reflow processing is not completed; if the second notification message used by the first client to indicate the end of reflow is received, it is determined that the result of the reflow processing is completed.

In an exemplary embodiment, the implementation process of sending the reflow parameters of the target reflow instance to the first client is described through the following steps, specifically including: determining the first message middleware corresponding to the target reflow instance interface; establish a first message channel for transmitting the return parameter based on the first message middleware interface; send the return parameter to the first client through the first message channel; wherein, the The first message middleware interface allows connecting clients of different middleware types.

In an exemplary embodiment, further, after using the configuration information to configure the initial reflow instance to generate a target reflow instance, the following technical solution is also proposed: after determining the instance state of the target reflow instance In the case of indicating that the target backflow instance has been enabled, create a second client corresponding to the target backflow instance; obtain the query result of the second client for the business message; determine that the query result indicates the If there is a service message to be reflowed in the service message, if it is determined that there is a corresponding relationship between the service message to be reflowed and the target reflow instance, it is determined that the reflow processing result is not completed.

Optionally, in a case where it is determined that the query result indicates that there is no service message to be reflowed in the service message, it is determined that the reflow processing result is completed.

In an exemplary embodiment, it further proposes an implementation process of obtaining the query result of the service message from the second client, which specifically includes the following steps: determining the second message middleware interface corresponding to the target reflow instance; Establish a second message channel for transmitting the query result based on the second message middleware interface; receive the query result transmitted through the second message channel; wherein, the second message middleware interface allows docking Clients for different middleware types.

In an exemplary embodiment, after using the configuration information to configure the initial reflow instance to generate a target reflow instance, other technical solutions are further proposed, and the specific steps include: determining the instance of the target reflow instance If the state indicates that the target reflux instance is finished enabling, destroy the first client corresponding to the target reflux instance; if a third notification message indicating that the first client is destroyed successfully is received, then determine the The reflow processing result is complete.

In an exemplary embodiment, further, after using the configuration information to configure the initial reflow instance to generate a target reflow instance, after determining that the instance status indicates that the target reflow instance has ended activation Next, destroy the second client corresponding to the target reflow instance; if a fourth notification message indicating that the second client is destroyed successfully is received, it is determined that the reflow processing result is completed.

In an exemplary embodiment, the process of using the configuration information to configure the initial reflow instance in the above step S206 specifically includes the following steps: determining the configuration of the initial reflow instance from the preset configuration library The preset number of backflows, the initial backflow time interval of the initial backflow instance; when it is determined that the preset number of backflows is not greater than a preset threshold, set the The incremental time of the backflow interval time, and determine the backflow time interval of the target backflow instance according to the sum of the initial backflow time interval and the incremental time; when it is determined that the preset number of backflow times is greater than the preset threshold value, the The reflow interval time is set as a default increment time, and the reflow time interval of the target reflow instance is determined according to the sum of the initial reflow time interval and the default increment time.

Wherein, in the process of setting the incremental time of the backflow interval based on the difference between the preset number of backflows and the preset threshold value, for example, the incremental time of the backflow interval can be set to increase with the preset number of backflows and the preset threshold. The difference between the thresholds increases, or the increment time of the backflow interval can also be set to decrease as the difference between the preset number of backflows and the preset threshold decreases, which is not limited in the present application.

In an optional embodiment, the preset number of reflows may also be directly determined as the number of reflows of the target reflow instance.

In order to better understand the process of the method for generating the above-mentioned target reflow instance, the flow of the implementation method for generating the above-mentioned target reflow instance will be described below in combination with optional embodiments, but it is not intended to limit the technical solutions of the embodiments of the present application.

In this embodiment, a method for processing reflow messages using a target reflow instance is provided. FIG. 3 is a schematic flow diagram of using a target reflow instance to process reflow messages in the embodiment of the present application. As shown in FIG. 3 , it includes the following modules:

Module 1, reflux-config, message reflux policy configuration module, used to provide message reflux policy query, configuration, start and stop functions; after the reflux instance (that is, the above target reflux instance) is started and stopped: notify reflux-processor to create or destroy the reflux Instance message consumption client; notify reflux-scheduler to create or destroy the reflux instance message sending client.

Wherein, the above-mentioned module 1 is also used to configure the above-mentioned target reflow instance.

Module 2, reflux-core, the core module of the message reflux system, is used to provide a unified message consumption and production interface, realize different types of MQ middleware sending and receiving messages, and provide it in the form of SDK.

Module 3, reflux-processor, the message reflux system processing module, is used to monitor the messages to be reflux sent by the business process, judge whether the message needs to continue to reflux according to the reflux strategy, calculate the time of the next reflux, and persist it in the DB. Message consumption depends on the unified message consumption interface provided by reflux-core.

Module 4, reflux-scheduler, the reflux message sending scheduler module, is used to circularly query the messages to be reflux and push them to MQ. Message push depends on the unified message production interface provided by reflux-core.

Module 5, reflux-search, the problem traceability module, is used to support the retrieval of data that has not been processed normally after exceeding the number of reflows, and is used for problem traceability.

The specific implementation process is as follows:

Step 1. In the business upstream message queue, the upstream original business message is as follows:

Step 2, business logic processing, that is, start to consume the messages of the message queue in step 1, and do business processing.

In step 3, it is determined that the service processing is successful.

Step 4. Determine that the business processing fails, and encapsulate the original message into a return message, and then push it to the message queue in step 5.

Among them, it should be noted that other data relied on in step 2 may fail in the final business processing due to reasons such as delay, failure to find the processing result, or abnormal program processing.

In one embodiment, the procedure for encapsulating the original message into a data reflow message body (that is, the above-mentioned message to be reflowed) is as follows:

Step 5. Store the return message pushed after the business processing is abnormal.

Step 6. The message return system consumes the message msg to be returned in the message queue in step 5.

Step 7: Parse the message msg to be reflowed to obtain the reflow instance name caseName and the original message body message.

Step 8. According to the backflow instance name caseName parsed in step 7, query the backflow policy cache, obtain the backflow policy configuration of the backflow instance, and calculate the upper limit of the backflow times of the backflow instance.

Step 9. Calculate the number of reflux times: parse the number of times the message has been refluxed from the message body to be refluxed, that is, reflux.times. The message body to be refluxed is as follows:

Step 10. According to the number of reflows calculated in step 9 and the upper limit of the number of reflows calculated in step 8, it is judged whether to continue the reflow.

Step 11. If it is necessary to continue the reflow, calculate the next reflow time and persist it in the DB: calculate the next reflow time according to the reflow strategy obtained in step 8, and add 1 to the reflow times calculated in step 9 before backfilling Into the original message, the structure that is finally persisted in the DB is as follows:

Step 12. If the reflow does not need to be continued, that is, the reflow is stopped, the original message body in step 7 is saved in the exception data table corresponding to the reflow instance for traceability and query of business problems.

Further, reflow can also be realized through scheduled tasks, specifically:

Step 13. Trigger the timed task of each reflow instance.

Step 14, the scheduled task will cyclically query the original message to be reflowed in the DB.

Step 15. Call the unified message sending interface provided by reflux-core, and push the queried data to be returned to the message queue in step 16.

Step 16, the business process will continue to consume the MQ.

It should be noted that the configuration process of the backflow policy can also be implemented through the following steps:

Step 17. Create a reflow instance configuration.

Step 18. Query the configuration details of the reflow instance.

Step 19. Enable or disable the reflow instance configuration.

Step 20, when the reflux instance is enabled: reflux-processor and reflux-scheduler need to be notified to create an MQ client, which is the unified message production and sending interface provided by reflux-core.

Step 21. When the reflux instance is closed: reflux-processor and reflux-scheduler need to be notified to destroy the MQ client, which is the unified message production and sending interface provided by reflux-core.

Further, in one embodiment, as shown in Figure 4, the message backflow system can support multiple backflows. When configuring the backflow instance, you can configure the maximum number of retries. The default value is 16 times. There is no maximum value for this parameter. It is recommended to use the default value. The interval time changes step by step according to the number of retries, and the value ranges from 1 second to 2 hours. If the maximum number of retries is less than or equal to 16 times, the interval time will be changed stepwise according to the retry interval time of out-of-order messages. If the maximum number of retries is greater than 16, the interval between retries exceeding 16 is 2 hours.

Through the above-mentioned embodiments, in this application, the logic of sending and receiving messages of different types of MQs is implemented inside the message return system, and the message return is realized by using the return flow instance, so as to re-process the abnormal message after processing (that is, the business message that the above-mentioned business processing failed). Throwing, and based on the function of abnormal data persistence, the message that still fails to be processed after re-throwing is permanently persisted. At the same time, it can provide retrieval for the persisted message to realize the source of the problem. In addition, in view of the problem that the current message backflow mechanism does not support dynamic adjustment of the backflow strategy, this application can update the configuration according to the latest configuration data in the database every once in a while after updating the backflow strategy, so that there is no need to restart the business ETL process. Next, realize the dynamic adjustment of the configuration.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is Better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to make a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) execute the method of each embodiment of the present application.

Fig. 5 is a structural block diagram (1) of a generating device of a target reflow example according to an embodiment of the present application; as shown in Fig. 5 , it includes:

The determining module 42 is configured to determine an initial reflow instance corresponding to the business message when it is determined that a business message that fails to be processed is detected, wherein the initial reflow instance is a reflow instance that has not been configured for reflow;

The configuration module 44 is configured to determine the configuration information used to configure the reflow instance from the preset configuration library in response to the configuration instruction of the target object, and use the configuration information to configure the initial reflow instance to generate A target reflow instance, wherein the target reflow instance is used to determine a reflow processing result after reflow processing is performed on the service message.

Through the above-mentioned device, when it is determined that a business message that fails to process a business is detected, the initial reflow instance corresponding to the business message is determined; and then in response to the configuration instruction of the target object, it is determined from the preset configuration library for configuration configuration information of the reflow instance, and use the configuration information to configure the initial reflow instance to generate a target reflow instance for determining a reflow processing result after reflow processing is performed on the business message. In related technologies, the technical problem of low efficiency of data reflow processing caused by manually configured reflow instances is solved, thereby improving the efficiency of data reflow processing.

In an exemplary embodiment, the above-mentioned device for generating a target reflow instance further includes: a first creation module, configured to create the target reflow instance when it is determined that the instance status of the target reflow instance indicates that the target reflow instance The first client corresponding to the target reflow instance; in response to the query instruction of the first client, obtain the instance name contained in the query instruction; when it is determined that the instance name is consistent with the instance name of the target reflow instance , sending the reflow parameters of the target reflow instance to the first client.

In an exemplary embodiment, the above-mentioned first creation module is further configured to: determine that the result of the reflow process is incomplete if the first notification message from the first client indicating to continue the reflow process is received; if After receiving the second notification message from the first client indicating to end the reflow, it is determined that the reflow processing result is completed.

In an exemplary embodiment, the above-mentioned first creation module is further configured to: determine the first message middleware interface corresponding to the target reflow instance; establish a method for transmitting the reflow parameter based on the first message middleware interface The first message channel; the return parameter is sent to the first client through the first message channel; wherein, the first message middleware interface allows docking with clients of different middleware types.

In an exemplary embodiment, the above-mentioned device for generating a target reflow instance further includes: a second creation module configured to: create the target reflow instance when it is determined that the instance status of the target reflow instance indicates that the target reflow instance has been enabled the second client corresponding to the target reflow instance; obtain the query result of the service message from the second client; if it is determined that the query result indicates that there is a service message to be processed in the service message, If it is determined that there is a corresponding relationship between the service message to be reflow processed and the target reflow instance, it is determined that the reflow processing result is not completed.

In an exemplary embodiment, the above-mentioned second creation module is further configured to: determine the second message middleware interface corresponding to the target reflow instance; establish a message for transmitting the query result based on the second message middleware interface The second message channel; receiving the query result transmitted through the second message channel; wherein, the second message middleware interface allows docking with clients of different middleware types.

In an exemplary embodiment, the above-mentioned device for generating a target reflow instance further includes: a first destruction module configured to destroy the target reflow instance when it is determined that the instance status of the target reflow instance indicates that the The first client corresponding to the target reflow instance; if a third notification message indicating that the first client is destroyed successfully is received, it is determined that the reflow processing result is completed.

In an exemplary embodiment, further, the above-mentioned device for generating a target reflow instance further includes: a second destruction module, configured to, when it is determined that the instance state of the target reflow instance indicates that the target reflow instance has ended activation, Destroy the second client corresponding to the target reflow instance; if a fourth notification message indicating that the second client is destroyed successfully is received, determine that the reflow processing result is completed.

Fig. 6 is a structural block diagram (2) of a device for generating a target reflow example according to an embodiment of the present application; as shown in Fig. 6, the above-mentioned configuration module 44 includes: a setting unit 52 for selecting from the preset configuration library Determine the preset number of reflows of the initial reflow instance, the initial reflow time interval of the initial reflow instance; when it is determined that the preset number of reflows is not greater than a preset threshold, based on the preset number of reflows and the preset Set the increment time of the backflow interval time by setting the difference of the threshold value, and determine the backflow time interval of the target backflow instance according to the sum value of the initial backflow time interval and the increment time; when determining that the preset number of backflow times is greater than In the case of a preset threshold, the reflow interval is set as a default increment time, and the reflow time interval of the target reflow instance is determined according to the sum of the initial reflow time interval and the default increment time.

An embodiment of the present application further provides a storage medium, the storage medium includes a stored program, wherein the above-mentioned program executes any one of the above-mentioned methods when running.

Optionally, in this embodiment, the above-mentioned storage medium may be configured to store program codes for performing the following steps:

S1. When it is determined that a service message that fails to process a business is detected, determine an initial reflow instance corresponding to the service message, where the initial reflow instance is a reflow instance that has not been configured for reflow;

S2. In response to a configuration instruction of the target object, determine configuration information for configuring the reflow instance from a preset configuration library, and use the configuration information to configure the initial reflow instance to generate a target reflow instance, Wherein, the target reflow instance is used to determine a reflow processing result after reflow processing is performed on the service message.

An embodiment of the present application also provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.

Optionally, the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.

Optionally, in this embodiment, the above-mentioned processor may be configured to execute the following steps through a computer program:

S1. When it is determined that a service message that fails to process a business is detected, determine an initial reflow instance corresponding to the service message, where the initial reflow instance is a reflow instance that has not been configured for reflow;

S2. In response to a configuration instruction of the target object, determine configuration information for configuring the reflow instance from a preset configuration library, and use the configuration information to configure the initial reflow instance to generate a target reflow instance, Wherein, the target reflow instance is used to determine a reflow processing result after reflow processing is performed on the service message.

Optionally, in this embodiment, the above-mentioned storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), Various media that can store program codes such as removable hard disks, magnetic disks, or optical disks.

Optionally, for specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and optional implementation manners, and details are not repeated in this embodiment.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned application can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present application is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present application. It should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present application, some improvements and modifications can also be made. These improvements and modifications are also It should be regarded as the protection scope of this application.

Claims (12)

1. The method for generating the target reflux example is characterized by comprising the following steps:

under the condition that the service message of which the service processing is failed is determined to be monitored, determining an initial reflow instance corresponding to the service message, wherein the initial reflow instance is a reflow instance which is not subjected to reflow configuration; and responding to a configuration instruction of a target object, determining configuration information for configuring the reflow example from a preset configuration library, and configuring the initial reflow example by using the configuration information to generate a target reflow example, wherein the target reflow example is used for determining a reflow processing result after the business message is subjected to reflow processing.

2. The method for generating a target reflow instance according to claim 1, wherein after configuring the initial reflow instance using the configuration information to generate a target reflow instance, the method further comprises:

Under the condition that the instance state of the target reflux instance is determined to indicate that the target reflux instance is started, a first client corresponding to the target reflux instance is created;

responding to a query instruction of the first client, and acquiring an instance name contained in the query instruction;

and sending the reflow parameters of the target reflow instance to the first client under the condition that the instance name is consistent with the instance name of the target reflow instance.

3. The method for generating the target reflux instance according to claim 2, wherein after sending the reflux parameters of the target reflux instance to the first client, the method further comprises:

if a first notification message for indicating to continue the reflow by the first client is received, determining that the reflow processing result is incomplete;

and if a second notification message for indicating that the reflow is finished is received by the first client, determining that the reflow processing result is finished.

4. The method for generating the target reflux instance according to claim 2, wherein sending the reflux parameters of the target reflux instance to the first client includes:

Determining a first message middleware interface corresponding to the target reflux instance;

establishing a first message channel for transmitting the reflow parameters based on the first message middleware interface;

sending the reflow parameters to the first client through the first message channel;

wherein the first message middleware interface allows interfacing clients of different middleware types.

5. The method for generating a target reflow instance according to claim 1, wherein after configuring the initial reflow instance using the configuration information to generate a target reflow instance, the method further comprises:

under the condition that the instance state of the target reflux instance is determined to indicate that the target reflux instance is started, a second client corresponding to the target reflux instance is created;

acquiring a query result of the second client on the service message;

and under the condition that the query result indicates that the service message to be reflowed exists in the service messages, if the corresponding relation between the service message to be reflowed and the target reflow example is determined, determining that the reflow result is incomplete.

6. The method for generating the target reflux instance according to claim 5, wherein obtaining the query result of the second client for the service message comprises:

determining a second message middleware interface corresponding to the target reflux instance;

establishing a second message channel for transmitting the query result based on the second message middleware interface;

receiving the query result transmitted through the second message channel;

wherein the second message middleware interface allows interfacing clients of different middleware types.

7. The method for generating a target reflow instance according to claim 1, wherein after configuring the initial reflow instance using the configuration information to generate a target reflow instance, the method further comprises:

destroying a first client corresponding to the target reflux instance under the condition that the instance state of the target reflux instance indicates that the target reflux instance is started;

and if a third notification message for indicating that the first client is destroyed successfully is received, determining that the reflow processing result is finished.

8. The method for generating a target reflow instance according to claim 1, wherein after configuring the initial reflow instance using the configuration information to generate a target reflow instance, the method further comprises:

Destroying a second client corresponding to the target reflux instance under the condition that the instance state of the target reflux instance indicates that the target reflux instance is started;

and if a fourth known message for indicating that the second client is destroyed successfully is received, determining that the reflow processing result is finished.

9. The method for generating the target reflow instance according to claim 1, wherein configuring the initial reflow instance using the configuration information includes:

determining the preset reflow times of the initial reflow examples from the preset configuration library, wherein the initial reflow time interval of the initial reflow examples;

setting increasing time of the reflow interval time based on the difference value of the preset reflow times and the preset threshold value under the condition that the preset reflow times are not larger than the preset threshold value, and determining the reflow time interval of the target reflow example according to the sum value of the initial reflow time interval and the increasing time;

and setting the reflow interval time as a default increment time under the condition that the preset reflow times are larger than a preset threshold value, and determining the reflow time interval of the target reflow example according to the sum value of the initial reflow time interval and the default increment time.

10. A device for generating a target reflux instance, comprising:

the determining module is used for determining an initial reflow instance corresponding to the service message under the condition that the service message with failed service processing is determined, wherein the initial reflow instance is a reflow instance without reflow configuration;

the configuration module is used for responding to a configuration instruction of a target object, determining configuration information for configuring the reflow instance from a preset configuration library, and configuring the initial reflow instance by using the configuration information to generate a target reflow instance, wherein the target reflow instance is used for determining a reflow processing result after the business message is subjected to reflow processing.

11. A computer readable storage medium, characterized in that the computer readable storage medium comprises a stored program, wherein the program when run performs the method of any of the preceding claims 1 to 9.

12. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of the claims 1 to 9 by means of the computer program.