SYSTEM AND METHOD FOR SUPPORTING ONE-WAY REMOTE METHOD INVOCATION FOR SESSION REPLICATION IN A SERVER CLUSTER

• US 20120144045A1
• Filed: 09/15/2011
• Published: 06/07/2012
• Est. Priority Date: 09/15/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Revanuru, Naresh, Torstensson, Patrik, Otenko, Oleksandr, Bihani, Ballav, Agarwal, Prashant
• Granted Patent: US 8,856,352 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 15/17318 Parallel communications techniques, e.g. gather, scatter, reduce, roadcast, multicast, all to all
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 49/358 Infiniband Switches
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: Y10T 409/308904 : Multiple row dividing head
• CPC Class Codes: Y10T 409/309072 : including cutter limited to rotary motion
• CPC Class Codes: Y10T 409/309128 : with means to adjust work support vertically
• CPC Class Codes: Y10T 409/309352 : Cutter spindle or spindle support
• CPC Class Codes: Y10T 409/309408 : with cutter holder

Abstract

A system and method can support one-way Remote Method Invocation (RMI) session replication in a middleware machine environment, such as a server cluster. The server cluster can include a primary application server and a secondary application server. The primary application server receives a request with a session from a client, maintain the session information, and replicate the session information to a secondary application server using one-way Remote Method Invocation (RMI). The primary application server can then respond to the client based on the session information after receiving a return message of the one-way RMI from a network socket associate with the primary application server. The benefit of using one-way RMI is that the primary application server does not have to wait for an acknowledgment from the secondary application server instance, since the underlying transport protocol guarantees that the session data has been successfully transmitted to the second server instance.

Claims

1. A method for supporting session replication in a server cluster, comprising:

receiving, via a primary application server, a request associated with a session from a client;

replicating, via the primary application server, session information associated with the session in the request to a secondary application server using one-way Remote Method Invocation (RMI);

receiving, via the primary application server, a return message from a network socket associate with the primary application server; and

responding, via the primary application server, to the client based on the session information without waiting for a response from the secondary application server.

2. The method according to claim 1, further comprising:

serializing the session information by the primary application server before it is replicated to the secondary application server.

3. The method according to claim 2, further comprising:

allowing the secondary application server to deserialize the serialized session information before responding to the client, when the primary application server fails.

4. The method according to claim 1, further comprising:

supporting one-way RMI session replication based on a socket direct protocol (SDP).

5. The method according to claim 4, further comprising:

allowing a virtual machine that runs underneath the primary application server to automatically set up a SDP socket for transmitting session information to the secondary application server using one-way RMI.

6. The method according to claim 4, further comprising:

setting up a first SDP socket on the primary application server side and setting up a second SDP socket on the secondary application server side.

7. The method according to claim 6, further comprising:

initiating, via the primary application server, a send call to the first SDP socket to start transmitting the session information;

informing, via the first SDP socket, the second SDP socket that the session information is available;

instructing, via the secondary application server, the second SDP socket to receive the session data;

performing, via the second SDP socket, a read operation to grab the session data from a buffer associated the primary application server;

informing, via the second SDP socket, the first SDP socket when the RDMA read operation is completed; and

sending, via the first SDP socket, a return message to the primary application server and separately sending, via the second SDP socket, a return message to the secondary application server.

8. The method according to claim 1, further comprising:

allowing the primary application server to select one of multiple replication channels to replicate the session information to at least one of multiple secondary application servers.

9. The method according to claim 8, further comprising:

allowing different data transport protocol to be used in different replication channels.

10. The method according to claim 8, further comprising:

ensuring that all session information in a particular session is replicated through a particular channel that is configured for performing one-way RMI session replication.

11. A system for supporting in-memory session replication in a server cluster, comprising:

one or more processors,

a primary application server running on the one or more processors, wherein the primary application server operated to perform the steps of

receiving a request associated with a session from a client;

replicating session information associated with the session in the request to a secondary application server using one-way Remote Method Invocation (RMI);

receiving a return message from a network socket associate with the primary application server; and

responding to the client based on the session information without waiting for a response from the secondary application server.

12. A machine readable medium having instructions stored thereon that when executed cause a system to:

receive, via a primary application server, a request associated with a session from a client;

replicate, via the primary application server, session information associated with the session in the request to a secondary application server using one-way Remote Method Invocation (RMI);

receive, via the primary application server, a return message from a network socket associate with the primary application server; and

respond, via the primary application server, to the client based on the session information without waiting for a response from the secondary application server.