Method for distributed transaction support using JDBC 1.0 drivers

• US 6,411,956 B1
• Filed: 06/14/1999
• Issued: 06/25/2002
• Est. Priority Date: 06/14/1999
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Ng, Tony Chun Tung
• Primary Examiner(s): Mizrahi, Diane D.
• Application Number:
  US09/333,141
• Time in Patent Office: 1,107 Days
• Field of Search: 707/4, 707/101, 707/102, 707/103, 707/104.1, 707/10, 709/1, 709/203, 709/204, 709/225, 709/229, 713/156
• US Class Current: 1/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A method is disclosed for providing distributed transaction support functionality using JDBC 1.0 drivers. Instead of creating a new physical database connection for each connection request, an interface driver internally maintains a mapping in a table between a global transaction identifier and the physical database connection. Even if an application requests multiple connections to the same database for the same transaction, all database access through those connections would actually be redirected to the same physical database connection as maintained in the table. This allows all the work to be coordinated under the same transaction. Thus, limited JDBC 2.0 Standard Extension driver compatibility is achieved using standard JDBC 1.0 drivers.

Claims

1. A method for distributed transaction support on a computer system having a database system using a database driver, the method comprising the steps of:

associating a physical database connection with each transaction;

assigning a virtual database connection to a component requesting a database connection; and

associating each virtual database connection with a physical database connection based upon a transaction identifier.

2. The method of claim 1, further comprising the step of:

dynamically swapping virtual connections associated with a same physical connection, in order to provide database connections for each of the components.

3. The method of claim 2, wherein the database driver is a JDBC 1.0 driver.

4. The method of claim 3, wherein the method provides simulation of JDBC 2.0 Standard Extension driver behavior.

5. The method of claim 4, wherein the step of associating comprises the step of forming a table of transaction and connection relationships.

6. The method of claim 5, wherein the method is implemented as an adapter which can interface to a JDBC 1.0 driver.

7. The method of claim 6, wherein the adapter provides a JDBC 2.0 API interface as viewed by a container.

8. The method of claim 7, wherein all the components associated with a transaction are on the same process or Java Virtual Machine (JVM).

9. The method of claim 8, wherein the computer system is a Java 2 Platform Enterprise Edition (J2EE) system.

10. In a computer system database driver adapter, a method for associating multiple database connections with a single transaction, the method comprising the steps of:

associating a physical database connection with each transaction by forming a table of transaction and physical connection relationships;

assigning a virtual database connection to a component requesting a database connection, associating each virtual database connection with a physical database connection based upon a transaction identifier stored in the table; and

dynamically swapping virtual connections associated with a same physical connection, in order to provide database connections for the components.

11. The method of claim 10, wherein the adapter provides simulation of JDBC 2.0 Standard Extension driver behavior.

12. The method of claim 11, wherein the adapter can interface to either a JDBC 1.0 driver.

13. The method of claim 12, wherein the adapter provides a JDBC 2.0 API interface as viewed by a container.

14. The method of claim 13, wherein n all the components associated with a transaction are on the same process or Java Virtual Machine (JVM).

15. The method of claim 14, wherein the computer system is a Java 2 Platform Enterprise Edition (J2EE) system.

16. A method for simulating JDBC 2.0 Standard Extension driver behavior using a standard JDBC 1.0 driver, the method comprising the steps of:

creating a mapping in a table between global transaction identifiers and physical database connections; and

redirecting all database connection requests associated with a global transaction identifier through the same physical database connection as maintained in the table.

17. The method of claim 16, wherein the step of redirecting comprises the steps of:

assigning a virtual connection to a component requesting a database connection; and

associating each virtual database connection with a physical database connection based upon the transaction identifier of the component.

18. The method of claim 17, further comprising the step of:

dynamically swapping virtual connections associated with a same physical connection, in order to provide database connections for each of the components.

19. A distributed transaction support system on a computer having a database, said distributed transaction support system being configured to:

associate a physical database connection with each transaction;

assign a virtual database connection to a component requesting a database connection, and

associate each virtual database connection with a physical database connection based upon a transaction identifier.

20. A distributed transaction support system as recited in claim 19, wherein the database driver is a JDBC 1.0 driver.

21. A distributed transaction support system as recited in claim 19, wherein said distributed transaction support system simulates JDBC 2.0 Standard Extension driver behavior.

22. A computer readable media including computer program code;

said computer readable media comprising;

computer program code for associating a physical database connection with each transaction;

computer program code for assigning a virtual database connection to a component requesting a database connection; and

computer program code for associating each virtual database connection with a physical database connection based upon a transaction identifier.

23. A distributed transaction support system on a computer having a database, said distributed transaction support system being configured to:

associate a physical database connection with each transaction;

assign a virtual database connection to a component requesting a database connection;

associate each virtual database connection with a physical database connection based upon a transaction identifier; and

dynamically swap virtual connections associated with a same physical dynamically swapping virtual connections associated with a same physical connection, in order to provide database connections for each of the components.

24. A computer readable media including computer program code;

said computer readable media comprising;

computer program code for associating a physical database connection with each transaction;

computer program code for assigning a virtual database connection to a component requesting a database connection;

computer program code for associating each virtual database connection with a physical database connection based upon a transaction identifier; and

computer program code for dynamically swapping virtual connections associated with a same physical connection, in order to provide database connections for each of the components.