INTERPROCESS COMMUNICATION USING A SINGLE SEMAPHORE

• US 20120185875A1
• Filed: 03/28/2012
• Published: 07/19/2012
• Est. Priority Date: 07/16/2010
• Status: Active Grant

• Current Assignee: AirBNB Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Bain, Peter D.
• Granted Patent: US 8,527,456 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores

Abstract

A method to enable communication between software processes includes initiating a plurality of processes, the processes including both attachment processes and target processes. A single semaphore is created and initialized for use by the plurality of processes such that each of the target processes wait on the semaphore. An attachment process writes a message file, identifying a specific target process, to a location accessible by the target processes. The attachment process then increments the semaphore by the number of target processes, thereby unblocking the target processes and allowing them to check the message file. When the specific target process determines that the message file is intended for that target, a connection is established between the attachment process and the specific target process. The attachment process then decrements the semaphore to zero to block the target processes. A corresponding computer program product and apparatus are also disclosed herein.

Claims

1. A method for enabling communication between a plurality of processes, the method comprising:

initiating a plurality of processes, the plurality of processes comprising both attachment processes and target processes;

creating and initializing a single semaphore for use by the plurality of processes, such that each of the target processes are initially blocked by the semaphore;

writing, by an attachment process, a message file to a location accessible by the target processes and identifying a specific target process;

incrementing the semaphore by the number of target processes, thereby unblocking the target processes and allowing them to check the message file;

establishing a connection between the attachment process and the specific target process identified in the message file; and

decrementing the semaphore to zero, thereby blocking the target processes.

2. The method of claim 1, wherein, prior to incrementing the semaphore, the attachment process locks synchronization files associated with each of the target processes.

3. The method of claim 2, wherein, after decrementing the semaphore to zero, the attachment process unlocks the synchronization files associated with each of the target processes.

4. The method of claim 1, wherein, prior to incrementing the semaphore, the attachment process locks a master lock file to prevent races with other attachment processes.

5. The method of claim 4, wherein, after decrementing the semaphore to zero, the attachment process unlocks the master lock file.

6. The method of claim 1, wherein each of the plurality of processes is associated with a Java Virtual Machine.

7. The method of claim 1, wherein establishing a connection further comprises establishing an API connection.

8. The method of claim 1, wherein establishing a connection further comprises instructing the specific target process to load one or more tool agents.