JP5061210B2 - Application server and method for monitoring multiple backend servers - Google Patents

Description

  The present invention relates to an application server that monitors the communication status of a plurality of back-end servers that manage content in an application server that provides content in response to a request from a client terminal, and a method thereof.

  In recent years, one web page in response to a request request includes a plurality of contents (for example, one web page includes news, blogs, stock prices, fortune-telling), and the plurality of contents are managed by individual back-end servers. Has been. Therefore, an application server that has received a request request from a client terminal needs to access a plurality of back-end servers when providing a Web page corresponding to the request request.

  Here, when a communication failure has occurred in the back-end server, the application server cannot access the back-end server. As a means for detecting whether or not a communication failure has occurred, for example, the technique described in Patent Document 1 is used. Are known.

JP 2002-94507 A

  By the way, in patent document 1, although the communication failure of the back end server can be detected, the detected communication failure cannot be dealt with. Here, a problem when the communication failure of the back-end server cannot be dealt with will be described with reference to FIG.

  In FIG. 8, a request request is made from the client terminal 2 to the application server 1. The Web page corresponding to this request request includes news content, blog content, stock price content, and fortune telling content. The news content is managed by the back end server 3A, the blog content is managed by the back end server 3B, the stock price content is managed by the back end server 3C (not shown), and the fortune telling content is managed by the back end server 3D (not shown). . In FIG. 8, the back-end server 3B has a communication failure and is unable to communicate.

  When the application server 1 accesses the back-end servers 3A to 3D in response to the request and acquires the corresponding content, the back-end servers 3A, 3C, and 3D can communicate without causing a communication failure. Corresponding content can be acquired. On the other hand, since the back-end server 3B cannot communicate, the corresponding content cannot be acquired. At this time, if the communication failure of the back-end server 3B cannot be dealt with, the application server 1 repeatedly accesses the back-end server 3B and wastes the resources of the application server 1.

  As a result, the resources of the application server 1 become insufficient, and a failure (delay) occurs not only in the backend server 3B that cannot communicate but also in communication with the backend servers 3A, 3C, and 3D that can communicate. Therefore, on the display unit of the client terminal 2, for example, the stock price content 201C and the fortune telling content 201D that can be displayed immediately are not displayed for a long time, and the user of the client terminal 2 is uncomfortable.

  Therefore, the present invention suppresses user discomfort due to a decrease in resource of an application server, and provides an application server and method capable of suppressing a decrease in resource when a back-end server communication failure occurs. Objective.

( 1 ) An application server including a request processing device that acquires contents of a plurality of back-end servers in response to a request and provides them to a client terminal, and monitors a communication status indicating whether communication with the back-end server is possible And a monitoring DB that stores the communication status for each back-end server, and the back-end server monitoring device responds according to the communication status stored in the monitoring DB. The interruption level update means for updating the degree of restriction of communication with the backend server in a stepwise manner with respect to the backend server, the communication status is periodically acquired from the monitoring DB, and the number of times the communication could not be performed within a predetermined time. A communication status confirmation means for determining whether or not the first threshold value is exceeded, Upon receiving a request request from the client terminal, the request processing device controls whether to limit communication to the back-end server based on the request request based on the degree updated by the cutoff level update unit. A communication control unit that performs content acquisition, a content acquisition unit that acquires content from a back-end server that manages content corresponding to the request request, on the condition that communication is not restricted by the communication control unit, and is acquired by the content acquisition unit Content provision means for providing the content to the client terminal, and the blocking level update means stepwise increases the degree each time the communication status confirmation means determines that the first threshold value is exceeded. Application server to raise.

According to the application server of ( 1 ), communication with the back-end server can be appropriately controlled because communication with the back-end server is restricted step by step without being interrupted immediately. As a result, a reduction in resource of the application server can be suppressed, and communication is restricted in stages, so that the influence on the client terminal can be minimized. Moreover, in order to limit communication to the backend server step by step depending on the number of times the backend server has failed to communicate, if the backend server communication is in a delayed state due to an increase in load or the like, Communication can be appropriately controlled.

( 2 ) The communication status confirmation unit determines whether or not the number of communication failures within a predetermined time does not exceed a second threshold value, and the blocking level update unit performs the second operation by the communication status confirmation unit. The application server according to ( 1 ), wherein each time the degree is determined not to be exceeded, the degree is gradually reduced.

According to the application server of ( 2 ), when the number of times the back-end server cannot communicate decreases, the communication restriction to the back-end server is gradually released, so that the communication status of the back-end server is recovered. The communication with the back-end server can be appropriately controlled.

( 3 ) The application server according to ( 2 ), wherein the first threshold and the second threshold can be changed for each of the plurality of back-end servers.

According to the application server of ( 3 ), since the threshold value can be arbitrarily set, it is possible to more accurately determine whether the back-end server communication is delayed.

( 4 ) The content providing unit provides a substitute content to the client terminal instead of the content provided by the back-end server whose communication is controlled by the communication control unit. ( 1 ) to ( 3 ) Application server.

According to the application server of ( 4 ), it is possible to provide a user-friendly application server as compared with a case where content managed by a back-end server whose communication is restricted is not provided.

( 5 ) The back-end server monitoring device is configured such that communication is restricted 100% to the administrator of the back-end server on the condition that the cutoff level update unit restricts communication to the back-end server by 100%. The application server according to any one of ( 1 ) to ( 4 ), further comprising an alert notification means for notifying that the user is present.

According to the application server of ( 5 ), the administrator of the back-end server that has been disconnected (100% restriction) can cope with it at an early stage, thereby improving operational efficiency.

( 6 ) The contents of a plurality of back-end servers are acquired in response to request requests, and the application server provided to the client terminal monitors the communication status indicating whether communication with the back-end server is possible for each back-end server. In the method, the application server includes a monitoring DB that periodically accesses the back-end server and stores a communication status of the back-end server, and the application server receives a request request from the client terminal. A storage step of acquiring communication statuses of a plurality of back-end servers that manage content corresponding to the request request and storing them in the monitoring DB; acquiring the communication status from the monitoring DB; and communicating within a predetermined time The number of times there was no first threshold A determination step for determining whether or not to update, an update step for stepwise updating a degree of limiting communication with the back-end server for the corresponding back-end server according to the communication status stored in the monitoring DB, Upon receiving a request request from the client terminal, based on the degree updated by the step, a control step for controlling whether to limit communication to the back-end server based on the request request; and the control step An acquisition step of acquiring content from a back-end server that manages the content corresponding to the request request, and a providing step of providing the acquired content to the client terminal, on condition that communication is not controlled by In the update step, A method for gradually increasing the degree each time the communication status confirmation means determines that the first threshold value is exceeded.

According to the method ( 6 ), the same effect as that of the application server ( 1 ) can be expected.

  ADVANTAGE OF THE INVENTION According to this invention, the application server which can suppress the fall of a resource at the time of the communication failure of a back end server, and its method can be provided.

It is a figure which shows the outline of the application server which concerns on 1st Embodiment. It is a block diagram which shows the structure of the application server which concerns on 1st Embodiment. It is a figure which shows an example of monitoring DB of the application server which concerns on 1st Embodiment. It is a flow which shows the flow of the web page data provision process of the application server which concerns on 1st Embodiment. It is a flow which shows the flow of the communication interruption | blocking process of the application server which concerns on 1st Embodiment. It is a flow which shows the flow of the communication return process of the application server which concerns on 1st Embodiment. It is a figure which shows operation | movement of the application server which concerns on 1st Embodiment. It is a figure which shows operation | movement of the conventional application server. It is a figure which shows the outline of the application server which concerns on 2nd Embodiment. It is a block diagram which shows the structure of the application server which concerns on 2nd Embodiment. It is a figure which shows an example of monitoring DB of the application server which concerns on 2nd Embodiment. It is a flow which shows the flow of the web page data provision process of the application server which concerns on 2nd Embodiment. It is a flow which shows the flow of the interruption | blocking level update process of the application server which concerns on 2nd Embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  This embodiment is applied to a computer and its peripheral devices. Each means in the present embodiment is configured by hardware included in a computer and its peripheral devices, and software that controls the hardware.

  The hardware includes a storage device, a communication device, a display device, and an input device in addition to a CPU (Central Processing Unit) as a control unit. Examples of the storage device include a memory (RAM: Random Access Memory, ROM: Read Only Memory, etc.), a hard disk drive (HDD: Hard Disk Drive), and an optical disk (CD: Compact Disk, DVD: Digital Versatile Drive, etc.). It is done. Examples of the communication device include various wired and wireless interface devices. Examples of the display device include various displays such as a liquid crystal display and a plasma display. Examples of the input device include a keyboard and a pointing device (such as a mouse and a tracking ball).

  The software includes a computer program and data for controlling the hardware. The computer program and data are stored in a storage device and are appropriately executed and referenced by a control unit. The computer program and data can be distributed via a communication line, or can be recorded on a computer-readable medium such as a CD-ROM and distributed.

[First Embodiment]
With reference to FIGS. 1-7, the application server 1 which concerns on 1st Embodiment is demonstrated.

[Outline of Application Server]
FIG. 1 is a diagram showing an outline of an application server 1 according to the first embodiment. The application server 1 is provided for each request request, and receives a request request from client terminals 2A, 2B, 2C (hereinafter referred to as “client terminal 2” if not distinguished), and a plurality of requests according to the request request. The data (Web page data) that constitutes the Web page including the content is sent back to the client terminal 2.

  The “request request” is information for designating content desired by the client terminal 2 (user), and corresponds to, for example, a URL (Uniform Resource Locator).

  When the application server 1 receives the request, the application server 1 sends a plurality of back-end servers 3A, 3B,... (Hereinafter referred to as “back-end server 3” if they are not distinguished) to manage the contents constituting the corresponding Web page. Access and get content from each.

  Here, in FIG. 1, the Web page corresponding to the request request from the client terminal 2 includes content managed by the back-end server 3A and content managed by the back-end server 3B. Further, the back-end server 3A is in a communicable state, and the back-end server 3B is in a state in which communication failure occurs and communication is impossible. At this time, the application server 1 according to the first embodiment accesses the back-end server 3A but does not access the back-end server 3B. As a result, the back-end server 3B that cannot communicate is not repeatedly accessed, and a reduction in resource of the application server 1 can be suppressed.

  Hereinafter, a specific configuration of the application server 1 according to the first embodiment will be described.

[Configuration of Application Server 1]
FIG. 2 is a block diagram showing the configuration of the application server 1. The application server 1 communicates between a request processing device 11 that provides Web page data in response to a request from the client terminal 2 and a back-end server 3 that manages content included in the Web page configured by the Web page data. The back-end server monitoring device 12 that monitors the status and the monitoring DB 13 that stores the communication status of the back-end server 3 are configured.

  The request processing device 11 includes a request receiving unit 111, a blocking information confirmation unit 112, a communication status acquisition unit 113, a content acquisition unit 114, and a content provision unit 115.

  The request receiving unit 111 receives a request request from the client terminal 2.

  The blocking information confirmation unit 112 refers to the monitoring DB 13 and confirms whether or not the back-end server 3 that manages the content constituting the Web page corresponding to the request request is in a communication blocking state. Specifically, by referring to a monitoring table of the monitoring DB 13 to be described later in FIG. 3 (2) and confirming a blocking flag of the back-end server 3 to be accessed in response to a request request, the corresponding back-end server 3 Check if the communication is cut off. The cutoff flag is updated to “1 (communication cutoff)” by the communication cutoff unit 122 described later, and is updated to “0 (communication possible)” by the communication return unit 124 described later. Accordingly, the blocking information confirmation unit 112 determines that the communication is blocked when the blocking flag of the corresponding back-end server 3 is “1”, and determines that the communication is possible when it is “0”. to decide.

  The communication status acquisition unit 113 acquires the communication status (communication status) of the back-end server 3 that is confirmed as being communicable by the blocking information confirmation unit 112 among the back-end servers 3 that manage the content according to the request. . For example, the communication status is acquired by throwing “echo request” of ICMP (Internet Control Message Protocol) to the back-end server 3 and executing “ping” to receive “echo reply” from the back-end server 3. Here, the communication status acquisition unit 113 acquires the communication status a plurality of times at a predetermined interval (for example, 1 second). At this time, if “echo reply” is not received from the back-end server 3, the status table of the monitoring DB 13 stores that the communication status of the corresponding back-end server 3 is an error (see FIG. )reference).

  The content acquisition unit 114 accesses the back-end server 3 that is confirmed not to be in the communication cutoff state by the cutoff information confirmation unit 112 among the back-end servers 3 that manage the content according to the request request, and acquires the content.

  The content providing unit 115 generates Web page data from the acquired plurality of contents and provides it to the client terminal 2. If there is a back-end server 3 in a communication cut-off state, Web page data including substitute content (for example, guidance content such as “currently unavailable”) is generated instead of the content managed by the back-end server 3 And may be provided.

  Subsequently, the back-end server monitoring device 12 includes a communication status confirmation unit 121, a communication cutoff unit 122, an alert notification unit 123, and a communication return unit 124.

  The communication status confirmation unit 121 refers to the status table of the monitoring DB 13 which will be described later with reference to FIG. 3A, and confirms for each back-end server 3 whether the number of errors within a predetermined time exceeds a predetermined threshold. . This threshold value may be different for each back-end server 3. The threshold value may be arbitrarily changed by the administrator of the application server 1 or the back-end server 3.

  The communication blocking unit 122 sets the back-end server 3 in a communication blocking state when the number of errors within a predetermined time exceeds a threshold value. Specifically, the blocking flag of the corresponding back-end server 3 is updated to “1” in the monitoring table of the monitoring DB 13 described later in FIG.

  The alert notification unit 123 notifies the administrator terminal 4 of the back-end server 3 that the back-end server 3 to be managed is in a communication cut-off state. Thereby, the administrator can recognize early that there is a communication failure in the back-end server 3, and can solve this communication failure early.

  The communication return means 124 accesses the back-end server 3 in the communication cut-off state (the cut-off flag is “1”) periodically (at a longer interval (for example, 1 minute) than the communication status acquisition means 113). The communication status is acquired and it is determined whether or not communication is possible. If communication is possible, the communication cutoff state is canceled by updating the cutoff flag of the monitoring table (FIG. 3B) of the monitoring DB 13 to “0”.

  Here, in the first embodiment, not when the communication status acquisition unit 113 receives “echo reply” (when the communication status of the corresponding back-end server 3 becomes an error in the status table of the monitoring DB 13). If the number of errors “within a predetermined time” exceeds the threshold, the communication status of the back-end server 3 is set to the communication cut-off state. This is to prevent the communication from being interrupted until the communication with the back-end server 3 is temporarily impossible due to an increase in traffic.

  Subsequently, the monitoring DB 13 includes a status table and a monitoring table, and stores the communication status of the back-end server 3. As shown in FIG. 3A, the status table stores the communication status of the back-end server 3 acquired by the communication status acquisition unit 113. For example, referring to FIG. 3 (1), it is stored that communication with the backend server 3A was possible at 18:20:01 on June 21, and the backend was recorded at 18:20:11 on June 21. It is stored that communication with the server 3B could not be established.

  In addition, the monitoring table stores information on the blocking flag for each type of the back-end server 3 as shown in FIG. When the blocking flag is “0”, it means that communication is possible, and when the blocking flag is “1”, communication is blocked (the back-end server 3 is not accessed even if a request is made). It means that. The blocking flag is updated from “0” to “1” by the communication blocking unit 122 when the number of errors in the status table within a predetermined time for the corresponding back-end server 3 exceeds a threshold value. Further, when the communication return means 124 determines that communication is possible, the cutoff flag is updated from “1” to “0”.

[Processing of application server 1]
Next, an operation flow of the application server 1 will be described with reference to FIGS.

[Web page data provision processing]
FIG. 4 is a flowchart showing the flow of Web page data provision processing when providing Web page data in response to a request request received from the client terminal 2.

  S1: The request reception unit 111 receives a request request for specifying a Web page desired by the user from the client terminal 2.

  S2: Subsequently, the blocking information confirmation unit 112 identifies the back-end server 3 that manages the content included in the Web page corresponding to the request request, and confirms the communication information of the corresponding back-end server 3. That is, the blocking information confirmation unit 112 refers to the monitoring table of the monitoring DB 13 and confirms the blocking flag of the backend server 3.

  S3: For the back-end server 3 that is not in the communication cut-off state at this time, the communication status acquisition unit 113 accesses the communication status multiple times at a predetermined interval (for example, 1 second) to acquire the communication status.

  S4: Subsequently, the content acquisition unit 114 acquires the content from the back-end server 3 with which the communication status is confirmed and can be communicated.

S5: On the other hand, the communication status acquisition unit 113 and the content acquisition unit 114 do not access the back-end server 3 that is confirmed to be in the communication cutoff state by the cutoff information confirmation unit 112, and the content acquisition unit 114 The substitute content stored in the storage device of the application server 1 (which may be a storage device of another server) is acquired.
It should be noted that not only the back-end server 3 that is in the communication cut-off state but also the back-end server 3 that is not in the communication cut-off state (the communication flag is “0”) but cannot be confirmed by the communication status acquisition unit 113 The content may be acquired.

  S6: Subsequently, the content providing unit 115 generates Web page data corresponding to the request request from the acquired content and substitute content, and provides it to the client terminal 2.

[Communication blocking process]
Next, with reference to FIG. 5, a communication blocking process for blocking communication with the backend server 3 will be described.

  S11: The communication status confirmation unit 121 refers to the status table of the monitoring DB 13 and confirms the communication status of the back-end server 3. For example, the communication status confirmation unit 121 confirms whether or not the number of errors within a predetermined time exceeds a predetermined threshold value for each corresponding back-end server 3.

  S12: Subsequently, the communication cutoff unit 122 sets the back-end server 3 in which the number of errors within a predetermined time exceeds a predetermined threshold to a communication cutoff state. That is, the blocking flag of the backend server 3 is updated to “1” in the monitoring table of the monitoring DB 13. As a result, in S2 of FIG. 4, it is confirmed that the communication is cut off by the cut-off information confirmation unit 112, and even if a request is made from the client terminal 2, the back-end server 3 is not accessed.

  S13: Next, the alert notification means 123 sends the mail to the administrator terminal 4 of the administrator who manages the back-end server 3 that is in the communication cut-off state, so that the back-end server 3 to be managed is in the communication cut-off state. Notify that. By this notification, the administrator of the back-end server 3 can recognize early that a communication failure has occurred in the back-end server 3, and can expect that the communication failure will be resolved early.

[Communication recovery processing]
Next, with reference to FIG. 6, communication return processing for releasing the communication cutoff state of the back-end server 3 will be described.

  S21: The communication return means 124 acquires a blocking flag from the monitoring table of the monitoring DB 13, and identifies the back-end server 3 whose blocking flag is “1”. That is, the communication return unit 124 identifies the back-end server 3 that is in a communication cut-off state.

  S22: Subsequently, the communication return means 124 periodically accesses the back-end server 3 that is in the communication cut-off state, and acquires the communication status.

  S23: At this time, when the connection with the back-end server 3 in the communication cut-off state can be confirmed, the communication return means 124 sets the cut-off flag of the back-end server 3 to “1” in the monitoring table of the monitoring DB 13. To "0". On the other hand, when the connection cannot be confirmed, the communication return means 124 maintains the cutoff flag of the backend server 3 as “1”. As a result, when the connection with the back-end server 3 that is in the communication cut-off state can be confirmed, the communication cut-off state is released, and then the back-end server 3 is accessed in response to a request from the client terminal 2 Will be.

  As described above, according to the application server 1 according to the first embodiment, the backend server 3 that is confirmed to be in the communication cut-off state is not repeatedly accessed at the time of content acquisition. A decrease in the resources of the application server 1 due to repeated access to the server 3 can be suppressed.

  Further, in this case, according to the application server 1 according to the first embodiment, the back-end server 3 in which a communication failure has occurred can be automatically set in a communication cut-off state, and the administrator of the back-end server 3 Then, when the communication failure is resolved, the communication disconnection state can be automatically canceled by the communication return means 124. Therefore, the control of the communication cutoff state of the back-end server 3 can be automatically performed, and the operation cost can be reduced.

  Further, since an alert is notified to the administrator of the back-end server 3 that is in the communication cut-off state, the administrator can respond to the communication failure at an early stage and can improve the operation efficiency.

[Operation example of application server 1]
Next, an operation example of the application server 1 according to the first embodiment will be described with reference to FIG.

  When a request request is made from the client terminal 2 to the application server 1, the application server 1 acquires content from a plurality of back-end servers 3 that manage the content that constitutes the Web page corresponding to the request request. Here, in FIG. 7, the Web page corresponding to the request request includes news content, blog content, stock price content, and fortune-telling content. News content is managed by the back-end server 3A, blog content is managed by the back-end server 3B, stock price content is managed by the back-end server 3C (not shown), and fortune-telling content is managed by the back-end server 3D (not shown). . Further, in FIG. 7, the back-end server 3B is in a state where communication failure occurs and communication is impossible, so the blocking flag is updated to “1”.

  In response to the request, the application server 1 accesses the back-end servers 3A to 3D and acquires the corresponding content. Since the back-end servers 3A, 3C, and 3D are communicable, the corresponding content is acquired. Can do. On the other hand, since the back-end server 3B is in a communication cut-off state, it is not accessed even if a request is made.

  As a result, the back-end server 3 in which a communication failure has occurred is not repeatedly accessed, so that the resource of the application server 1 can be prevented from being reduced, and communication with back-end servers 3A, 3C, 3D that can communicate No need to affect Thereby, the Web page including the news content 201A, the stock price content 201C, and the fortune telling content 201D managed by the communicable back-end servers 3A, 3C, and 3D is appropriately displayed on the display unit of the client terminal 2. At this time, if the substitute content 201B is displayed instead of the blog content managed by the back-end server 3B in the communication cut-off state, the user of the client terminal 2 can understand the situation of the back-end server 3B. It is possible to prevent the user of the client terminal 2 from feeling uncomfortable.

[Second Embodiment]
Next, an application server 1A according to the second embodiment will be described with reference to FIGS. Note that in the second embodiment, identical symbols are assigned to configurations identical to those in the first embodiment and detailed description thereof is omitted.

  The application server 1 according to the first embodiment immediately disconnects communication according to the communication status of the back-end server 3 stored in the status table of the monitoring DB 13 (when the number of errors in a predetermined time exceeds a predetermined threshold). State. On the other hand, in the application server 1A of the second embodiment, communication is limited step by step according to the communication status of the back-end server 3. For example, it is suitable when the communication status of the back-end server 3 is in a delayed state due to an increase in load or the like.

  Referring to FIG. 9, back end server 3A is a back end server 3 capable of communication, and back end server 3B is a back end server 3 that restricts communication by one third. When a request request is made from the client terminals 2A, 2B, and 2C, the application server 1A acquires the content from the communicable back-end server 3A and provides the acquired content to the client terminals 2A, 2B, and 2C. On the other hand, since the back-end server 3B restricts communication by one third, the application server 1A makes a content request based on a request request from the client terminals 2B and 2C, but based on a request request from the client terminal 2A. Limit content requests. As a result, the content managed by the back-end server 3B is provided to the client terminals 2B and 2C, and the content managed by the back-end server 3B is not provided to the client terminal 2A. Note that the application server 1A may provide a substitute content instead of the content managed by the back-end server 3B, as with the application server 1, for the client terminal 2A whose communication is restricted.

  In this way, in the application server 1A, communication with the back-end server 3B whose communication status is in a delayed state is limited in stages, so that a reduction in resources of the application server 1A can be suppressed and communication is possible. No need to affect the communication with 3. Further, since the application server 1A does not immediately cut off the communication but restricts the communication step by step, the influence on the client terminal 2 can be minimized.

  Hereinafter, a specific configuration of the application server 1A according to the second embodiment will be described.

[Configuration of Application Server 1A]
FIG. 10 is a block diagram showing the configuration of the application server 1A.
The application server 1A communicates between a request processing device 11A that provides Web page data in response to a request from the client terminal 2 and a back-end server 3 that manages content included in the Web page configured by the Web page data. The back-end server monitoring device 12A that monitors the situation and the monitoring DB 13A that stores the communication status of the back-end server 3 are configured.

  The request processing apparatus 11A includes a request reception unit 111, a communication control unit 112A, a communication status acquisition unit 113, a content acquisition unit 114, and a content provision unit 115.

The communication control unit 112A refers to the monitoring DB 13A, and confirms the communication restriction state of the back-end server 3 that manages the contents constituting the Web page according to the request request received by the request reception unit 111. Specifically, the communication control unit 112A refers to a monitoring table of the monitoring DB 13A, which will be described later with reference to FIG. 11, and confirms the blocking level of the back-end server 3 to be accessed according to the request request. The communication restriction state of the server 3 is confirmed. The blocking level is “0”, for example, where there is no communication restriction, “1”, for example, which restricts 10% communication, “2”, for example, which restricts 20% communication, and similarly “3”. “9” refers to a state in which, for example, 30% to 90% of communication is restricted, and “10” refers to a state in which, for example, 100% of communication is restricted (ie, a communication cutoff state). Of course, the communication restriction state is not limited to this, and can be arbitrarily set. Such interruption level update is performed by the interruption level updating means 122A.
The communication control unit 112A limits communication to the back-end server 3 (communication by the communication status acquisition unit 113 and the content acquisition unit 114) based on the confirmed blocking level. For example, the communication control unit 112A limits the communication of 10% when the cutoff level is “1”. As an example of a method of restricting 10% communication, a random number is generated, and communication based on a request request whose remainder is “1” among the request requests from the client terminal 2 divided by 10 is restricted, It is conceivable that communication based on a request request whose remainder is other than “1” is not limited (of course, it can be realized by other methods).

The communication status acquisition unit 113 and the content acquisition unit 114 perform predetermined communication with the back-end server 3 based on a request request that communication is not limited. The content providing unit 115 provides the content acquired by the content acquisition unit 114 to the client terminal 2.
Note that the content acquisition unit 114, in response to a request request with restricted communication, substitutes for the content managed by the back-end server 3 with restricted communication (for example, guidance content such as “currently unavailable”). And the content providing means may provide the substitute content to the client terminal 2.

  Subsequently, the back-end server monitoring device 12A includes a communication status confirmation unit 121A, a cutoff level update unit 122A, and an alert notification unit 123.

The communication status confirmation unit 121A periodically (for example, 1 minute) confirms the status table of the monitoring DB 13A (same as the status table of the first embodiment shown in FIG. 3 (1)), and the number of errors within a predetermined time is determined in advance. It is confirmed for each back-end server 3 whether or not a predetermined first threshold value is exceeded.
Further, the communication status confirmation unit 121A periodically checks the status table of the monitoring DB 13A, and determines whether the number of errors within a predetermined time does not exceed a predetermined second threshold, and the blocking level is “1” to “1”. 9 ”for each back-end server 3.
In addition, the communication status confirmation unit 121A accesses the back-end server 3 with the cutoff level “10” periodically (for example, for 1 minute), acquires the communication status, and determines whether communication is possible. That is, it is directly confirmed whether or not communication is possible with respect to the back-end server 3 whose communication is cut off.

The first threshold value and the second threshold value may be the number of errors within a predetermined time, or may be a ratio of the number of errors with respect to all communications within a predetermined time. Further, the first threshold value and the second threshold value may be different for each back-end server 3. The first threshold value and the second threshold value may be arbitrarily changed by the administrator of the application server 1A or the back-end server 3. The second threshold value is preferably the same value as the first threshold value or smaller than the first threshold value.
Further, “more than or less than” may be “more than or less than”, “greater than or less than”, “more than or less than”, or “greater than or less than”. However, when the first threshold value and the second threshold value are set to the same value, it is preferably “more than or less than” or “greater than or less than”.

The blocking level update unit 122A updates the blocking level of the monitoring table of the monitoring DB 13A. Specifically, when the communication status confirmation unit 121A determines that the number of errors within a predetermined time exceeds the first threshold, the blocking level update unit 122A sets the blocking level of the corresponding back-end server 3. Increase "1". On the other hand, when the communication status confirmation unit 121A determines that the number of errors within the predetermined time does not exceed the second threshold, the blocking level update unit 122A sets the blocking level of the corresponding back-end server 3 to “1”. ”Lower. As described above, the cutoff level update unit 122A updates the cutoff level in stages based on the number of errors, thereby limiting communication to the back-end server 3 in stages.
Further, when the communication status confirmation unit 121A determines that communication is possible for the back-end server 3 whose block level is “10”, the block level update unit 122A displays the block level of the corresponding back-end server 3. Is updated from “10” to “9”.

  The alert notification unit 123 manages the administrator terminal 4 of the backend server 3 when the blocking level update unit 122A updates the blocking level from “9” to “10” (that is, updates the communication blocking state). The back-end server 3 to be notified is in a communication cut-off state.

Subsequently, the monitoring DB 13A is composed of a status table and a monitoring table, and stores the communication status of the back-end server 3. The status table is the same as that in the first embodiment, and stores the communication status of the back-end server 3 acquired by the communication status acquisition means 113 as shown in FIG.
Further, the monitoring table stores information on the cutoff level for each type of the back-end server 3, as shown in FIG.

[Processing of application server 1]
Next, an operation flow of the application server 1A will be described with reference to FIGS.

[Web page data provision processing]
FIG. 12 is a flowchart showing a flow of Web page data provision processing when providing Web page data in response to a request request received from the client terminal 2. The web page data providing process of the second embodiment is basically the same as the web page data providing process of the first embodiment, but the process of step S102 is different.

  S101: The request receiving unit 111 receives a request request for specifying a Web page desired by the user from the client terminal 2.

  S102: Subsequently, the communication control unit 112A specifies the back-end server 3 that manages the content included in the Web page according to the request request, and restricts communication based on the blocking level of the corresponding back-end server 3. . Specifically, the communication control unit 112A limits the communication of 10% when the cutoff level is “1”.

  S103: If there is no communication restriction, the communication status acquisition unit 113 accesses the back-end server 3 a plurality of times at a predetermined interval (for example, 1 second), and acquires the communication status.

  S104: Subsequently, the content acquisition unit 114 acquires the content from the back-end server 3 with which the communication status is confirmed and can be communicated.

S105: On the other hand, when communication is restricted by the communication control unit 112A, the communication status acquisition unit 113 and the content acquisition unit 114 do not access the back-end server 3, and the content acquisition unit 114 is a storage device of the application server 1A. The substitute content stored in (may be a storage device of another server) is acquired.
Note that the content acquisition unit 114 may acquire the substitute content not only when communication is restricted but also when the communication status acquisition unit 113 cannot confirm that communication is possible.

  S106: Subsequently, the content providing unit 115 generates Web page data corresponding to the request request from the acquired content and substitute content, and provides it to the client terminal 2.

[Blocking level update processing]
Next, a block level update process for updating the block level of the back-end server 3 will be described with reference to FIG. In FIG. 13, S111 to S115 indicate the flow of processing when updating the blocking level from “10” to “9”, and S116 to S120 indicate the flow of processing when increasing the blocking level in stages. , S116 to S123 show the flow of processing when the blocking level is lowered stepwise.

  S111: The communication status confirmation unit 121A acquires the blocking level of the target back-end server 3 from the monitoring table of the monitoring DB 13A.

  S112: The communication status confirmation unit 121A determines whether or not the acquired blocking level is “10”, that is, whether or not the back-end server 3 is in a communication blocking state.

  S113, S114: At this time, if the communication is cut off, the communication status confirmation unit 121A accesses the back-end server 3 periodically (for example, 1 minute), acquires the communication status, and is communication possible? Judge whether or not.

  S115: At this time, if communication is possible, the cutoff level updater 122A lowers the cutoff level from “10” to “9” and ends the process. On the other hand, if communication is impossible, the cutoff level updater 122A ends the process.

  S116: If the blocking level is not “10”, the communication status confirmation unit 121A refers to the status table of the monitoring DB 13A and acquires the communication status of the back-end server 3.

S117: Subsequently, the communication status confirmation unit 121A determines whether or not the number of errors within a predetermined time exceeds the first threshold value.
S118: At this time, if the first threshold value is exceeded, the cutoff level updater 122A increases the cutoff level of the target back-end server 3 by “1”.

S119: Subsequently, the cutoff level updater 122A determines whether or not the cutoff level has been updated to “10”.
S120: At this time, when the interruption level is updated to “10”, the alert notification unit 123 transmits an email to the administrator terminal 4 of the administrator who manages the back-end server 3 in the communication interruption state. Thus, the back-end server 3 to be managed is notified that the communication is cut off, and the process is terminated. On the other hand, if the cutoff level is not “10”, the alert notification means 123 ends the process.

S121: When the number of errors within a predetermined time does not exceed the first threshold, the communication status confirmation unit 121A determines whether or not the number of errors does not exceed the second threshold.
S122: At this time, if the second threshold value is not exceeded, the cutoff level update unit 122A determines whether or not the cutoff level of the target back-end server 3 is “0”. On the other hand, when the second threshold value is exceeded, the cutoff level updater 122A ends the process.
S123: Subsequently, when the blocking level is not “0” (that is, when communication restriction is imposed), the blocking level update unit 122A lowers the blocking level of the target back-end server 3 by “1”, The process ends. On the other hand, when the cutoff level is “0”, the cutoff level updater 122A ends the process.

The application server 1A according to the second embodiment has been described above.
According to the application server 1A, when communication to the back-end server 3 is in a delayed state due to an increase in load or the like, it is possible to limit communication to the back-end server 3 in stages according to the delay state. As a result, the application server 1 </ b> A can suppress a reduction in its own resources, and does not affect communication with the back-end server 3 that can communicate. Further, since the application server 1A does not immediately cut off the communication but restricts the communication step by step, the influence on the client terminal 2 can be minimized.

  As mentioned above, although embodiment of this invention was described, this invention is not restricted to embodiment mentioned above. The effects described in the embodiments of the present invention are only the most preferable effects resulting from the present invention, and the effects of the present invention are limited to those described in the embodiments of the present invention. is not.

  In the application server 1A according to the second embodiment, the alert notification unit 123 notifies the administrator terminal 4 when the blocking level is updated from “9” to “10” (that is, when communication is blocked). Although the predetermined notification is to be performed, the present invention is not limited to this. For example, a predetermined notification may be sent to the administrator terminal 4 every time the blocking level is updated. In particular, when the blocking level increases by “1” (that is, when communication restriction is applied), A predetermined notification may be sent to the administrator terminal 4.

DESCRIPTION OF SYMBOLS 1 Application server 11 Request processing apparatus 12 Back-end server monitoring apparatus 13 Monitoring DB
111 Request Accepting Unit 112 Blocking Information Confirming Unit 113 Communication Status Obtaining Unit 114 Content Obtaining Unit 115 Content Providing Unit 121 Communication Status Confirming Unit 122 Communication Blocking Unit 123 Alert Notification Unit 124 Communication Returning Unit

Claims (6)

An application server including a request processing device that acquires content of a plurality of back-end servers in response to a request and provides the content to a client terminal,
A back-end server monitoring device that monitors a communication status indicating whether communication to the back-end server is possible, and a monitoring DB that stores the communication status for each back-end server,
The back-end server monitoring device, according to the communication status stored in the monitoring DB, for the corresponding back-end server, a blocking level update unit that updates the degree of limiting communication with the back-end server step by step;
Communication status confirmation means for periodically acquiring the communication status from the monitoring DB and determining whether or not the number of times communication could not be performed within a predetermined time exceeds a first threshold;
The request processing device includes:
A communication control unit that controls whether to limit communication to the back-end server based on the request request based on the degree updated by the blocking level update unit upon receiving a request request from the client terminal; ,
Content acquisition means for acquiring content from a back-end server that manages content corresponding to the request request on the condition that communication is not restricted by the communication control means;
Content providing means for providing the client terminal with the content acquired by the content acquisition means;
With
The block level update means is an application server that increases the degree in steps each time the communication status confirmation means determines that the first threshold value is exceeded. The communication status confirmation means determines whether or not the number of times of communication within a predetermined time does not exceed the second threshold,
2. The application server according to claim 1 , wherein the blocking level update unit gradually decreases the degree each time the communication status confirmation unit determines that the second threshold value is not exceeded. The application server according to claim 2 , wherein the first threshold and the second threshold can be changed for each of the plurality of back-end servers. The application server according to any one of claims 1 to 3 , wherein the content providing unit provides a substitute content to the client terminal in place of the content provided by the back-end server whose communication is controlled by the communication control unit. The back-end server monitoring device
Alert notification means for notifying the administrator of the back-end server that communication is 100% restricted, provided that the blocking level update means restricts communication to the back-end server by 100%; the application server according to any one of claims 1 to 4 comprising. In this method, the content of a plurality of back-end servers is acquired in response to a request request, and the application server provided to the client terminal monitors the communication status indicating whether communication with the back-end server is possible for each back-end server. And
The application server includes a monitoring DB that periodically accesses the back-end server and stores the communication status of the back-end server,
The application server is
A storage step of receiving a request request from the client terminal and acquiring communication statuses of a plurality of back-end servers that manage content corresponding to the request request and storing the communication status in the monitoring DB;
A determination step of acquiring the communication status from the monitoring DB and determining whether or not the number of times of communication within a predetermined time exceeds a first threshold;
An update step for gradually updating the degree of limiting communication with the back-end server for the corresponding back-end server according to the communication status stored in the monitoring DB;
Upon receiving a request request from the client terminal, based on the degree updated by the step, a control step for controlling whether to limit communication to the backend server based on the request request;
An acquisition step of acquiring content from a back-end server that manages content corresponding to the request request, on the condition that communication is not controlled by the control step;
A providing step of providing the acquired content to the client terminal;
Including
In the updating step, the degree is gradually increased each time the communication status confirmation unit determines that the first threshold value is exceeded.

Images