EP1057108A1 - Procede et appareil utilises pour la suspension et la poursuite de processus eloignes - Google Patents

Procede et appareil utilises pour la suspension et la poursuite de processus eloignes

Info

Publication number
EP1057108A1
EP1057108A1 EP99936131A EP99936131A EP1057108A1 EP 1057108 A1 EP1057108 A1 EP 1057108A1 EP 99936131 A EP99936131 A EP 99936131A EP 99936131 A EP99936131 A EP 99936131A EP 1057108 A1 EP1057108 A1 EP 1057108A1
Authority
EP
European Patent Office
Prior art keywords
remote method
resources
remote
server system
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP99936131A
Other languages
German (de)
English (en)
Inventor
Kenneth C. R. C. Arnold
Ann M. Wollrath
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sun Microsystems Inc
Original Assignee
Sun Microsystems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US09/044,917 external-priority patent/US6237024B1/en
Application filed by Sun Microsystems Inc filed Critical Sun Microsystems Inc
Publication of EP1057108A1 publication Critical patent/EP1057108A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/465—Distributed object oriented systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/42—Loop networks
    • H04L12/427—Loop networks with decentralised control
    • H04L12/433—Loop networks with decentralised control with asynchronous transmission, e.g. token ring, register insertion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/468—Specific access rights for resources, e.g. using capability register
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G06F9/5022—Mechanisms to release resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • G06F9/548—Object oriented; Remote method invocation [RMI]

Definitions

  • This invention generally relates to distributed computing systems and more particularly, to a method and apparatus for the suspension and continuation of remote processes.
  • a typical distributed computing system makes the services and computing power of many servers available to many different clients over a network.
  • a client machine accesses processing capabilities on a server machine using a remote procedure call (RPC) system.
  • RPC remote procedure call
  • the RPC system processes the request on the remote machine and returns the desired results to the requesting client.
  • the network used to transmit the request and return the results can be a local area network (LAN), a wide area network (WAN), and can also include the Internet.
  • Sophisticated distributed computing applications on the Internet offer electronic commerce (e- commerce), telecommuting, and interactive entertainment services around the world using this client-server arrangement.
  • Each request from a client generally causes a server process to designate resources, 4 including one or more threads, to process the requests.
  • a thread sometimes called a lightweight process, is a separate sequence of instructions within a process having a separate flow of control. The thread must carve out resources from the system as needed to fulfill the particular request. If resources such as memory and data are available, multiple threads can be executed in parallel to fulfill multiple tasks.
  • Thread schedulers can be used by the process spawning the threads to coordinate parallel execution of the threads based on a thread's priority, state of execution (i.e. sleep, alive, dead, running), and dependencies among the various threads.
  • a thread scheduler on a single processor system distributes the processor's computing power among many threads to provide the illusion that the threads are actually running in parallel.
  • scheduling techniques including first-come-first-served, shortest-thread-first, priority scheduling, and preemptive scheduling techniques such as round-robin.
  • Hybrid scheduling techniques which combine these techniques can also be used as needed by the particular implementation.
  • schedulers associate different threads with different processors to execute threads in parallel and take advantage of the added computing power.
  • a method and apparatus for enabling a remote method to suspend processing and relinquish resources to the server system comprises receiving a request from a remote method call on a client system.
  • the remote method is allocated system resources from the server system and invoked.
  • One system level type of resource is a thread.
  • the method determines if any general resources required for processing the remote method are presently not available.
  • a general resource can be memory, disk storage space, data, or any resource that a system resource may depend on.
  • the remote method is suspended from further processing and system resources are relinquished to the server system when the remote method depends on a general resource which is not available.
  • Another method consistent with the present invention enables a previously suspended remote method to continue processing on the server system and generate a result for a client application.
  • This method comprises receiving an indication that a continuation event associated with a suspended remote method has occurred.
  • System resources and general resources are allocated to the remote method in preparation to continue processing the remote method.
  • the remote method utilizes the combined allocated resources to continue execution and generate results.
  • results are transmitted from the server system to the client application on the client system using a remote procedure call (RPC) system such as remote method invocation (RMI).
  • RPC remote procedure call
  • RMI remote method invocation
  • FIG. 1. illustrates a network suitable for use with methods and systems consistent with the present invention
  • FIG. 2 is block diagram of a computer system suitable for use with methods and systems consistent with the present invention
  • FIG. 3 is a block diagram of a client-server networking environment suitable for use with methods and systems consistent with the present invention
  • FIG. 4 is a block diagram of the subsystems used to suspend and continue processing of remote method calls consistent with methods and systems of the present invention
  • FIG. 5 is a flow chart of the steps performed to suspend and continue a remote method call consistent with methods and systems of the present invention
  • FIG. 6 is a flow chart of the steps performed to suspend a remote method call consistent with methods and systems of the present invention.
  • FIG. 7 is a flow chart of the steps performed to continue a remote method call consistent with methods and systems of the present invention.
  • a system designed consistent with the present invention assumes that a computer system can host either client or server functions.
  • the roles each computer assumes in a client-server system depends on the specific call being made between the client and the server. For example, a client process typically requests a service generated by a server process located on a remote machine. Conversely, a server process is located on a machine which receives and services a 8 clients requests. Therefore, the same computer system can act as a client when requesting a service and a server when fulfilling a request for a service.
  • RPC remote procedure call
  • systems consistent with the present invention are also advantageous in that they are compatible with clients on existing client-server systems. This is especially important in heterogeneous networked computing environments such as the Internet. Because the server is modified to allocate and deallocate resources more efficiently, the present invention does not
  • the exemplary distributed system (1) allows users of the system to share services and resources over a network of many devices; (2) provides programmers with tools and
  • the exemplary distributed system utilizes the JavaTM programming environment to allow both code and data to be moved from device to device in a seamless manner. Accordingly, the exemplary distributed system is layered on top of the Java programming environment and exploits the 9 characteristics of this environment, including the security offered by it and the strong typing provided by it.
  • the Java programming environment is more clearly described in Jaworski, Java 1.1 Developer's Guide. Sams.net (1997), which is incorporated herein by reference.
  • the exemplary distributed system provides the simplicity of access and the power of sharing that can be provided by a single system without giving up the flexibility and personalized response of a personal computer or workstation.
  • the exemplary distributed system may contain thousands of devices operated by users who are geographically disperse, but who agree on basic notions of trust, administration, and policy.
  • a "service” refers to a resource, data, or functionality that can be accessed by a user, program, device, or another service and that can be computational, storage related, communication related, or related to providing access to another user.
  • Examples of services provided as part of a Djinn include devices, such as printers, displays, and disks; software, such as applications or utilities; information, such as databases and files; and users of the system.
  • Both users and devices may join a Djinn.
  • the user or device When joining a Djinn, the user or device adds zero or more services to the Djinn and may access, subject to security constraints, any one of the services it contains.
  • devices and users federate into a Djinn to share access to its services.
  • the services of the Djinn appear programmatically as objects of the Java programming environment, which may include other objects, software components written in different programming languages, or hardware devices.
  • a service has an interface defining the operations that can be requested of that service, and the type of the service determines the interfaces that make up that service.
  • Fig. 1 depicts the exemplary distributed system 100 containing a computer 102, a computer 104, and a device 106 interconnected by a network 108.
  • the device 106 may be any of a number of devices, such as a printer, fax machine, storage device, computer, or other devices.
  • the network 108 may be a local area network, wide area network, or the Internet. Although only two computers and one device are depicted as comprising the exemplary 10 distributed system 100, one skilled in the art will appreciate that the exemplary distributed system 100 may include additional computers or devices.
  • Fig. 2 depicts the computer 102 in greater detail to show a number of the software components of the exemplary distributed system 100.
  • Computer 102 includes a memory 202, a secondary storage device 204, a central processing unit (CPU) 206, an input device 208, and 5a video display 210.
  • the memory 202 includes a lookup service 212, a discovery server 214, and a JavaTM runtime system 216.
  • the Java runtime system 216 includes the JavaTM remote method invocation system (R-MI) 218 and a JavaTM virtual machine 220.
  • the secondary storage device 204 includes a JavaTM space 222.
  • the Java runtime system 216 includes the JavaTM API, allowing programs running on top of the Java runtime system to access, in a platform-independent manner, various system functions, including 5windowing capabilities and networking capabilities of the host operating system. Since the Java API provides a single common API across all operating systems to which the Java runtime system 216 is ported, the programs running on top of a Java runtime system run in a platform- independent manner, regardless of the operating system or hardware configuration of the host platform.
  • the Java runtime system 216 is provided as part of the JavaTM software development lOkit available from Sun Microsystems of Mountain View, CA.
  • the Java virtual machine 220 also facilitates platform independence.
  • the Java virtual machine 220 acts like an abstract computing machine, receiving instructions from programs in the form of byte codes and interpreting these byte codes by dynamically converting them into a form for execution, such as object code, and executing them.
  • RMI 218 facilitates remote method invocation by allowing objects executing on one computer or device to invoke methods of an object on another computer or device. Both RMI and the Java virtual machine are also provided as part of the Java software development kit.
  • the lookup service 212 defines the services that are available for a particular Djinn. That is, there may be more than one Djinn and, consequently, more than one lookup service within the exemplary distributed system 100.
  • the lookup service 212 contains one object for each service within the Djinn, and each object contains various methods that facilitate access to the 1 1 corresponding service.
  • the lookup service 212 and its access are described in greater detail in co-pending U.S. Patent Application No.09/044,826, entitled "Method and System for Facilitating Access to a Lookup Service," which has previously been incorporated by reference.
  • the discovery server 214 detects when a new device is added to the exemplary distributed system 100, during a process known as boot and join or discovery, and when such a new device is detected, the discovery server passes a reference to the lookup service 212 to the new device, so that the new device may register its services with the lookup service and become a member of the Djinn. After registration, the new device becomes a member of the Djinn, and as a result, it may access all the services contained in the lookup service 212.
  • the process of boot and join is described in greater detail in co-pending U.S. Patent Application No. 09/044,939, entitled "Apparatus and Method for providing Downloadable Code for Use in Communicating with a Device in a Distributed System," which has previously been incorporated by reference.
  • the Java space 222 is an object repository used by programs within the exemplary distributed system 100 to store objects. Programs use the Java space 222 to store objects persistently as well as to make them accessible to other devices within the exemplary distributed system. Java spaces are described in greater detail in co-pending U.S. Patent Application No. 08/971,529, entitled “Database System Employing Polymorphic Entry and Entry Matching,” assigned to a common assignee, filed on November 17, 1997, which is incorporated herein by reference. One skilled in the art will appreciate that the exemplary distributed system 100 may contain many lookup services, discovery servers, and Java spaces.
  • FIG. 3 depicts an exemplary client-server system consistent with the present invention and exemplary distributed system 100.
  • client-server system 300 consists of a client computer 302, also referred to as client 302, a server computer 312, also referred to as server 312, and a network 310 coupled between client 302 and server 312.
  • client-server system can be implemented using the JavaTM object oriented language and as an enhancement to RMI 218.
  • RPC remote procedure call
  • Client 302 includes a client application 304 having a remote method call 306, a remote stub 308, and a remote method runtime 309.
  • Client application 304 is typically software developed by a user and includes remote method call 306 for invoking a process on server 312.
  • client application 304 can be a JavaTM application written in the JavaTM programming language.
  • Remote method call 306 is implemented using an RPC mechanism such as RMI.
  • Remote method stub 308 marshals data and parameters provided by remote method call 306.
  • the data and parameters are arranged in a predetermined format that can be unmarshalled by a remote method skeleton 315 on server 312.
  • Remote method runtime 309 tracks the status of processes associated with remote method call 306 as they are processed on server 312.
  • Remote method runtime 309 also determines whether the communication link between client application 304 and server 312 is up or has been disconnected.
  • Remote method runtime 309 can query server 312 for the status of the link. If no response is made in a reasonable period of time or server 312 indicates the link is down, remote method runtime 309 notifies client application 304 that the remote method call has terminated.
  • Network 310 provides a communication link between client 302 and server 312.
  • Network 310 can be the Internet or a corporate or campus-wide intranet.
  • Network 310 can use TCP/IP or any other network protocols including Novell Netware, AppleTalk, X.25, or any other network capable of supporting an RPC system such as RMI.
  • Server 312 includes a corresponding remote method runtime 314 and remote method skeleton 315.
  • server 312 also includes a general resource manager 316, an event handler 317, a remote method resource manager 322, a remote event handler 323, and 13 numerous remote method resources 324.
  • Server 312 also includes a remote object A 318 and a remote object B 320. Each remote object is associated with a number of methods (not shown) which client application 304 can invoke using remote method call 306.
  • Alternative configurations of server 312 may include any number of remote objects for performing remote
  • Remote method runtime 314 is responsible for keeping client 302 informed of the remote method execution status. Remote method runtime 314 provides information to client 302 indicating that the remote method is processing data. Consistent with the present invention, the processing status is not interrupted even when a remote method is suspended. Instead, remote
  • 5method mntime 314 maintains the connection with client 302 until the remote method completes processing the requested task.
  • Remote method runtime 314 also indicates to client 302 when a remote method has terminated abnormally or in error.
  • the method determines if any general resources required for processing the remote method are presently not available.
  • a general resource can be memory, disk storage space, data, or any resource that a system resource may depend on.
  • Remote method skeleton 315 is responsible for unmarshalling data and parameters transmitted over network 310.
  • the parameters and data are used as arguments for executing a remote method on server 312.
  • General resource manager 316 and event handler 317 manage resources used by local processes and methods executed on server 312. Local methods executed on server 312 look to general resource manager 316 and event handler 317 to coordinate allocation and deallocation of general resources.
  • These general resources can include primary storage, such as memory, or
  • Event handler 317 detects events associated with local processes and, therefore, the details of event handler 317 are not included in this specification. Essentially, general resource manager 316 and event handler 317 are dedicated to managing resources associated with those processes and methods lOwhich are not being invoked remotely from a client such as client 302.
  • remote method resource manager 322 and remote event handler 323 are responsible for allocating and deallocating remote method resources 324 as needed by remote methods.
  • Remote method resources 324 can be considered a system resource since they enable 14 a method to utilize a system level resource such as networking. Often, the system resources will have dependencies on the general resources mentioned above.
  • Remote method resource manager 322 transfers remote method resources 324 between remote methods associated with remote object 318, remote object 320, and other objects (not shown).
  • Remote event handler 323 detects when resources are released that a remote method needs to process a particular task. Transferring these remote method resources is facilitated
  • a suspend method is invoked when a remote method is about to block. This typically occurs just before a remote method is blocked waiting for a resource to become available.
  • the suspend method marks the remote method as suspended and a remote method resource manager returns threads and other resources back to the server system. When the resources become
  • a remote method resource manager and a continue method work together to allocate the threads and other remote method resources to the suspended remote method.
  • a remote method runtime invokes the suspended remote method so that it may continue processing.
  • a remote method waiting for a write operation enters a ready to block state and relinquishes threads and other resources by invoking a suspend operation.
  • the suspend operation lOmarks the remote method as suspended and the remote method resource manager returns the threads to a thread pool associated with the server system.
  • a continue method marks the suspended remote method as runnable and the remote method resource manager allocates threads and to other resources back to the suspended remote process.
  • a remote method runtime invokes the previously suspended remote method which enables the
  • Figure 4 is a block diagram illustrating the essential software subsystems used to suspend and continue processing a remote method. These software subsystems include remote method resources 324, remote method resource manager 322, and exemplary remote object A 318 having remote method 416 and execution state 418.
  • Remote method resources 324 in Fig. 4 includes a thread pool 402 having threads in-use 404, available threads 406, and an RPC state 408. Threads in-use 404 contains references to threads currently being used by remote methods while available threads 406 contains threads 15 currently available for use by remote methods.
  • RPC state 408 is kept in remote method resources 324 to store information used by an RPC system, such as RMI, when a remote method is suspended. This information can include information the RPC system to continue processing a suspended remote method and return results to the client.
  • remote method resources 324 could also include other resources other than threads. These other network resources could include primary storage, secondary storage and any other resource used in conjunction with processing remote methods.
  • Remote method resource manager 322 includes a suspend method 410, a continuation method 412, and a state store 414.
  • Suspend method 410 obtains an execution state 418 from remote method 416 and a RPC state 408 from remote method resources 324. This state information is stored in state store 414 before remote method 416 is suspended.
  • suspend method 410 marks a remote method 416 as suspended when remote method 416 indicates that it is about to be blocked and that it has threads and other resources.
  • remote method resource manager 322 returns the threads and other resources to server 312 and remote method 416 is suspended from further processing. For example, assume remote method 416 is attempting to read data from a queue which is temporarily empty. When remote method 416 detects the queue is empty, remote method 416 will invoke suspend method 410 to initiate the suspension process.
  • Continue method 412 is the companion to suspend method 410.
  • Continue method 412 is typically invoked when a resource is available or a particular event has occurred. For example, writing data to a particular queue can trigger a continuation event which can invoke continue method 412.
  • Continue method 412 locates the suspended remote method waiting on the resource and marks it as runnable.
  • remote method resource manager 322 allocates threads and other resources to the previously suspended remote method. Execution state 418 and RPC state 408 stored in state store 414 are used to ensure that remote method 416 continues processing at the appropriate point prior to being suspended.
  • FIG. 5 is a flow chart indicating the steps performed to suspend and continue a remote call in consistent with methods and systems of the present invention.
  • the server 312 receives a request from remote method call 306 on client 302 to process remote method 416. Accordingly, remote method skeleton 315 unmarshalls the data and parameters transmitted in the request (step 506). After the data and parameters are decoded by remote method skeleton 315 they are passed to remote method 416.
  • Remote method runtime 314 on server 312 indicates to remote method runtime 309 on client 302 that server 312 has received the request to invoke remote method 416 and is processing the request (step 507).
  • Client application 304 continues to receive an indication that server 312 is processing the request even if remote method 416 is suspended and threads and other resources are relinquished.
  • Remote method resource manager 322 allocates the threads and other resources to remote method 416 which is about to be invoked (step 508). Threads allocated to remote method 416 are taken from available threads 406 in thread pool 402. Multiple threads can be used to process several remote methods or tasks in parallel. Assuming the threads and other resources are available, remote method mntime 314 invokes remote method 416 on behalf of client application 304 (step 510). If the remote method resource manager cannot allocate a thread or other resources to remote method 416, it is put on an execution queue pending release of a thread or other resources from another process.
  • Remote method 416 includes instructions for determining if a suspend condition exists (step 512). These instructions also include information to determine when a continuation condition exists.
  • a suspend condition occurs when remote method 416 depends on a resource which is not available or an event which has not yet occurred. In contrast, the continuation event occurs when the resource is available or the event occurs.
  • remote method 416 is sampling data points and pauses a long time interval between each sampling. During this long pause, remote method 416 may block waiting for a timer event to indicate the end of the next time interval.
  • remote method 416 relinquishes resources and registers continuation instructions with a remote event handler 323 to monitor certain resources and events (step 516).
  • remote method 416 is suspended from further processing and awaits the particular continuation event in order to continue processing (step 518).
  • a continuation event is an event generated 17 when a resource becomes available or an event occurs that a suspended remote method depends on for further processing.
  • Remote event handler 323 processes the continuation instructions registered by suspended remote method 416. The remote method completes the task and returns the results back to client application 304 (step 514). It should be understood that a remote method can be suspended and continued many times before completing a task and returning results to the client.
  • FIG. 6 is a flow chart of the steps performed to suspend a remote call consistent with methods and systems of the present invention.
  • remote method 416 detects that a suspend event has occurred and elects to relinquish threads and other resources (step 602).
  • Remote method is marked as being suspended by suspend method 410.
  • remote method 416 provides remote method resource manager 322 with execution state 418, RPC state 408, and relinquishes the threads and other resources (step 604).
  • Remote method resource manager 322 places these threads back into available threads 406.
  • remote method 416 can choose to suspend processing without relinquishing any threads or resources.
  • Execution state 418 records state information related to remote method 418 at the time it is suspended including local variables, program counter, and any other information related to remote method 416.
  • RPC state 408 records state information associated with the RPC system, such as RMI, when remote method 416 is suspended.
  • RPC state 408 enables the RPC system to communicate with a client and return results when remote method 416 continues execution.
  • remote method resource manager 322 stores RPC state 408 and execution state 418 (step 608).
  • Remote method resource manager 322 stores this state information to continue processing a suspended remote method at some time in the future.
  • Remote method 416 also registers continuation instmctions with remote event handler 323 which monitors certain resources and events. Generally, the continuation instmctions are used for preprocessing data and contacting the appropriate suspended process.
  • remote method 416 is blocked from further processing and waits for a continuation event to occur ( step 610). 18
  • FIG. 7 is a flow chart of the steps performed to continue a previously suspended remote method, such as remote method 41 with methods and systems consistent with the present invention. Typically, each step of this process occurs asynchronously as the particular conditions are met.
  • remote event handler 323 receives an indication that a particular continuation event has occurred.
  • Remote event handler 323 associates the continuation event with a particular remote method (step 702) and invokes the corresponding continuation instructions.
  • the continuation event is an event generated when a resource becomes available or an event occurs which the suspended remote method depends on for further processing. For example, a continuation event can occur when information is written to a queue that a suspended remote method was waiting to read.
  • Step 704 is typically an asynchronous process that occurs when remote method resource manager checks for status on the suspended process and not necessarily when status of the remote process is changed to runnable.
  • Remote method resource manager 322 allocates the resources, such as threads, to remote method 416 (step 706).
  • Remote method mntime 314 loads execution state 418 and RPC state 408 from state store 414.
  • Execution state 418 prepares remote method 416 to continue processing at the point it left off prior to being suspended (step 708).
  • remote method 416 may be several pieces of interrelated code which each start where the previous code section stopped prior to being suspended.
  • remote method 416 can be implemented as a single code segment with execution starting at different points in the code segment.
  • RPC state 408 enables the RPC system, such as RMI 218, to continue processing and return results to the proper remote method call 306.
  • Remote method mntime 314 enables remote method 416 to continue execution.
  • Remote method 416 then continues processing on the server using the assigned threads and other resources (step 710).
  • results are generated by remote method 416 and are provided to remote method skeleton 315 for encoding and packaging (step 712).
  • These encoded results 19 are passed over network 310 to remote method stub 308 where they are decoded and provided to remote method call 306 (step 714).

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multi Processors (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

On décrit un procédé et un appareil permettant à des procédés éloignés bloqués de renoncer à des chemins et à d'autres ressources destinées à d'autres procédés sur un système de serveur. Dans un environnement de calcul réparti, plusieurs ressources de réseau sont attribuées à des procédés éloignés mais sont bloquées pendant le moment où ils attendent la fin d'une opération, telle qu'un opération d'écriture provenant d'un autre processus. Lorsque suffisamment de procédés éloignés sont bloqués, les chemins et les autres ressources de réseau peuvent s'épuiser. Les systèmes de clients demandant des services de serveur peuvent connaître des temps de réponse plus lents. Ce procédé et ce système utilisent une technique qui permet à des procédés éloignés de renoncer à des ressources de réseau telles que des chemins, pour que d'autres procédés les utilisent alors que les procédés sont bloqués. Lorsque les conditions provoquant le blocage des procédés éloignés sont résolues, les procédés éloignés poursuivent l'exécution. Cette technique permet à des systèmes de transaction client-serveur à grand débit d'utiliser plus efficacement des chemins et d'autres ressources dans un environnement de calcul réparti.
EP99936131A 1998-02-26 1999-02-18 Procede et appareil utilises pour la suspension et la poursuite de processus eloignes Withdrawn EP1057108A1 (fr)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US7604898P 1998-02-26 1998-02-26
US76048P 1998-02-26
US44917 1998-03-20
US09/044,917 US6237024B1 (en) 1998-03-20 1998-03-20 Method and apparatus for the suspension and continuation of remote processes
PCT/US1999/003520 WO1999044131A1 (fr) 1998-02-26 1999-02-18 Procede et appareil utilises pour la suspension et la poursuite de processus eloignes

Publications (1)

Publication Number Publication Date
EP1057108A1 true EP1057108A1 (fr) 2000-12-06

Family

ID=26722150

Family Applications (1)

Application Number Title Priority Date Filing Date
EP99936131A Withdrawn EP1057108A1 (fr) 1998-02-26 1999-02-18 Procede et appareil utilises pour la suspension et la poursuite de processus eloignes

Country Status (6)

Country Link
EP (1) EP1057108A1 (fr)
JP (1) JP2002505471A (fr)
KR (1) KR20010041297A (fr)
CN (1) CN1298502A (fr)
AU (1) AU3300499A (fr)
WO (1) WO1999044131A1 (fr)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1128266A3 (fr) * 2000-02-22 2004-02-25 Orsus Solutions Limited Architecture d'application logiciel coopérative
US7076551B2 (en) 2000-04-03 2006-07-11 Texas Instruments Incorporated Using remote procedure calls to manage co-processor resources
US7493391B2 (en) * 2001-02-12 2009-02-17 International Business Machines Corporation System for automated session resource clean-up by determining whether server resources have been held by client longer than preset thresholds
EP1249758B1 (fr) 2001-04-11 2012-03-07 Texas Instruments Incorporated Appels de procédures à distance pour gérer des ressources d'un coprocesseur
US7168612B2 (en) * 2001-12-24 2007-01-30 Axalto Inc Method and apparatus for processing transactions in a data processing system
US20030182426A1 (en) * 2002-03-21 2003-09-25 Sun Microsystems, Inc. Apparatus and method of lazy connection transaction enlistment
US7496494B2 (en) 2002-09-17 2009-02-24 International Business Machines Corporation Method and system for multiprocessor emulation on a multiprocessor host system
US9043194B2 (en) 2002-09-17 2015-05-26 International Business Machines Corporation Method and system for efficient emulation of multiprocessor memory consistency
US7953588B2 (en) 2002-09-17 2011-05-31 International Business Machines Corporation Method and system for efficient emulation of multiprocessor address translation on a multiprocessor host
US8108843B2 (en) 2002-09-17 2012-01-31 International Business Machines Corporation Hybrid mechanism for more efficient emulation and method therefor
CN1306403C (zh) * 2003-12-30 2007-03-21 北京金山数字娱乐科技有限公司 一种用于游戏的网络服务器系统
JP2007108804A (ja) * 2004-01-27 2007-04-26 Matsushita Electric Ind Co Ltd アプリケーション起動調停システム
US9323571B2 (en) * 2004-02-06 2016-04-26 Intel Corporation Methods for reducing energy consumption of buffered applications using simultaneous multi-threading processor
US20050179936A1 (en) * 2004-02-13 2005-08-18 Microsoft Corporation Scalable print spooler
JP4208783B2 (ja) * 2004-07-28 2009-01-14 キヤノン株式会社 画像処理装置および設定時刻調整方法およびプログラム
JP4126702B2 (ja) * 2004-12-01 2008-07-30 インターナショナル・ビジネス・マシーンズ・コーポレーション 制御装置、情報処理システム、制御方法、及びプログラム
US20070174655A1 (en) * 2006-01-18 2007-07-26 Brown Kyle G System and method of implementing automatic resource outage handling
CN101414340B (zh) * 2007-10-15 2015-12-02 北京瑞星信息技术有限公司 一种防止远程线程启动的方法
WO2012008016A1 (fr) * 2010-07-13 2012-01-19 富士通株式会社 Dispositif, système, programme et procédé de traitement de chemins multiples
US8473957B2 (en) * 2010-12-13 2013-06-25 Microsoft Corporation Architecture for providing on-demand and background processing
KR101357975B1 (ko) * 2011-10-17 2014-02-03 엔에이치엔엔터테인먼트 주식회사 코루틴을 이용하여 원격 프로시저 호출 서비스를 제공하는 방법 및 장치
US20150341445A1 (en) * 2014-05-23 2015-11-26 Radoslav Nikolov Hybrid applications operating between on-premise and cloud platforms
CN107092532B (zh) * 2017-03-22 2020-08-04 武汉斗鱼网络科技有限公司 一种远程调用方法及远程调用装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ATE116456T1 (de) * 1990-10-19 1995-01-15 Cray Research Inc Skalierbares parallel-vektorrechnersystem.
US5553305A (en) * 1992-04-14 1996-09-03 International Business Machines Corporation System for synchronizing execution by a processing element of threads within a process using a state indicator
GB9414951D0 (en) * 1994-07-25 1994-09-14 British Telecomm Computer system having client-server architecture
JPH0962526A (ja) * 1995-08-28 1997-03-07 Fujitsu Ltd 耐故障型ｒｐｃシステムおよび方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO9944131A1 *

Also Published As

Publication number Publication date
AU3300499A (en) 1999-09-15
JP2002505471A (ja) 2002-02-19
CN1298502A (zh) 2001-06-06
WO1999044131A1 (fr) 1999-09-02
KR20010041297A (ko) 2001-05-15

Similar Documents

Publication Publication Date Title
US6237024B1 (en) Method and apparatus for the suspension and continuation of remote processes
WO1999044131A1 (fr) Procede et appareil utilises pour la suspension et la poursuite de processus eloignes
US5452459A (en) Method and apparatus for allocating server access in a distributed computing environment
US7246167B2 (en) Communication multiplexor using listener process to detect newly active client connections and passes to dispatcher processes for handling the connections
US20010010053A1 (en) Service framework for a distributed object network system
CA2191824C (fr) Methode et dispositif pour le verrouillage d'objet qui soit spatialement efficace
US7130905B2 (en) System and method for coordinating access to data for a distributed application
EP1442372B1 (fr) Isolement au moyen de machines virtuelles rattachables a un processus
KR100898315B1 (ko) 인핸스드 런타임 호스팅
Neuman et al. The Prospero resource manager: A scalable framework for processor allocation in distributed systems
JP4690437B2 (ja) ネットワークアプリケーションにおける通信方法、通信装置及びそのためのプログラム
KR20060041928A (ko) 프린트 시스템 및 방법
EP0695993A2 (fr) Système et méthode pour la communication entre des processus
EP0704796B1 (fr) Méthode et appareil à dispositif de capacité pour un système de traitement de données à micro-noyaux
Wang et al. Lsbatch: A Distributed Load Sharing Atch System
US20080065838A1 (en) Data processing system with memory access
US6507861B1 (en) System and method for avoiding deadlock in a non-preemptive multi-threaded application running in a non-preemptive multi-tasking environment
Neuman et al. Resource management for distributed parallel systems
EP0689139A2 (fr) Méthode et appareil à port de réponse anonyme pour un système de traitement de données à micro-noyaux
EP0689137A2 (fr) Méthode et appareil d'enregistrement de structure de contrÔle de message pour un système de traitement de données à micro-noyaux
KR20010040971A (ko) 분산 시스템에서 오브젝트의 지연된 재구성 및 이벤트통지를 위한 원격 로딩
Froidevaux et al. The mainframe as a high-available, highly scalable CORBA platform
Janson et al. CORBA vs. DCOM
Owego Realtime CORBA
Pava Design Specification for the Real Time Platform Middleware

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20000908

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE FR GB IE NL SE

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20030902