JPH10232848A - Client / server system - Google Patents

Abstract

(57) [Problem] To suppress consumption of physical resources of a server in a client / server system in which a client making a processing request and a server receiving the processing request are connected via a communication path. An object is to provide a mechanism that can recover even when a failure occurs. SOLUTION: When receiving a request from a client 12, a remote procedure control unit 1112 of a management server 111 executes a start procedure 1111 using a parameter of a request application server name. The start procedure 1111 refers to the start application server name corresponding to the requested application server name requested to be started by the application server start information management unit 113, reads the start parameters of the corresponding application server 112, and reads the application server 11
Start 2

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client / server system in which a client making a processing request and a server receiving the processing request are connected via a communication path.

[0002]

2. Description of the Related Art Conventionally, a client / server system has a configuration as shown in FIG. In FIG. 6, 6
Reference numeral 1 denotes a server. In the server 61, reference numerals 611 and 612 denote application servers for receiving remote procedure calls from clients. An application server provided with various types of remote procedures has a plurality of application servers running on the server. 61
Reference numerals 11 and 6121 denote remote procedures, which register procedures that can be executed by the client. 61
Reference numerals 12 and 6122 denote remote procedure control units, which receive a request to execute the remote procedure 6111 or the remote procedure 6121 from the remote procedure control unit 622 of the client and execute the contents of the request.
The execution result is returned to the remote procedure control unit 622 of the client.

Reference numeral 62 denotes a client.
, An application 621 is a start procedure registered in the application server 612;
Request execution of a remote procedure. 622, a remote procedure control unit that accesses the application server using the binding information passed from the application 621;
The remote procedure control unit 6112 transmits an execution request for the remote procedure 6111 to the remote procedure control unit 6112, and receives an execution result of the remote procedure 6111 from the remote procedure control unit 6111. 63 is a communication path.

The operation of the client / server system configured as described above will be described below. It is assumed that the client 62 knows in advance binding information for accessing a plurality of application servers on the server.

First, when it is desired to use the remote procedure 6111 on the client 62 application server 611, the application 621 executes the remote procedure 6111 using the binding information of the application server 611 as a parameter. The remote procedure control unit 622 accesses the application server 611 using the binding information passed from the application 621, and the remote procedure control unit 611 of the application server 611.
2 transmits a request to execute the remote procedure 6112. The remote procedure control unit 6112 receives an execution request from the remote procedure control unit 622 of the client and receives the requested remote procedure 611.
1 is executed, and the execution result is returned to the remote procedure control unit 622 of the client. The remote procedure control unit 622 receives the execution result of the remote procedure 6111, and stores the content thereof in the application 621.
Return to When the remote procedure of another application server 612 is to be used, the remote procedure 612 is executed from the application 621 using the binding information of the application server 612.

[0006]

In the method described in the above-mentioned prior art, a plurality of application servers are started regardless of whether or not the application server is used, so that the physical resources of the server are wasted. Was doing. In addition, a request for a remote procedure was accepted regardless of the load status of the server. Also, there is no mechanism to restart when a failure occurs in the application server. In addition, if the result of the remote procedure call cannot be obtained as a result of normal termination of the executed remote procedure call due to a client failure, it is not known whether or not it is necessary to re-execute the remote procedure.

[0007] Therefore, the first object of the present invention is to suppress the consumption of physical resources of a server. Second,
The purpose is to accept or reject a request from a client depending on the load status of a server. Thirdly, an object of the present invention is to provide a mechanism capable of recovering from a failure of the management server or the application server, and to enable the client to execute the remote procedure as before. Fourth, it is an object of the present invention to determine whether it is necessary to re-execute a remote procedure when a failure occurs in a client.

[0008]

In order to solve the above-mentioned problems, the present invention firstly provides a management server for managing the activation status of an application server, wherein the management server uses information of the application server to manage a plurality of application servers. By associating the client with one application server, consumption of physical resources of the server can be suppressed.

Second, by providing the management server with a CPU monitoring unit for monitoring the load of the CPU, the CPU is provided when the application server is started and when the application server is started.
By providing the CPU monitoring unit that monitors the load on the PU, it is possible to control the acceptance / rejection of requests from the clients and to stabilize the load on the server when executing the remote procedure.

Third, by further providing a remote procedure for starting another application server in the event of an application server failure in the management server, the management server starts the alternative application server even if a failure occurs in the application server, Can execute remote procedures on alternative application servers.

Fourth, a storage device for storing information executed by a remote procedure of an application server in a server and a remote procedure capable of acquiring information executed by the remote procedure stored in the storage device are stored in a management server. By registering, it is possible to obtain the result of the remote procedure that was not obtained as a normal end due to the failure of the client.

[0012]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below with reference to FIGS.

(Embodiment 1) FIG. 1 shows an example of a client / server system according to the present invention. In FIG. 1, reference numeral 11 denotes a server, 111 denotes a management server for managing the activation status of an application server, and 1111. Is a start procedure. When the client 12 requests execution of the start procedure 1111, a start application name corresponding to the specified requested application server name is entered into the application server start information management unit 11.
3 starts the application server having the obtained start application server name, receives the binding information of the started application server from the binding information receiving unit 11111, and registers the information of the started application server in the application server information unit 114. .

Reference numeral 11111 denotes a binding information receiving unit. The binding information transmitting unit of the application server activated from the activation procedure 1111 communicates the binding information of the application server, that is, communication between the client (local machine) and the server (remote machine). To receive the protocol sequence and network information for enabling.

Reference numeral 1112 denotes a remote procedure control unit which receives a request to execute the start procedure 1111 from the client remote procedure control unit, executes the request, and returns the execution result to the client remote procedure control unit.

An application server 112 receives a remote procedure call from a client.
Reference numeral 1121 denotes a binding information transmitting unit that transmits the binding information of the application server 112 to the binding information receiving unit 11111 of the management server 111.

Reference numeral 1122 denotes a remote procedure, which registers a procedure executable by the client.
A remote procedure control unit 1123 receives an execution request of the remote procedure 1122 from the remote procedure control unit of the client, executes the content of the request, and returns an execution result to the remote procedure control unit of the client.

Reference numeral 113 denotes an application server start information management unit which manages a start application server name corresponding to an application server name requested to be started by a client. The start application server name corresponding to the application server name, the number of threads when starting the application server, and the maximum access number.

Reference numeral 114 denotes an application server information section which stores information on the application server and information on the client being accessed when the application server is activated by the activation procedure 1111. The application server name, binding information, and accessing client information are stored. , The maximum number of accesses is written.

Reference numeral 12 denotes a client, and 121 denotes an application, which requests execution of a start procedure and a remote procedure registered in the management server 111 and the application server 112.

Reference numeral 122 denotes a remote procedure control unit.
The management server 111 or the application server 112 is accessed using the binding information passed from the application 121, and the start procedure 1 is sent to the remote procedure control unit 1112 of the management server 111.
The execution request of the remote procedure 1122 is transmitted to the remote procedure control unit 1123 of the application server 112, and the execution results of the activation procedure 1111 and the remote procedure 1122 are transmitted from the remote procedure control unit 1112 and the remote procedure control unit 1123, respectively. Receive. 13 is a communication path.

The operation of the client / server system configured as described above will be described with reference to FIG.

On the server 11, only the management server 111 has been activated, and is in a state of waiting for an execution request of the activation procedure 1111 from the client 12. The client 12 is a management server 111 of the server 11.
Knows the binding information of the management server 111
Can be executed.

Process 1-1: First, the client 12
The application 121 executes a start procedure 1111 for starting the application server 112 using the binding information of the management server 111 and the name of the requesting application server to be requested to start as parameters.

Process 1-2: The remote procedure control unit 122 accesses the request to the management server 111 using the binding information of the management server 111, and executes the start procedure 1111 together with the parameters to the remote procedure control unit 1112 of the management server 111. Request.

Process 1-3: Upon receiving a request from the client 12, the remote procedure control section 1112 of the management server 111 executes the start procedure 1111 with the request application server name as a parameter.

Process 1-4: Start-up procedure 1111
Acquires from the application server startup information management unit 113 a startup application server name corresponding to the requested application server name requested to be started, and determines whether or not the specified startup application server name has already been started. Refer to the application server information. If the start application server name is already registered in the application server name of the application server information, it means that the application server is being started.

Process 1-5: First, a case where the device has not been started will be described.
Go to -6).

Process 1-51: The designated application server 112 is in the application server information section 11
4, the application server 112 refers to the application server activation information management unit 113 to activate the specified application server 112, and reads the activation parameters of the application server 112. The start parameters are the start application server name, the number of threads, and the maximum number of accesses that can communicate with the application server. The information is read and the application server 112 is started.

Process 1-52: Application server 1
12 is activated, the binding information transmitting unit 112
1 transmits the binding information of the application server 112 to the binding information receiving unit 11111.

Process 1-53: start procedure 1111
Upon receiving the binding information, the binding information receiving unit 11111 of the application determines the application server name, the binding information of the application server, the client information of the client that is started and accessed, and the maximum number of accesses that can communicate with the application server, by using the startup procedure 1111. It is registered in the application server information unit 114 as server information, and returns the binding information of the activated application server 112 to the remote procedure control unit 1112 as the execution result of the activation procedure 1111.

Process 1-54: The remote procedure control unit 1112 returns the binding information of the application server 112 to the remote procedure control unit 122 as a result of executing the start procedure 1111.

Process 1-55: The remote procedure control unit 122 passes the returned binding information to the application 121. Application 1
21 can communicate with the application server 112 using the binding information.

Process 1-6: Next, it is assumed that the application server 112 has already been started by another client, and in that state, the client 12 has executed the start procedure 1111 for starting the application server 112.

Process 1-61: In process 1-4, as a result of reference, it is known that the device is already running, so the maximum access number is compared with the number of client information.

Process 1-62: As a result of the comparison, if the client 12 is accessed but the access is less than the maximum access, the binding information of the running application server 112 is obtained from the application server information unit 114 and the binding information of the running application server name is obtained. And bind the binding information to the startup procedure 1
The execution result of step 111 is returned to the remote procedure control unit 122 of the client.

Process 1-63: The remote procedure control unit 122 passes the returned binding information to the application 121. Application 1
21 can communicate with the application server 112 using the binding information.

Process 1-64: On the other hand, if the maximum access number is exceeded in process 1-61, another new application server is started, and the client is newly started by the application server starting procedure from the client. By returning the binding information of the application server, the client can access the newly started application server.

As described above, in the present embodiment, by providing the management server that manages the activation status of the application server, the required minimum number of application servers can be reduced without activating many application servers as in the related art. It is possible to start up and communicate with a plurality of clients, thereby reducing the consumption of physical resources of the machine.

For example, if the client cannot access the management server for some reason after the management server starts the application server, a new management server is started manually or the like, and the client sends the management server to the management server. Even if an application server start request is issued to the application server, the management server can grasp the information of the application server being started by referring to the application server start information management unit and the application server management unit. It can also prevent the application server from starting.

Further, even when there is one application server for the management server, machine resources can be suppressed by using a plurality of threads, and the practical effect is large.

(Embodiment 2) FIG. 2 shows an example of a client / server system according to the present invention. In FIG. 2, reference numeral 21 denotes a server, 211 denotes a management server for managing the activation status of an application server, and 2111. Is a start procedure. When a client requests execution of the start procedure 2111, a start application name corresponding to the specified requested application server name is obtained from the application server start information management unit 213 and started by the CPU monitoring unit 21112. An inquiry is made as to whether the application server can be activated. If the application server can be activated, the application server having the acquired activation application server name is activated, and the binding information of the activated application server is received from the binding information receiving unit 21111. To register the information of the application server that was started in over server information section 214. If the result of the inquiry to the CPU monitoring unit 21112 indicates that it cannot be started,
Remote procedure control unit 2 sends information that it cannot be started
Return to 112.

Reference numeral 21111 denotes a binding information receiving unit which receives the binding information of the application server from the binding information transmitting unit of the application server activated from the activation procedure 2111.

Reference numeral 21112 denotes a CPU monitoring unit which refers to the idle threshold value corresponding to the application server to be activated by the application server activation information management unit 213 when the application server is activated, and compares it with the actual idle value of the server. . When the actual load of the server is lower than the idle threshold value of the application server start information management unit 213, information that the server can be started is returned to the start procedure 2111, and the actual load is higher than the idle threshold value of the application server start information management unit 213. Sometimes, information that startup is impossible is performed by the startup procedure 211.
Return to 1.

Reference numeral 2112 denotes a remote procedure control unit which receives a request to execute the start procedure 2111 from the remote procedure control unit of the client, executes the content of the request, and returns the execution result to the remote procedure control unit of the client.

An application server 212 receives a remote procedure call from a client.
Reference numeral 2121 denotes a binding information transmission unit which transmits the binding information of the application server to the management server 211.
Is transmitted to the binding information receiving unit 21111.

Reference numeral 2122 denotes a remote procedure, which registers a procedure executable by the client.
Reference numeral 2123 denotes a remote procedure control unit which receives the execution request of the remote procedure 2122 from the client remote procedure control unit, executes the content of the request, and returns the execution result to the client remote procedure control unit.

Reference numeral 213 denotes an application server start information management unit for managing a start application server name corresponding to an application server name requested to be started by a client. The start application server name corresponding to the application server name, the number of threads when starting the application server, and the maximum access number.

Reference numeral 214 denotes an application server information section which stores information on the application server and information on the client being accessed when the application server is started by the start procedure 2111. The name of the started application server, binding information, and information on the accessing client are stored. , The maximum number of accesses is written.

Reference numeral 22 denotes a client, 221 denotes an application, and a start procedure 211 registered in the management server 211 and the application server 212.
1. Request execution of remote procedure 2122.

Reference numeral 222 denotes a remote procedure control unit.
The management server 211 or the application server 212 is accessed using the binding information passed from the application 221, and the start procedure 2 is transmitted to the remote procedure control unit 2112 of the management server 211.
The execution request of the remote procedure 2122 is transmitted from the remote procedure control unit 2112 and the remote procedure control unit 2123 to the remote procedure control unit 2123 of the application server 212. Receive. 23 is a communication path.

The operation of the client / server system configured as described above will be described with reference to FIG.

On the server 21, only the management server 211 has been activated, and is in a state of waiting for an execution request of the activation procedure 2111 from the client 22. The client 22 is a management server 211 of the server 21.
Knows the binding information of the management server 211
Can be executed.

Process 2-1: First, the client 22
The application 221 executes a start procedure 2111 for starting the application server 212 using the binding information of the management server 211 and the name of the requesting application server to be requested to start as parameters.

Process 2-2: The remote procedure control unit 222 accesses the request to the management server 211 using the binding information of the management server 211, and executes the start procedure 2111 together with the parameter to the remote procedure control unit 2111 of the management server 211. Request.

Process 2-3: Upon receiving the request from the client 22, the remote procedure control unit 2112 of the management server 211 executes the start procedure 2111 using the request application server name as a parameter.

Process 2-4: Start-up procedure 2111
Acquires the start application server name corresponding to the requested application server name from the application server start information management unit 213, and determines whether or not the specified start application server name has already been started. Refer to the application server information. If the start application server name is already registered in the application server name of the application server information, it means that the application server is being started.

Process 2-5: In the following example, a case where it has not been started will be described. Process 2-51: designated application server 21
2 is not registered in the application server information section 214, so that the designated application server 21
2 to determine whether the load is ready to be activated
An inquiry is made to the PU monitoring unit 21112.

Process 2-52: CPU monitoring unit 21112
Refers to the idle threshold value of the application server activation information management unit 213 corresponding to the application server to be activated, and compares it with the actual idle value of the server 21.

Process 2-53: First, the case where the actual load of the server 21 is lower than the idle threshold value will be described (if the load is higher, the process proceeds to the later-described process 2-54).

Process 2-531: CPU monitoring unit 21112
Returns to the activation procedure 2111 that the server 21 can be activated because the actual idle value of the server 21 is lower than the idle threshold. The startup procedure 2111 is executed by the CPU
Since a result indicating that the application server can be started is obtained from the monitoring unit 211112, the application server start information management unit 213
And reads the start parameter of the corresponding application server 212. The start parameters are the start application server name, the number of threads, and the maximum number of accesses that can communicate with the application server. The information is read and the application server 212 is started.

Process 2-532: When the application server 212 is started, the binding information transmitting unit 21
21 transmits the binding information of the application server 212 to the binding information receiving unit 21111.

Process 2-533: start procedure 211
When the binding information is received, the binding information receiving unit 21111 receives the application information, and executes the activation procedure 2111 to execute the application server name, the binding information of the application server, the client information of the activated and accessed client, and the maximum number of accesses that can communicate with the application server 212. The application server information registration unit 214 registers, as application server information, an idle threshold value indicating an allowable range of application server activation corresponding to the activated application server recorded in the application server activation information management unit 213 in the application server information unit 214. Startup procedure 2 for binding information of 212
111 as the execution result of the remote procedure control unit 2
Return to 112.

Process 2-534: The remote procedure control unit 2112 returns the binding information of the application server 212 to the remote procedure control unit 222 as a result of executing the activation procedure 2111.

Process 2-535: The remote procedure control section 222 passes the returned binding information to the application 221. The application 221 can communicate with the application server 212 using the binding information.

Process 2-54: Next, in the process 2-52, when the CPU monitoring unit 21112 makes a comparison, the server 2
A case in which the actual load of one is higher than the idle threshold will be described.

Process 2-541: CPU monitoring unit 21112
Returns to the start procedure 2111 that the server 21 cannot be started because the actual idle value of the server 21 is higher than the idle threshold value.

Process 2-542: start procedure 211
1 obtains from the CPU monitoring unit 21112 that the server 21 cannot be started, and returns a result indicating that the server 21 cannot be started due to a high load to the remote procedure control unit 2112 as an execution result of the start procedure 2111.

Process 2-543: The remote procedure control unit 2112 returns a message to the remote procedure control unit 222 to the effect that starting is impossible due to high load as the execution procedure 2111 execution result.

Process 2-544: The remote procedure control unit 222 sends the returned result to the application 22
Pass to 1.

Process 2-545: Application 221
Indicates that the application server 212 cannot be started because the server 21 is currently under heavy load.

In the process 2-4, the application server 212 has already been activated by another client, and in this state, the activation procedure 211 for activating the application server 212 from the client 22 is performed.
When Step 1 is executed, the same processing as the processing 1-6 and the subsequent steps in the first embodiment is performed.

As described above, in the present embodiment, by providing the CPU monitoring unit 21112 in the start procedure 2111 in the management server 211, in addition to the effect of the first embodiment, the present invention is further applied to the case where the application server 212 is started. In addition, when the server is under a heavy load, the activation of the application server from the client can be refused, and the practical effect is great.

(Embodiment 3) FIG. 3 shows an example of a client / server system according to the present invention. In FIG. 3, reference numeral 31 denotes a server, 311 denotes a management server for managing the activation status of an application server, 3111 Is a start-up procedure. When execution of this start-up procedure is requested from the client 32, a start-up application name corresponding to the specified request application server name is obtained from the application server start-up information management unit 313, and the obtained start-up application server name is obtained. , The binding information of the activated application server is received from the binding information receiving unit 31111, and the information of the activated application server is registered in the application server information unit 314.

Reference numeral 31111 denotes a binding information receiving unit which receives the binding information of the application server 312 from the binding information transmitting unit 3121 of the application server activated from the activation procedure 3111.

Reference numeral 3112 denotes a remote procedure control unit which receives a request to execute the start procedure 3111 from the client remote procedure control unit, executes the request, and returns the execution result to the client remote procedure control unit.

An application server 312 receives a remote procedure call from a client.
Reference numeral 3121 denotes a binding information transmission unit which transmits the binding information of the application server to the management server 311.
To the binding information receiving unit 31111.

Reference numeral 3122 denotes a remote procedure which registers a procedure which can be executed by the client.
According to the result of the inquiry to the CPU monitoring unit 31221,
Execute or reject remote procedures.

Reference numeral 31221 denotes a CPU monitoring unit, which refers to an idle threshold value corresponding to the application server to be activated by the application server activation information management unit 313 when executing a remote procedure, and compares it with the actual idle value of the server. When the actual load of the server is lower than the idle threshold value of the application server information section 314, information that the server can be executed is returned to the remote procedure,
When the actual load is higher than the idle threshold value of the application server information unit 314, information indicating that execution is impossible is returned to the remote procedure.

Reference numeral 3123 denotes a remote procedure control unit which receives a request for executing the remote procedure 3122 from the remote procedure control unit of the client, executes the content of the request, and returns the execution result to the remote procedure control unit of the client.

Reference numeral 313 denotes an application server start information management unit for managing a start application server name corresponding to an application server name requested to be started by a client. The start application server name corresponding to the application server name, the number of threads and the maximum number of accesses when starting the application server, and the idle threshold value for restricting the execution of the remote procedure.

Reference numeral 314 denotes an application server information section for storing the information of the application server and the information of the client being accessed when the application server is activated by the activation procedure. The name of the activated application server, the binding information, the accessing client information, The maximum number of accesses and the idle threshold to limit the execution of remote procedures are written.

Reference numeral 32 denotes a client, and 321 denotes an application, which requests execution of a start procedure and a remote procedure registered in the management server and the application server.

Reference numeral 322 denotes a remote procedure control unit.
The management server 311 or the application server 312 is accessed using the binding information passed from the application 321, and the start procedure 3 is sent to the remote procedure control unit 3112 of the management server 311.
The execution request of the remote procedure 3122 is transmitted to the remote procedure control unit 3123 of the application server 312, and the execution results of the start procedure 3111 and the remote procedure 3122 are transmitted from the remote procedure control unit 3112 and the remote procedure control unit 3123, respectively. Receive. 33 is a communication path.

The operation of the client / server system configured as described above will be described with reference to FIG.

In the state where only the management server 311 is running on the server 31, the management server 311 receives a start request of the application server 312 from the client 32, and executes the application server 312 in the same procedure as in the first embodiment. Is executed, that is, the processing is performed up to the processing 1-55, and the communication with the application server 312 is started.

Process 3-1: First, the client 32
From application 321 to application server 3
The remote procedure 312 of the application server 312 using the binding information of
Execute Step 2.

Process 3-2: The remote procedure control unit 322 transmits the request using the binding information of the application server 312 to the application server 31.
2 and requests the remote procedure control unit 3123 of the application server 312 to execute the remote procedure 3122 together with the parameters.

Process 3-3: Application server 31
Upon receiving the request from the client 32, the second remote procedure control unit 3123 executes the requested remote procedure 3122.

Process 3-4: remote procedure 312
2 indicates that the load on the server 31 is
An inquiry is made to the CPU monitoring unit 3221 to confirm whether or not Step 2 is executable.

Process 3-5: The CPU monitoring section 3221
The application server activation information management unit 313 refers to the idle threshold value corresponding to the application server 312 that executes the remote procedure 3122, and compares it with the actual idle value of the server 31.

Process 3-6: First, a case where the actual load of the server 31 is lower than the idle threshold value will be described (while,
If it is higher, the process proceeds to the process 3-7 described later).

Process 3-61: CPU monitoring section 3221
Returns to the remote procedure 3122 that the server 31 is executable because the actual idle value is lower than the idle threshold.

Process 3-62: remote procedure 31
22 has obtained a result that it can be executed from the CPU monitoring unit 31221, and
Is executed, and the execution result is sent to the mote procedure control unit 312.
Return to 3.

Process 3-63: The remote procedure control unit 3123 returns the execution result of the remote procedure 3122 to the remote procedure control unit 322.

Process 3-64: The remote procedure control unit 322 sends the returned result to the application.
Give one.

Process 3-7: Next, a description will be given of a case where the actual load of the server 31 is higher than the idle threshold value at the time of comparison by the CPU monitoring section 3221 in the process 3-5.

Process 3-71: CPU monitoring section 31221
Returns to the remote procedure 3122 that execution is not possible because the actual idle value of the server 31 is higher than the idle threshold.

Process 3-72: Remote procedure 31
The server 22 returns a result to the remote procedure control unit 3123 to the effect that the remote procedure 3122 cannot be executed due to a high load, because the server monitoring unit 31221 obtains a result indicating that the remote procedure 3122 cannot be executed.

Process 3-73: The remote procedure control unit 3123 returns a message to the effect that it cannot be executed due to a high load to the remote procedure control unit 322 as an execution result of the remote procedure 3122.

Process 3-74: The remote procedure control unit 322 sends the returned result to the application 321.
Pass to Based on the result, the application 321 has determined that the remote procedure 31
22 can not be executed.

As described above, in the present embodiment, by providing the CPU monitoring unit in the remote procedure of the application server, in addition to the effect of the first embodiment, the server can be used when the remote procedure 3122 is executed. When the load is high, the execution of the remote procedure from the client is refused, that is, the performance of other processes can be emphasized, and the practical effect is great.

(Embodiment 4) FIG. 4 shows an example of a client / server system according to the present invention. In FIG. 4, reference numeral 41 denotes a server, 411 denotes a management server for managing the activation status of an application server, 4111 Is a start procedure. When the client 42 requests execution of this start procedure, the start application name corresponding to the specified requested application server name is obtained from the application server start information management unit 413, and the obtained start application server name is obtained. , The binding information of the activated application server is received from the binding information receiving unit 41111, and the information of the activated application server is registered in the application server information unit 414.

Reference numeral 41111 denotes a binding information receiving unit which receives the binding information of the application server 412 from the binding information transmitting unit 4121 of the application server activated from the activation procedure 4111.

Reference numeral 4112 denotes an alternative application server start procedure. When execution of this start procedure is requested by the client 42, a start application name corresponding to the specified requested application server name is obtained from the application server start information management unit 413. Then, the application server having the acquired application server name is activated, the binding information of the activated application server is received from the binding information receiving unit 4121, and the information of the activated application server is registered in the application server information unit 414.

Reference numeral 41121 denotes a binding information receiving unit which receives the binding information of the alternative application server 415 from the binding information transmitting unit 4151 of the alternative application server 415 activated from the alternative application activation procedure 4112.

Reference numeral 4113 denotes a remote procedure control unit.
Receives the execution request of the start procedure 4111 or the alternative application server start procedure 4112 from the client, executes the contents of the request, and returns the execution result to the remote procedure control unit 422 of the client.

An application server 412 receives a remote procedure call from a client, and has the same configuration as the first embodiment, that is, the application server 112 in FIG.

Reference numeral 415 denotes an alternative application server that receives a remote procedure call from the client 42. Reference numeral 4151 denotes a binding information transmitting unit that transmits the binding information of the alternative application server 415 to the binding information receiving unit of the alternative application server activation procedure 4112 of the management server 411. 41
Send to 121.

Reference numeral 4152 denotes a remote procedure, which registers a procedure executable by the client.

Reference numeral 4153 denotes a remote procedure control unit.
In response to the execution request of the remote procedure 4152 from the client 22, the request is executed and the execution result is returned to the remote procedure control unit 422 of the client 42.

An application server start information management unit 413 manages a start application server name corresponding to an application server name requested to be started by the client 42. The stored information includes a requested application server name requested to be started by the client, The start application server name corresponding to the request application server name, the number of threads for starting the application server, and the maximum number of accesses.

Reference numeral 414 denotes an application server information section for storing information on the application server 412 or the alternative application server 415 and the client information being accessed when the application server 412 or the alternative application server 415 is activated by the activation procedure 4111. The server name, the binding information, the accessing client information, and the maximum number of accesses are written.

Reference numeral 42 denotes a client, 421 denotes an application, and a start procedure 411 registered in the management server 411 and the application server 412.
1. Request execution of the remote procedure 4122.

Reference numeral 422 denotes a remote procedure control unit.
Using the binding information passed from the application 421, the management server 411, the application server 412, or the alternative application server 4
15 and requests the remote procedure control unit 4113 of the management server 411 to execute the start procedure 4111, requests the remote procedure control unit 4113 of the management server 411 to execute the alternative application server start procedure 4112, and executes the application server 41.
The remote procedure control unit 411 transmits an execution request of the remote procedure 4122 to the remote procedure control unit 4123, and transmits the execution results of the start procedure 4111, the alternative application server start procedure 4112, and the remote procedure 4152 to the remote procedure control unit 411, respectively.
3. Received from the remote procedure control unit 4153. 43 is a communication path.

The operation of the client / server system configured as described above will be described with reference to FIG.

On the server 41, in a state where only the management server 411 has been started, the management server 411 receives a request for starting the application server 412 from the client 42, and (in the first embodiment) executes the same procedure as that of the application server 412 according to the same procedure. Step of executing startup, that is, processing 1
It is assumed that the process is performed up to −55 and communication and activation with the application server 412 are possible.

However, a failure has occurred in the application server 412, and the application server 41
It is assumed that the access to No. 2 is disabled.

Process 4-1: First, the client 42
Application 421 to application server 4
The remote procedure 412 of the application server 412 using the binding information of
2 is requested.

Process 4-2: The remote procedure control unit 422 attempts to access the request to the application server 412 using the binding information of the application server 412.

Process 4-3: However, the remote procedure control unit 422 returns a communication error to the application 421 because communication from the client 42 is disabled due to a failure in the application server 412.

Process 4-4: The application 421
In order to start the alternative application server 415,
The alternative application server start procedure 4112 is executed using the binding information of the management server 411 and the alternative application server name as parameters.

Process 4-5: The remote procedure control unit 422 accesses the request to the management server 411 using the binding information of the management server 411, and sends the request to the remote procedure control unit 4113 of the management server 411 together with the parameters together with the alternative application server start procedure. 4112 is requested.

Processing 4-6: Upon receiving the request from the client 42, the remote procedure control unit 4113 of the management server 411 executes the alternative application server start procedure 4112 using the name of the alternative application server that has requested the start as a parameter.

Process 4-7: The alternative application server start procedure 4112 stores the start application server name corresponding to the requested application server name requested to be started by the application server start information management unit 41.
3 and refers to the application server information in the application server information section 414 to determine whether the specified activation application server name has already been activated. If the start application server name is already registered in the application server name of the application server information, it means that the application server is being started.

Process 4-8: First, the case where the device has not been started will be described.
Go to -9).

Process 4-81: Since the designated alternative application server 415 is not registered in the application server information section 414, refer to the application server activation information management section 413 to activate the designated alternative application server 415. Then, the corresponding application server 415 is read. The start parameters are the start application server name, the number of threads, and the maximum number of accesses that can communicate with the application server. The information is read and the alternative application server is started.

Process 4-82: When the alternative application server 415 is started, the binding information transmitting unit 4
151 transmits the binding information of the alternative application server 415 to the binding information receiving unit 41121.

Process 4-83: The binding information receiving section 41121 of the alternative application server start procedure 4112 receives the binding information, and
12 registers the application server name, the binding information of the application server 415, the client information of the activated and accessed client, and the maximum number of accesses that can communicate with the application server 415 in the application server information section 414 as the application server information. Deletes the information of the client 42 from the client information of the application server information section 414 relating to the application server 412 used so far, and replaces the binding information of the activated alternative application server 415 with the alternative application server activation procedure 411.
2 as the execution result of the remote procedure control unit 411
Return to 3.

Process 4-84: The remote procedure control unit 4113 returns the binding information of the alternative application server 415 to the remote procedure control unit 422 as the execution result of the alternative application server start procedure 4112.

Process 4-85: The remote procedure control unit 422 passes the returned binding information to the application 421. Application 4
21 can communicate with the alternative application server 415 using this binding information.

Process 4-9: It is assumed that the alternative application server 415 has already been started by another client, and in this state, the alternative application server start procedure 4112 for starting the alternative application server 415 from the client 42 has been executed.

Process 4-91: First, the client executes the alternative application server start procedure 4112 from the application 42 with the binding information of the management server 411 and the name of the alternative application server to be requested to start as parameters.

Process 4-92: The remote procedure control section 422 accesses the request to the management server 411 using the binding information of the management server 411, and sends the request to the remote procedure control section 4113 of the management server 411 together with the parameters together with the alternative application server start procedure. 4112 is requested.

Process 4-93: Upon receiving the request from the client 42, the remote procedure control unit 4113 of the management server 411 executes the alternative application start procedure 4112 using the parameter of the request alternative application server name.

Process 4-94: The substitute application start procedure 4112 sets the start application server name corresponding to the requested substitute application server name requested to be started to the application server start information management section 41.
3, the application server information of the application server information section 414 is referred to as to whether the specified start application server name has already been started.

Process 4-95: As a result of the reference, it is known that the device is already running. Then, the maximum access number is compared with the number of client information.

Process 4-96: As a result of the comparison, if the client 42 is accessed but the access is less than the maximum access, the binding information of the activated alternative application server 415 is stored in the application server information section 414.
From the client information in the application server information section 414 relating to the application server 412, the binding information of the client 42 is deleted, and the acquired binding information is used as the execution result of the alternative application server startup procedure 4112. Return to remote procedure control unit 4113.

Process 4-97: The remote procedure control unit 4113 returns the binding information of the alternative application server 415 to the remote procedure control unit 422 as the execution result of the alternative application server start procedure 4112.

Process 4-98: The remote procedure control unit 422 passes the returned binding information to the application 421. Application 4
21 can communicate with the alternative application server 415 using this binding information.

Process 4-99: On the other hand, in the process 4-95, when comparing the client information of the application server information section 414 with the maximum access number, if the number of clients to be accessed exceeds the maximum access number, a new application server is set. The client can access the newly started alternative application server by starting up and returning the binding information of the newly started up alternative application server to the client in the above described starting procedure of the alternative application server from the client.

In the present embodiment, the alternative application server 4
Although the relationship of No. 15 is positioned as a slave (temporary standby server) with respect to the master (normally used server), it eliminates the confusingness of the description, and the application server and the alternative application server are used. The relationship between and may be equally determined such that the master and the master are equally positioned.

As described above, in the present embodiment, the management server 411 is further provided with the alternative application server start procedure 4112, whereby the first embodiment is provided.
In addition to the effects of the above, even in the event of an application server failure, the alternative application server can be used by receiving another designation from the client (alternate application server) different from the application server. As you can see, the remote procedure can be executed, and its practical effect is great.

(Embodiment 5) FIG. 5 shows an example of a client / server system according to the present invention. In FIG. 5, reference numeral 51 denotes a server, and 511 denotes a management server for executing a history information acquisition procedure.

Reference numeral 5111 denotes a history information acquisition procedure. When execution of this procedure is requested by the client 52, the execution result is obtained based on the application server name, remote procedure name, and remote procedure arguments written in the history information section 513. Acquired and returned to the client 52 as the execution result of the history information acquisition procedure.

Reference numeral 5112 denotes a remote procedure control unit.
In response to the execution request of the history information acquisition procedure 5111 from the client 22, the content of the request is executed, and the execution result is transmitted to the remote procedure control unit 52 of the client 52.
Reply to 2.

An application server 512 receives a remote procedure call from the client 52, and a remote procedure 5121 registers a procedure that can be executed by the client.

Numeral 51211 denotes a history information writing unit.
The client information of the client 52 requesting the execution of the remote procedure 5121, the name of the application server having the remote procedure, the name of the remote procedure, the argument of the remote procedure, and the error information of the remote procedure are written in the history information section 513 when the remote procedure is executed.

Reference numeral 5112 denotes a remote procedure control unit.
In response to the execution request of the remote procedure 5121 from the client 22, the content of the request is executed, and the execution result is returned to the remote procedure control unit 522 of the client 52.

Reference numeral 513 denotes a history information section for storing the execution result of the remote procedure requested to be executed by the client 52, the client information requesting the execution of the remote procedure, the name of the application server provided with the remote procedure, and the executed remote procedure. Stores the name, remote procedure arguments, and remote procedure error information.

A client 52 and an application 521 request execution of a history information acquisition procedure and a remote procedure registered in the management server and the application server.

Reference numeral 522 denotes a remote procedure control unit.
The management server 511 or the application server 512 is accessed using the binding information passed from the application 521, and a request to execute the history information acquisition procedure 5111 to the remote procedure control unit 5112 of the management server 511, and the remote procedure control unit 5122 of the application server 512. Request to execute the remote procedure 5121, the activation procedure 5111 and the remote procedure 512.
1 to the remote procedure control unit 5
112, received from the remote procedure control unit 5122. 53 is a communication path.

The operation of the client / server system configured as described above will be described with reference to FIG.

On the server 51, the management server 511 and the application server 512 are activated, and the history information acquisition procedure 5 from the client 52 is executed.
It is in a waiting state for an execution request of the remote procedure 111 and the remote procedure 5121. Further, it is assumed that the client 52 knows the binding information of the management server 511 and the application server 512 of the server 51, and can execute the history information acquisition procedure 5111 and the remote procedure 5121 of the management server 511.

Process 5-1: First, the client 52
Application 521 to application server 5
A request for execution of the remote procedure 5121 on the application server 512 is made using the binding information of Twelve.

Process 5-2: The remote procedure control unit 522 sends the request to the application server 51 using the binding information of the application server 512.
2 and requests the remote procedure control unit 5122 of the application server 512 to execute the remote procedure 5121.

Process 5-3: Application server 51
When receiving the request from the client 52, the second remote procedure control unit 5122 executes the requested remote procedure 5121.

Process 5-4: remote procedure 512
1 transfers to the history information writing unit 51211 the error information, the client information requesting the execution of the remote procedure 5121, the name of the application server having the remote procedure, the remote procedure name, and the argument of the remote procedure.

Process 5-5: History information writing section 51
211 is client information received as a parameter,
Application server name, remote procedure name,
The arguments of the remote procedure and error information are written to the history information section 513. When writing is completed,
The remote procedure 5121 transmits the execution result of the remote procedure 5121 to the remote procedure control unit 5.
Return to 122.

Process 5-6: The remote procedure control unit 5122 returns the execution result of the remote procedure 5121 to the remote procedure control unit 522.

Process 5-7: The remote procedure control unit 522 passes the returned result to the application 521.

Here, the client 52 executes the remote procedure 5121 of the application server 512 according to the above procedure, and
Before the execution result of the remote procedure 5121 is obtained from the remote procedure control unit 5122 on the client 2 to the remote procedure control unit 522 of the client, the execution result cannot be obtained due to a failure such as a power failure on the client side.

Process 5-8: After recovery from the failure, first, the client 52 sends the management server 5
A request for executing the history information acquisition procedure 5111 on the management server 511 is made using the binding information of No. 11, the name of the application server having the remote procedure executed immediately before, the name of the remote procedure, and the arguments of the remote procedure as parameters.

Processing 5-9: The remote procedure control unit 522 accesses the request to the management server 511 by using the binding information of the management server 511, and executes the history information acquisition procedure 5111 to the remote procedure control unit 5112 of the management server 511. Request.

Process 5-10: Application server 5
The twelfth remote procedure control unit 5112 causes the requested history information acquisition procedure 5111 to be executed.

Process 5-11: History information acquisition procedure 5111
History information writing unit 5 based on the client information requesting execution of the client application 1, the name of the application server providing the remote procedure acquired as a parameter, the name of the remote procedure, and the arguments of the remote procedure.
The error information of the corresponding procedure is acquired by referring to the information written in 1211 and the result is returned to the remote procedure control unit 5112.

Process 5-12: The remote procedure control unit 5112 executes the history information acquisition procedure 5111
The execution result is returned to the remote procedure control unit 522.

Process 5-13: The remote procedure control unit 522 sends the returned result to the application 521.
Pass to

As described above, in the present embodiment, the history information procedure is provided in the management server even if the execution result of the remote procedure cannot be obtained due to a failure such as a power failure on the client side. By providing the history information section, after the failure recovery, by executing the history information acquisition procedure, the execution result of the remote procedure before the failure can be obtained, and it is determined whether the remote procedure needs to be re-executed. And its practical effect is great.

[0170]

Thus, according to the first aspect, the management server can utilize the information of the application server, associate a plurality of clients with one application server, and suppress the consumption of physical resources of the server. The advantageous effect described above can be obtained.

According to the second invention, the management server is provided with the CPU
By providing a CPU monitoring unit for monitoring the load on the application server, the CPU monitoring unit for monitoring the load on the CPU in the application server is provided. Control rejection,
An advantageous effect that the load on the server can be stabilized can be obtained.

According to the third aspect of the present invention, by further providing a remote procedure for starting another application server in the event of a failure of an application server in the management server, the management server can substitute an alternative application server even if a failure occurs in the application server. This has the advantageous effect that the client can execute the remote procedure of the alternative application server.

According to the fourth aspect, a storage device for storing information executed by a remote procedure of an application server in a server, and a remote procedure capable of acquiring information executed by a remote procedure stored in the storage device Is registered in the management server, it is possible to obtain an advantageous effect that a result of a remote procedure that cannot be obtained as a normal end due to a client failure can be obtained.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration example of a client / server system according to a first embodiment of the present invention;

FIG. 2 is a diagram showing a configuration example of a client / server system according to a second embodiment of the present invention;

FIG. 3 is a diagram showing a configuration example of a client / server system according to a third embodiment of the present invention;

FIG. 4 is a diagram showing a configuration example of a client / server system according to a fourth embodiment of the present invention;

FIG. 5 is a diagram showing a configuration example of a client / server system according to a fifth embodiment of the present invention.

FIG. 6 is a diagram showing a configuration example of a conventional client / server system.

[Explanation of symbols]

11 server 111 management server 1111 startup procedure 11111 binding information receiving unit 1112 remote procedure control unit 112 application server 1121 binding information transmission unit 1122 remote procedure 1123 remote procedure control unit 113 application server startup information management unit 114 application server information unit 12 client 121 application 122 remote procedure control unit 13 communication path 21 server 211 management server 2111 start procedure 21111 binding information receiving unit 21112 CPU monitoring unit 2112 remote procedure control unit 212 application server 2121 binding information transmitting unit 2122 remote procedure 2123 Remote procedure control unit 213 Application server start information management unit 214 Application server information unit 22 Client 221 Application 222 Remote procedure control unit 23 Communication path 31 Server 311 Management server 3111 Startup procedure 31111 Binding information receiving unit 3112 Remote procedure author 312 Application server 3121 Binding information transmission unit 3122 Remote procedure 31021 CPU monitoring unit 3123 Remote procedure control unit 313 Application server startup information management unit 314 Application server information unit 32 Client 321 Application 322 Remote procedure control unit 33 Communication path 41 Server 411 Management server 41 11 Start Procedure 41111 Binding Information Receiving Unit 4112 Alternative Application Server Starting Procedure 41121 Binding Information Receiving Unit 4113 Remote Procedure Control Unit 412 Application Server 4121 Binding Information Sending Unit 4122 Remote Procedure 4123 Remote Procedure Control Unit 413 Application Server Start Information Management Unit 414 Application Server Information section 415 Alternative application server 4151 Binding information transmission section 4152 Remote procedure 4153 Remote procedure control section 42 Client 421 Application 422 Remote procedure control section 43 Communication path 51 Server 511 Management server 5111 History information acquisition procedure Key 5112 remote procedure control unit 512 application server 5121 remote procedure 5121 history information writing unit 5122 remote procedure control unit 513 history information unit 52 client 521 application 522 remote procedure control unit 53 communication path 61 server 611 application server 6111 remote procedure 6112 remote procedure control Unit 612 application server 6121 remote procedure 6122 remote procedure control unit 62 client 621 application 622 remote procedure control unit 63 communication path

Claims (5)

[Claims] 1. A client / server system in which a client performing a processing request and a server receiving the processing request are connected via a communication path, wherein the server includes an application server having a remote procedure requested to be executed by the client. A management server that manages the start status of the application server, an application server start information management unit that manages parameters when the application server is started, and an application server information unit that stores information about the started application server. A first remote procedure control unit for receiving a remote procedure execution request from the client and returning a result of the remote procedure to the client in the server; Start the server,
An activation procedure having a binding information receiving unit for receiving the binding information of the application server; a binding information transmitting unit for transmitting the binding information of the application server to the management server in the application server; A client / server system comprising: a possible remote procedure; and a second remote procedure control unit that receives a remote procedure execution request from the client and returns a result of the remote procedure to the client. 2. The client / server system according to claim 1, further comprising a CPU monitoring unit that monitors a load on a CPU of the server in a startup procedure of the management server. 3. The client / server system according to claim 1, further comprising a CPU monitoring unit that monitors a load on a CPU of the server in a remote procedure of the application server. 4. A failure reception remote procedure for receiving a failure notification of an application server in a management server of the server, wherein a failure occurs in an application server designated by a client, and a failure occurs between the client and the application server. The client / server according to any one of claims 1 to 3, wherein, in a case where communication becomes impossible, the failure reception remote procedure starts a substitute application server newly designated by the client. system. 5. A storage device for storing a result of a remote procedure of an application server in a server; an information acquisition remote procedure for retrieving a result of the remote procedure by the application server from the storage device as a remote procedure in a management server; A history information writing unit for writing the result of the remote procedure to the history information is provided in the procedure, and when a failure occurs in the client and the result of the remote procedure cannot be obtained from the application server, the history stored in the management server is stored in the client. Requesting execution of an information acquisition procedure to acquire, from the storage device, a result of the remote procedure requested before a failure of the client. Motomeko 1
5. The client / server system according to any one of claims 1 to 4.