Mechanism for enabling session information to be shared across multiple processes

• US 6,938,085 B1
• Filed: 05/19/2000
• Issued: 08/30/2005
• Est. Priority Date: 09/24/1999
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Ramachandran, Viswanath, Belkin, Ruslan
• Primary Examiner(s): Maung, Zarni
• Assistant Examiner(s): Halim, Sahera
• Application Number:
  US09/574,398
• Time in Patent Office: 1,929 Days
• Field of Search: 709/227, 709/312, 709/228, 709/215, 709/213, 709/214, 709/217, 711/205
• US Class Current: 709/227
• CPC Class Codes: G06F 2209/5016 Session
• CPC Class Codes: G06F 2209/5018 Thread allocation
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: H04L 67/01 Protocols

Abstract

A mechanism for enabling session information to be shared across multiple processes in a multi-process environment is disclosed. There is provided a shared persistent memory-mapped file in a file system, which is mapped to the memory space of each of the processes. This file is used by all of the processes to store session information. Because the memory space of each process is mapped to the shared file, each process is able to access and manipulate all of the sessions in the system. Thus, sessions are no longer maintained on a process-specific basis. Rather, they are maintained on a centralized, shared basis. As a result, different requests pertaining to the same session may be serviced by different server processes without any adverse effects. Each process will be able to access and manipulate all of the state information pertaining to that session. By enabling session information to be shared, this mechanism eliminates the session management errors experienced by the prior art.

Claims

1. A computer system, comprising:

a memory-mapped file;

a first server process, said first server process servicing a first request pertaining to a particular session, said first server process storing session information pertaining to said particular session in said memory-mapped file; and

a second server process, said second server process servicing a second request pertaining to said particular session, said second server process accessing said session information from said memory-mapped file and using said session information to service said second request;

wherein said memory-mapped file is mapped to at least a portion of a virtual memory space of said first server process and at least a portion of a virtual memory space of said second server process.

2. The system of claim 1, wherein said first server process stores said session information into said memory-mapped file in the form of a serialized byte stream.

3. The system of claim 2, wherein said second server process deserializes said serialized byte stream prior to using said session information to service said second request.

4. The system of claim 1,wherein said second server process sets a busy indicator associated with said session information to indicate that said session information is currently in use, thereby preventing any other server process from using said session information while said second server process is using said session information.

5. The system of claim 1, wherein said second server process updates said session information to derive a set of updated session information, and wherein said second server process stores said updated session information in said memory-mapped file.

6. The system of claim 5, wherein said updated session information replaces said session information in said memory-mapped file.

7. The system of claim 6, further comprising:

a third server process, said third server process servicing a third request pertaining to said particular session, said third server process accessing said updated session information from said memory-mapped file and using said updated session information to service said third request.

8. A computer-implemented method for servicing requests, comprising:

instantiating a first server process;

instantiating a second server process;

receiving a first request pertaining to a particular session;

servicing said first request with said first server process, said first server process storing session information pertaining to said particular session in a memory-mapped file;

receiving a second request pertaining to said particular session; and

servicing said second request with said second server process, said second server process accessing said session information from said memory-mapped file and using said session information to service said second request;

mapping at least a portion of a virtual memory space of said first server process to said memory-mapped file; and

mapping at least a portion of a virtual memory space of said second server process to said memory-mapped file.

9. The method of claim 8, wherein said first server process stores said session information into said memory-mapped file in the form of a serialized byte stream.

10. The method of claim 9, wherein said second server process deserializes said serialized byte stream prior to using said session information to service said second request.

11. The method of claim 8, wherein servicing said second request comprises:

setting a busy indicator associated with said session information to indicate that said session information is currently in use, thereby preventing any other server process from using said session information while said second server process is using said session information.

12. The method of claim 8, wherein servicing said second request comprises:

updating said session information to derive a set of updated session information; and

storing said updated session information into said memory-mapped file.

13. The method of claim 12, wherein storing said updated session information into said memory-mapped file comprises:

overwriting said session information with said updated session information.

14. The method of claim 13, further comprising:

instantiating a third server process;

receiving a third request pertaining to said particular session; and

servicing said third request with said third server process, said third server process accessing said updated session information from said memory-mapped file and using said updated session information to service said third request.

15. A computer readable medium having stored thereon instructions which, when executed by one or more processors, cause the one or more processors to service requests, said computer readable medium comprising

instructions for causing one or more processors to instantiate a first server process;

instructions for causing one or more processors to instantiate a second server process;

instructions for causing one or more processors to receive a first request pertaining to a particular session;

instructions for causing one or more processors to service said first request with said first server process, said first server process storing session information pertaining to said particular session in a memory-mapped file;

instructions for causing one or more processors to receive a second request pertaining to said particular session; and

instructions for causing one or more processors to service said second request with said second server process, said second server process accessing said session information from said memory-mapped file and using said session information to service said second request;

instructions for causing one or more processors to map at least a portion of a virtual memory space of said first server process to said memory-mapped file; and

instructions for causing one or more processors to map at least a portion of a virtual memory space of said second server process to said memory-mapped file.

16. The computer readable medium of claim 15, wherein said first server process stores said session information into said memory-mapped file in the form of a serialized byte stream.

17. The computer readable medium of claim 16, wherein said second server process deserializes said serialized byte stream prior to using said session information to service said second request.

18. The computer readable medium of claim 15, wherein the instructions for causing one or more processors to service said second request comprises:

instructions for causing one or more processors to set a busy indicator associated with said session information to indicate that said session information is currently in use, thereby preventing any other server process from using said session information while said second server process is using said session information.

19. The computer readable medium of claim 15, wherein the instructions for causing one or more processors to service said second request comprises:

instructions for causing one or more processors to update said session information to derive a set of updated session information; and

instructions for causing one or more processors to store said updated session information into said memory-mapped file.

20. The computer readable medium of claim 19, wherein the instructions for causing one or more processors to store said updated session information into said memory-mapped file comprises:

instructions for causing one or more processors to overwrite said session information with said updated session information.

21. The computer readable medium of claim 20, further comprising:

instructions for causing one or more processors to instantiate a third server process;

instructions for causing one or more processors to receive a third request pertaining to said particular session; and

instructions for causing one or more processors to service said third request with said third server process, said third server process accessing said updated session information from said memory-mapped file and using said updated session information to service said third request.