Transaction sticky load balance policies

• US 9,600,341 B2
• Filed: 09/14/2009
• Issued: 03/21/2017
• Est. Priority Date: 09/14/2009
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Zamarreo, Galder, Stansberry, Brian Edward
• Primary Examiner(s): Lazaro, David
• Assistant Examiner(s): KOROBOV, VITALI A
• Application Number:
  US12/558,714
• Publication Number:
  US 20110066672A1
• Time in Patent Office: 2,745 Days
• Field of Search: 709/203, 709/217, 709/227
• US Class Current: 1/1
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

A transaction sticky load balance policy allows a remote client to choose a target server node from a server cluster to provide a transaction service. The load balance policy directs invocations of business methods within a transaction to the same target server node. The remote client receives the load balance policy from a proxy, which is downloaded to the remote client from one of the server nodes in the server cluster. The remote client selects a target server node according to the load balance policy. The remote client then invokes the business methods within a transaction on the target server node via the proxy. The target server node can execute all of the business methods within the transaction on a Java virtual machine. The business methods can be implemented with Enterprise JavaBeans (EJBs).

Claims

1. A method comprising:

executing, by a processing device of an application server, a transaction service, the application server being one of a plurality of application servers in an application server cluster, the plurality of application servers in the application server cluster executing the transaction service concurrently;

identifying, by the processing device, a policy for selecting one of the plurality of application servers in the application server cluster as a single application server for a transaction comprising a plurality of transaction-related operations, wherein the policy directs all of a plurality of invocations corresponding to the plurality of transaction-related operations of the transaction to the single application server to protect data integrity of the transaction;

receiving component configuration information indicating one or more components of the transaction service to be configured with the policy;

generating, by the processing device, a proxy in view of the policy and the component configuration information; and

providing, by the processing device, the proxy to a remote client, the proxy containing the policy directing the proxy to send all of the plurality of invocations of the plurality of transaction-related operations of the transaction to the single application server.

2. The method of claim 1, further comprising:

executing all of the plurality of transaction-related operations within the transaction on a Java virtual machine on the single application server.

3. The method of claim 1, wherein the plurality of transaction-related operations are implemented with Enterprise JavaBeans™

(EJBs).

4. The method of claim 1, wherein the policy comprises a configuration of a Management Bean (MBean) that manages the transaction service and the component configuration information comprises a configuration of EJBs that implement the plurality of transaction-related operations comprising the transaction service.

5. The method of claim 1, wherein the policy directs invocations of all of the plurality of transaction-related operations within a next transaction to a different application server in the application server cluster than the single application server.

6. The method of claim 1, wherein the policy comprises one of the following:

transaction sticky round robin, transaction sticky first available, transaction sticky first available all proxies, or transaction sticky random robin.

7. A method comprising:

receiving, by a processing device of a remote client, a request to perform a plurality of transaction-related operations of a transaction, wherein the plurality of transaction-related operations correspond to a plurality of invocations to invoke the plurality of transaction-related operations, and are undoable in response to failure of one of the plurality of transaction-related operations;

selecting, by the processing device, in view of a policy stored on the remote client, a single application server from a plurality of application servers in an application server cluster according to the policy, wherein the plurality of application servers in the application server cluster execute a transaction service concurrently to perform the plurality of transaction-related operations, and wherein the policy directs all of the plurality of invocations of the plurality of transaction-related operations of the transaction to the single application server;

directing, by the processing device, a first invocation of the plurality of invocations of the plurality of transaction-related operations within the transaction to the single application server to cause a corresponding first transaction-related operation of the plurality of the transaction-related operations within the transaction to be executed by a Java virtual machine on the single application server;

identifying a second transaction-related operation of the plurality of the transaction-related operations to be performed for the transaction;

determining, by the processing device, from the policy to direct a second invocation of the plurality of invocations to the single application server to cause the second transaction-related operation to be executed by the single application server to protect data integrity of the transaction; and

directing the second invocation of the plurality of invocations to the single application server.

8. The method of claim 7, wherein the plurality of transaction-related operations are implemented with Enterprise JavaBeans™

(EJBs).

9. The method of claim 7, wherein the load balance policy directs invocations of all of the plurality of transaction-related operations within a next transaction to a different application server in the application server cluster than the single application server.

10. The method of claim 7, further comprising:

determining the single application server for each transaction using the proxy.

11. The method of claim 7, further comprising:

determining whether an invocation of each transaction-related operation is successful; and

in response to a determination that the invocation is unsuccessful, selecting a different application server in the application server cluster to re-send the invocation.

12. A system comprising:

memory; and

a processing device of an application server being one of a plurality of application servers in an application server cluster, the processing device, operatively coupled to the memory, to;

execute a transaction service, the plurality of application servers the application server cluster to execute the transaction service concurrently; and

identify a policy for selecting one of the plurality of application servers in the application server cluster as a sing application server for a transaction comprising a plurality of transaction-related operations, wherein the policy directs all of a plurality of invocations corresponding to the plurality of transaction-related operations of the transaction to the single application server to protect data integrity of the transaction;

receive component configuration information indicating one or more components of the transaction service to be configured with the policy;

generate a proxy in view of the policy and the component configuration information; and

provide the proxy to a remote client, the proxy containing the policy directing the proxy to send all of the plurality of invocations of the plurality of transaction-related operations of the transaction to the single application server.

13. The system of claim 12, wherein the plurality of transaction-related operations are implemented with Enterprise JavaBeans™

(EJBs), and wherein the memory is to store data to be accessed by a Java-based transaction service.

14. The system of claim 12, wherein the proxy determines a different application server than the single application server in the application server cluster for the remote client when a new transaction starts.

15. The system of claim 12, wherein the proxy re-sends an invocation of a transaction-related operation to a different application server than the single application server in the application server cluster in response to a determination that a prior invocation was unsuccessful.

16. The system of claim 12, wherein policy comprises a configuration of a Management Bean (MBean) that manages the transaction service and the component configuration information comprises configuration of EJBs that implement the transaction-related operations comprising the transaction service.

17. A non-transitory computer readable storage medium including instructions that, when executed by a processing device of an application server being one of a plurality of application servers in an application server cluster, cause the processing device to:

execute, by the processing device, a transaction service, the plurality of application servers in the application server cluster to execute the transaction service concurrently;

identify, by the processing device, a policy for selecting one of the plurality of application servers in the application server cluster as a single application server for a transaction comprising a plurality of transaction-related operations, wherein the policy directs all of a plurality of invocations corresponding to the plurality of transaction-related operations of the transaction to the single application server to protect data integrity of the transaction;

receive component configuration information indicating one or more components of the transaction service to be configured with the policy;

generate, by the processing device, a proxy in view of the policy and the component configuration information; and

provide the proxy to a remote client, the proxy containing the policy directing the proxy to send all of the plurality of invocations of the plurality of transaction-related operations of the transaction to the single application server.

18. The non-transitory computer readable storage medium of claim 17, wherein the operations, when executed by the processing device, further cause the processing device to:

execute all of the transaction-related operations within the transaction on a Java virtual machine on the target server node.

19. The non-transitory computer readable storage medium of claim 17, wherein the plurality of transaction-related operations are implemented with Enterprise JavaBeans™

(EJBs).

20. The non-transitory computer readable storage medium of claim 17, wherein the policy comprises a configuration of a Management Bean (MBean) that manages the transaction service and the component configuration information comprises a configuration of EJBs that implement the transaction-related operations comprising the transaction service.