DISTRIBUTED MONITOR CONCURRENCY CONTROL

Abstract: A system and method is disclosed for synchronizing threads of execution within a distributed computing environment. Threads of execution within a computer spawn additional threads of execution on separate computers within the distributed computing environment. Each thread may compete for shared resources within the computing environment, thereby creating a need to avoid deadlocks among the local threads. Whereas locals thread exists within a single computing platform, logical threads are created to relate local threads to each other and thereby span the platforms on which the local threads reside. Distributed monitors are created to control access to shared resources by local threads based on logical thread affiliations. Locks within the distributed monitors are assigned to logical threads instead of local threads. Local threads that are each part of the same logical thread will all have access to the shared resource when the lock is assigned to the logical thread.

Description: TITLE: DISTRIBUTED MONITOR CONCURRENCY CONTROL Background of the Invention 1. Field of the Invention The present invention relates to computer hardware and software, and more particularly to a system for thread synchronization in a distributed computing environment wherein multiple threads of execution span across different computing platforms. 2. Descπption of the Pπor Art The logical progression of executed steps in a microprocessor is called a "thread" of execution. Simple computer systems have a smgle microprocessor and an operatmg system that allows only one active thread of execution. Thus, software will execute in a serial fashion, with each operation running sequentially after the termmation of the previous operation. This type of operatmg system becomes mefficient when system resources halt to allow a long calculation to finish executing For example, suppose that certain calculations were being performed on batches of data that were mput by a data entry operator. In a system with a single thread of execution, the data entry operator would have to pause while each calculation was finished on the previous batch of data. It would be more efficient if the data entry operator could contmuously input the data while calculations on the previous batch of data were executing in the background. Such a system would require multiple threads of execution: a first thread to process the mput from the operator, and a second thread to perform the calculations on the previous batch of data. In the example above, a multithreading scheme would be fairly simple to devise because it is unlikely that the first and second threads would interfere with each other. Each thread would execute on its own stack mdependently of the other. This is often called "unsynchronized" multithreading. In a computer with a single microprocessor, unsynchronized multithreading may be accomplished by time-multiplexing the microprocessor. This means that the -microprocessor, or CPU, divides its time between two or more stacks such that all stacks make some progress over time, without havmg the stacks explicitly call each other. The first stack would wait while execution proceeded on the second stack, and vice versa. As used herein, the term "concurre threads" means that two or more threads are in various stages of execution concurrently. Concurrent threads may be executmg one at a time in a time multiplexmg scheme. Alternatively, a computer with parallel processors may have concurrent threads executing simultaneously. There are a number of known techniques for time-multiplexing, including "preemptive" and "non-preemptive" multitasking. In a preemptive multitasking scheme, the operatmg system allocates time among the threads. In a non-preemptive scheme, the active thread controls the time at which it relinquishes execution. In general, there is no assurance that multiple threads of execution can run concurrently without interfering with each other. For example, two threads of execution may access the same location in memory to store intermediate results. In this scenario, the first thread may store a value to memory, followed by the second thread over-writing a different value to the same location in memory. Thus, when the first thread retrieves the value it will corrupt the calculation in unpredictable ways. Resources that may be shared among concurrent threads, such as memory, must be protected in a manner that prevents corrupnon between the threads The process of assuring that concurrent threads do not interfere with each other is called "thread synchronization " Modem operatmg systems that allow multitasking operations have vanous tools to accomplish thread synchronization Some examples include locks, monitors, and request servers Locks are relatively simple programming constructs that protect shared resources A lock must be "acquired" by a thread of execution before that thread can access the shared resource Pπor to gaining control of the shared resource, the thread must show evidence that it has acquired the lock, or alternatively, the entire system must respect a convention which threads without locks refram from accessmg the shared resource In a simple system, the shared resource may only allow one lock to issue at any time, thus preventing any concurrent access to the resource Locks can be difficult to use in a layered or nested architecture because the lock evidence must be explicitly supplied to allow access to the shared resource This presents a problem when a first thread acquires a lock, then waits for results from a second thread which also needs access to the same resource This scenario can lead to a "deadlock" in which the first and second threads are each waitmg for the other, as descnbed in the following example Suppose a method or procedure called "foo( )" acquires a lock on resource "R " Subsequently, "foo( )" calls "goo( )" which also tries to acquire a lock on the resource R The attempt by "goo( )" to acquire the lock will fail even though "goo( )" is operatmg on behalf of 'foo( ) " Thus,even when method "foo( )" has a lock, it can deadlock a system by calling a second method "goo( )" if both methods need the same resource R A higher level concept, called a "monitor," provides a solution to this type of nestmg problem Local "monitors" are a well known technique for thread synchronization They are fairly easy to use and map well to object-onented systems In certain respects, a local monitor can be viewed as a programming construct in which a lock is assigned to a thread In contrast, a simple lock (as descnbed m the example above) is typically assigned to a shared resource The local monitor is associated with the thread's section of code in which shared access is performed Each local monitor comprises a queue and a lock As a thread proceeds mto a monitor, the thread will either be assigned a spot on the queue, or will be granted access to the resource while other threads wait on the queue In this manner, a lock does not have to be passed from thread to thread Another technique for thread synchronization mvolves a "request server " A separate computing platform constitutes the request server, and clients to this server are the mdividual threads of execution The server creates mdividual (local) threads of execution to handle each request from a client Thus, the problems associated with distributed system concurrency control are reduced to a local problem of concurrency control where well known techniques can be applied One of the drawbacks of this approach is the large overhead required to generate a new thread for each client request Several U S Patents are directed to the problem of thread synchronization For example, U S Patent 5,341,491 discloses an apparatus and method for ensunng that lock requests are serviced in a multiprocessor system According to the disclosure, a lock queue includes a plurality of registers pipelined together, wherein lock requests only enter the lock queue if they are refused access to a shared resource a predetermined number of times U S Patents 5,636,376 and 5,675,798 disclose a system and method for selectively and contemporaneously monitormg processes in a multiprocessing server A status utility selectively accesses information to determine the status of the mdividual multiple processes executmg on the server workstation. The information is of a granulanty to identify processes which are hung up on semaphores, message queues, or the like. U.S Patent 5,590,335 discloses a process for analysis of deadlocks in an operatmg system. The process includes the step of searchmg for any thread stopped on a lock, and further for the thread that holds that lock, and further up the cham until a cycle is found. In this manner, the user can reconstruct the cycle determining the deadlock U S. Patent 5,590,326 discloses a shared data management scheme usmg shared data locks for multi-threading. In this scheme, different shared data identifiers are assigned to different threads, and different locks are set up for different shared data identifiers, so as to enable the detection of an access in violation to the locks U.S. Patent 5,524,247 discloses a system for schedulmg programming units to a resource based on status vanables mdicatmg a lock or lock-wait state. The central processmg unit (CPU) sets a predetermined value in the status vanable corresponding to a thread when the thread starts waitmg for a resource which it shares with other threads. The scheduler refers to the status vanable, selects, with pnonty, a thread other than the thread waitmg for the shared resource, and allocates the CPU to the thread thus selected U S. Patent 5,706,515 discloses a system for implementing an atomic wait for notification operations. A resource allocation subsystem mcludes an "initialization" procedure for initializing monitors, a "notify" procedure and a "wait" procedure Each monitor has an associated event data structure denoting the status of the monitor as Signaled or Unsignaled. Each monitor also stores a value mdicatmg how many threads are waiting on the monitor. U.S. Patent 5,247,675 discloses preemptive and non-preemptive schedulmg and execution of program threads m a multitaskmg operatmg system. The operatmg system permits application programs to influence the schedule of execution of program threads. A pnonty level is assigned to each thread, and the highest pnonty thread is executed first. U.S. Patent 5,481,706 discloses a system and method for creatmg thread-safe shared branes The system insures correct functioning and integnty of the library functions accessible by multiple threads. A wnte-exclusive lock is used to protect shared resources. Computer networks can allow different computing platforms to exchange data and to share network resources and peripheral devices In simple computer networks, software will only execute within a smgle platform, although data may be accessed from vanous resources within the network. The issues surrounding thread synchronization typically remain local to each computmg platform. More recent developments in computer networking have enabled the execution of threads to progress across several different computing platforms A "thread jump" occurs when a thread is executmg on a first computmg platform, and subsequently contmues its execution on a second computing platform within the network Networks of computmg platforms that allow thread jumps are herein referred to a "distnbuted systems " The problem of thread synchronization presents itself anew with distnbuted systems. The advent of thread jumps typically requires a method of thread synchronization that applies throughout the network. Pnor synchronization systems are not normally applicable because they apply withm the confines of a smgle computmg platform What has been desired, and is addressed by the present invention is a system and method for thread synchronization that applies to distnbuted systems Summary of the Invention The present invention extends the applicability of monitors to distnbuted systems. An important element of the present mvention is the "logical thread" which is compnsed of one or more "local threads " While a local thread exists within a smgle computmg platform, a logical thread may span several local threads, and thereby span the platforms on which the local threads reside. For example, m an object-oriented system, if an object on machme A makes a method call on an object on machme B, local threads on each machme (the calling thread and the called thread) belong to the same logical thread of execution. Thus, accordmg to the present mvention, monitors may be adapted to work with logical threads A mapping exists within each computmg platform which maps local threads to logical threads. The mapping may be in the form of a hash table, or any other programmmg construct which associates local threads with logical threads. As new local threads are spawned by calls from other parts of the network, the new local threads are assigned to logical threads by the mapping construct Monitors within each platform are designed to function with logical threads instead of local threads When a local thread enters a monitor, access to the shared resource is determined on the basis of the logical thread to which the local thread is affiliated Thus, if the calling thread on a first machme has already gamed access to a monitor, the called thread on a second machine will not be precluded from accessmg the same resource Brief Description of the Drawings A more complete understanding of the present mvention can be obtamed by considering the following detailed descnption of the preferred embodiments thereof in conjunction with the accompanymg drawmgs, in which: Figure 1 is a logic diagram representation of two local threads on different computers that belong to the same logical thread. Figure 2 is a logic diagram representation of local threads and logical threads accordmg to the present mvention, wherein logical thread 1 is compnsed of several local threads. Figure 3 is a logic diagram representation of a monitor. Detailed Description of the Invention Referring to Figure 1, Block 1 10 is representative of a first computer (Machme A) within a distnbuted network. Block 112 is representative of a second computer (Machme B) which is also connected within the same distnbuted network as Block 110. Below each respective block is a bar representative of a local thread of execution within its respective machme. Thus, bar 114 is a local thread of execution with machme 110, and bar 116 is a local thread of execution withm machine 112 Each of the local threads of execution, 114 and 116, are shown schematically as proceedmg stepwise from top to bottom m Figure 1. Thus, local thread 114 proceeds m its stepwise execution starting from the top of bar 114, until it reaches lme 118 Line 118 represents a local call from thread 114 that spawns another local thread withm Machme A The arrow-head on lme 118 represents a "return" of local thread 118, at which pomt local thread 118 is terminated Traditional thread synchronization schemes can be applied as long as local threads are spawned and returned withm the same platform (Machine A) A more complex scenario unfolds when local thread 114 is allowed to make a remote call to a second machme (Machme B) as shown by lme 120 This type of remote call is a feature of new distnbuted computmg environments. The remote call 120 spawns a new local thread on Machme B shown by bar 116 As between local threads 114 and 116, synchronization becomes problematic under pnor technology if thread 116 tne When thread 114 acquires a lock on a shared resource, the lock is held by the logical thread S ce local thread 116 is associated with the same logical thread, local thread 1 16 will be able to gam access to the shared resource and thereby avoid a deadlock. The mechanism for associatmg the lock with the logical thread is described below m connection with "monitors " Local thread 116 can make local calls that spawn new threads withm Machme B. as shown by lme 122 Additionally, local thread 116 can make remote calls to other machmes that are connected to the distnbuted computmg environment, which will spawn new local threads withm those machmes. In each case, every new thread spawned from the oπgmal logical thread will become part of the same logical thread. Logical threads can thereby extend over an arbitrary number of platforms withm a distnbuted computmg environment Local threads, which are threads of execution withm a single computing platform, are tied together to form logical threads. Remote method calls, from one computmg platform to another, are one way m which more than one local thread can become tied together to form a logical thread In some systems, event queumg and delivery could also tie multiple local threads to a smgle logical thread "Thread jumps" result m tying local threads together to form logical threads Accordmg to the present invention, the series of local threads shown in Figure 1 constitute a smgle logical thread. As logical thread is holdmg a lock on a monitor. If any one of the local threads ceases to exist, it is essential that the monitor lock be released in a timely manner to avoid lockmg out other access requests to the shared resource which the monitor controls. This problem is addressed, accordmg to the present mvention, with "reference counting" or "keep alive" mechanisms similar to "lease" type distnbuted garbage collectors. A logical thread may be created, and stopped, accordmg to the examples in the following code. The comments precedmg the code descnbe the function of certain program elements. It will be understood by skilled programmers that vanous equivalent implementations exist, mclud g different logical constructions of programmmg objects which, m aggregate, will perform the same function The sample code is wntten for a JAVA Virtual Machme (JVM) /** Start a logical thread If the current local thread does not yet have * a logical thread, startLogιcalThread( ) creates one and makes the * association Calls to startLogιcalThread( ) MUST be balanced by calls * to stopLogιcalThread( ) Generally this is accomplished with try/finally * blocks */ public static LogicalThread startLogιcalThread( ) synchromzed( mappmg I LogicalThread thread = getLogιcalThread( ), If ( thread = null) SetLogicalThread( thread = new LogicalThread( ) ); else thread.count++; return thread; } } /** Stop a logical thread. Calls to startLogicalThread( ) MUST be balanced by calls * to stopLogicalThread( ). Generally this is accomplished with try/finally * blocks. When the last stopLogicalThread( ) is called (nesting depth is zero), * the logical thread thread/local thread association is removed and the logical thread * effectively no longer exists. */ public static void stopLogicalThread( ); { synchronized( mapping ) { LogicalThread thread = getLogicalThread( ); if ( thread = null || thread.count = 0 ) mapping.remove( Thread.currentThread( ) ); else thread.count—; } } Referring now to Figure 2, two computers are shown as machine 1 (200) and machine 2 (202), which are connected in a distributed computing environment. Dashed line 208 in Figure 2 represents a logical separation between computing platforms 200 and 202, which are still connected through a network. Local threads on each machine are shown as tl, t2, and t3, which comprise a single logical thread LTI. A table within each machine is updated at each thread jump to maintain current affiliations of local threads with logical threads. A local thread, tl, is shown executing steps associated with function 1 in machine 1. Function 1 makes a call, "enter(x)" which is representative of a call to a monitor. Local thread tl thus acquires a lock on a monitor. A thread jump occurs during execution of function 2, spawning a new local thread t2 within machine 2. A table within machine 1 (204) records the affiliation of local thread tl with logical thread LTI . Similarly, a table within machine 2 (206) records the affiliation of local thread t2 with the same logical thread LTI. After a call to function 3, local thread t2 jumps back to machme 1 , thus spawning a new local thread t3 on machine 1. The table within machine 1 (204) is updated accordingly to reflect that t3 belongs to LTI. With each local thread, there is preferably associated a "thread context." The thread context is an identification assigned to local threads which is guaranteed to be unique among logical threads across all elements of the distnbuted system. When a thread jump occurs, the new local thread is given a thread context with the same identification as the thread from which the jump is bemg made. When a lock is acquured, the lock is tagged with that unique identification, thus ensurmg the shared resource is locked for all the constituent local threads of the logical thread. Whereas monitors typically operate with local threads, m a distnbuted momtor the lockmg function is associated with a logical thread. A distnbuted monitor preferable allows only a smgle logical thread to hold the lock at any one time. The logical thread that holds the lock can be identified through an Object Identifier (OID), which is one embodiment of the unique thread context. A mappmg withm each platform, for example tables 204 and 206, associate an OID with a distnbuted monitor. The mappmg is preferably updated whenever the association changes. The following sample code illustrates one way of mappmg local threads to logical threads. The comments precedmg the code descnbe the function of certain program elements. It will be understood by skilled programmers that vanous equivalent implementations exist, including different logical constructions of programmmg objects which, m aggregate, will perform the same function. The sample code is wntten for a JVM // Mapping of local/physical threads to LogicalThreads in this JVM pnvate static Hashtable mappmg = new Hashtable ( ), /** Get the logical thread for the cunent local thread. * If a logical thread does not exist, getLogicalThread ( ) * returns null. You start a logical thread by calling * LogιcalThread.startLogιcalThread( ) directly or implicitly * by calling LogιcalThread.momtorEnter( ) or LogιcalThreadmomtorLock( ). * A local thread may also be associated with a logical thread * by calling LogιcalThread.setLogιcalThread( ). * @return LogicalThread the logical thread associated with the current * local thread, or null if none. */ public static LogicalThread getLogιcalThread( ) } return (LogicalThread) mappmg. get ( Thread.currentThread(, ) ), /** Set the logical thread associated with the current local thread May * be null to remove an association. SetLogιcalThread( ) replaces any * previous association, which is returned. You should generally restore * the previous association at an appropriate time (unrolling). * @IogιcalThread * @return LogicalThread */ public static LogicalThread setLogιcalThread( LogicalThread logicalThread ) { if (logicalThread = null ) return (LogicalThread) mappιng.remove( Thread currentThread( ) ), else return (LogicalThread) mappιng.put( Thread.currentThread( ), logicalThread), Figure 3 represents the operation of a monitor Withm a smgle platform, monitors have long been used to synchronize threads The present invention extends the use of monitors to distnbuted computmg environments. A distnbuted monitor accordmg to the present invention is designed to work with logical threads, mstead of local threads Distnbuted monitors "belong" to objects, m the sense that the acquisition of a lock by an object is logically similar to "lockmg" the monitor. Two concurrent threads are illustrated in Figure 3. Each thread is local to a different computing platform- Thread 1 which is shown as line 300, and Thread 2 which is shown as line 302. The tick marks on each thread (300 and 302) represent steps m the execution of each respective thread. Accordmg to Figure 3, Thread 1 proceeds with its steps of execution until it reaches a step 310 m which it must acquire access to certain data, shown diagrammahcally as 304. Smce data 304 is a shared resource, it has a monitor 306 associated with it. The monitor 306 is compnsed of a queue 308, a lock 320, and the data 304. It will be understood by practitioners that monitor 306, as shown m Figure 3, is a highly stylized and simplified schematic that is used herein for purposes of illustration More accurate representations of monitors may be found m reputable texts descnbmg operating system architecture At step 310, Thread 1 "enters" the monitor. This action is shown schematically by the arrow 312 extending from step 310 to the monitor 306 m Figure 3. In this example, there are no other threads waitmg m the Queue 308 at the time that Thread 1 entered the monitor. Therefore, Thread 1 gams access to the lock 320, which functionally prevents other threads from accessmg the data 304. The action of gammg access to the lock 320 is shown by arrow 314, which extends from the monitor 306 back to the next step m Thread 1, shown as step 316 along lme 300 Havmg gamed access to the lock 320, Thread 1 proceeds through its steps of execution as shown schematically by successive tick marks along lme 300. Thread 1 has access and control of the shared resource 304 which it uses to perform its calculations. In the example shown by Figure 3, a second thread (labeled Thread 2 and shown schematically by lme 302) attempts to gam access to the shared resource 304 while Thread 1 holds the lock 320. In the example illustrated by Figure 3, Thread 2 is not part of the same logical thread as Thread 1 Therefore Thread 2 is forced to wait in a queue 308, as shown by the arrow labeled 318 In the general case, the queue 308 may hold several threads which are each waitmg to gam access to the shared resource 304 The monitor 306 may be designed to service the queue 308 with a first-in-first-out (FIFO) scheme. A more sophisticated monitor 306 may arrange pnonty in the queue 308 based on performance-enhancing cnteπa. The following example code illustrates the acquisition of a lock on a monitor. Note that an "oid" stands for an "object identifier." /** Acquire a distnbuted monitor lock on the given object. This * is a balking version of monιtorEnter( ) This call can fail if * the object does not have 'Monitor getMonιtor( )' method (NoSuchMethodException) * or if the object is remote and the remote call fails (RemoteException) * Whether or not this call succeeds or fails, it must be balanced by a * call to monιtorExιt( ) * @param. object Object whose monitor is to be used for lockmg * ©exception ObjectNotAvailableException a lock was not available for this object's * monitor. */ public static void momtorLock( Object object ) throws ObjectNotAvailableException { LogicalThread thread = LogιcalThread.startLogιcalThread( ) try { OID oid = (object mstanceof Proxy) ( (Proxy)object) . getOID( ) ObjectTable.put( object ), // First one - acquire lock if ( Ithread.locks contains ( oid ) ) { ιf( object mstanceof Proxy ) ((Proxy) object) .remoteMonitorLockJ ), else Monitor getMonιtor( object ) .monιtorLock( ), } thread.locks.addElement( oid ), } catch( ObjectNotAvailableException e ) / / Stuff in some additional information { throw new ObjectNotAvailableException object), } } Once an object has acquired a lock on a shared resource, it must eventually release the lock to allow other logical threads to gam access The following code illustrates the process for releasmg a lock from a logical thread /** Release a distnbuted monitor lock on the given object. This * is a balking version of monιtorEnter( ). This call can fail if * the object does not have 'Monitor getMonitor( )' method (NoSuchMethodException) * or if the object is remote and the remote call fails (RemoteException). * @param. object Object whose momtor is to be used for lockmg */ public static void monitorExit ( Object object ) { try { OID oid = (object mstanceof Proxy) ? ((Proxy)object) .getOID( ) . ObjectTable.put( object ); LogicalThread thread = getLogιcalThread( ); ιf( thread = = null ) throw new NoLogιcalThreadError( ) // Last one - release lock if ( thread.locks.removeElement ( oid ) &&. Ithread.locks.contams ( oid ) ) { // The mechanics are such that the OED must still be in place when // we make the ( (Proxy) object).remoteMomtorExιt_( ) call since that // vectors directly to another LogιcalThread.momtorExit( ) calls m // Factorylmpl. That second call will do nothing unless the OID is // present in the LogicalThread. Just make sure it gets removed - // hence the finally. thread.locks.addElement( oid ); try { if( object mstranceof Proxy ) ((Proxy)object) .remoteMonιtorExιt_( ); else Monιtor.getMonιtor( object ) .monιtorExιt( ); } finally { thread.locks.removeElement ( oid); } } finally { LogicalThread stopLogιcalThread( ), } It will be apparent to those of skill m the appertaining arts that vanous modifications can be made withm the scope of the above mvention Accordmgly, this mvention is not to be considered limited to the specific examples or embodiments chosen for the purposes of disclosure, but rather to cover all changes and modifications which do not constitute departures from the permissible scope of the present mvention Havmg thus descnbed our mvention, what is desired to be secured and covered by Letter Patent is presented m the appended claims

Claims: What is claimed 1. A method for synchronizing concurrent threads withm a distnbuted computmg network, said method compnsmg the steps of. (a) establishing a unique thread context for a first local thread on a first computer; (b) performing a thread jump from the first computer to a second computer to thereby spawn a second local thread on the second computer, wherem the first computer and the second computer are part of the distnbuted computmg network; and (c) transferring the unique thread context to the second local thread to thereby establish that the first local thread and the second local thread belong to the same logical thread 2 The method according to Claim 1, further compnsmg the steps of (a) acquiring a lock on a distnbuted monitor usmg the first local thread, (b) associatmg the lock with the logical thread; and (c) gammg access to the distnbuted monitor with the second local thread. 3. The method accordmg to Claim 1, further compnsmg the steps of: (a) mappmg, within the first computer, the first local thread to the logical thread; and (b) mappmg, withm the second computer, the second local thread to the logical thread. 4. The method accordmg to Claim 3, further compnsmg the step of updating each mappmg within each computer whenever a new logical thread is created. 5. The method accordmg to Claim 3, further compnsmg the step of updating each mappmg withm each computer whenever a new logical thread is terminated. 6. The method accordmg to Claim 3, wherem the mappmg is a table withm each of the first and second computers, said table contammg associations of local threads to logical threads 7 The method accordmg to Claim 1 , further compnsmg the step of creatmg a distnbuted monitor on shared resources. 8. A computing system for thread synchronization m a distnbuted computmg environment, said system compnsmg a first local thread resident on a first computer; a second local thread resident on a second computer, wherem said first computer and said second computer form at least part of said distnbuted computmg environment, a logical thread compnsed of said first local thread and said second local thread; a first mappmg, stored withm said first computer, associating said first local thread with said logical thread; and a second mapping, stored within said second computer, associating said second local thread with said logical thread. 9. The system according to Claim 8, further comprising a distributed monitor configured to operate on the logical thread. 10. The system according to Claim 9, wherein said distributed monitor is further configured to grant said second local thread access to a shared resource. 11. The system according to Claim 8, wherein said first mapping is a table stored within said first computer, and wherein said second mapping is a table stored within said second computer. 12. A system for thread synchronization in a distributed computing environment, said system comprising: a first local thread resident on a first computer; a second local thread resident on a second computer, wherein said first computer and said second computer form at least part of said distributed computing environment; a logical thread comprised of at least said first local thread and said second local thread; a mapping within said first computer, said mapping associating said first local thread with said logical thread; a mapping within said second computer, said mapping associating said second local thread with said logical thread; a distributed monitor within the distributed computing environment, comprised of (a) a queue, (b) a lock; and (c) a shared resource, wherein said distributed monitor is configured to allow at least said first local thread and said second local thread to gain access to said shared resource whenever said logical thread has gained access to said lock. 13. A digital storage medium within a distributed computing environment, said digital storage medium configured to enable computer operations comprising: (a) executing a first local thread on a first computer (b) executing a second local thread on a second computer, said first computer and said second computer forming at least a portion of said distributed computing environment; (c) defining a logical thread comprised of said first local thread and said second local thread; (d) maintaining a mapping within said first computer to associate said first local thread with said logical thread; (e) maintaining a mapping within said second computer to associate said second local thread with said logical thread; and (f) using a distributed monitor with said logical thread to provide thread synchronization within said distributed computing environment.

Inventors: CONNOR WILLIAM HAYDEN, HADDON BRUCE KENNETH, CONNOR, WILLIAM, HAYDEN, HADDON, BRUCE, KENNETH
Applicants: SUN MICROSYSTEMS INC, SUN MICROSYSTEMS, INC.
Application year: 1999
Main classification: G06F9
IPC codes: G06F9