Abstract: Roll back strategies for database deadlock resolution are customized by identifying a first transaction to a database, identifying a second transaction to the database and detecting a deadlock between the first and second transactions with respect to the database. The deadlock is resolved based upon a predetermined roll back strategy associated with at least one of the first or second transactions to identify a select one of the first and second transactions for roll back and a request is conveyed to roll back the selected one of the first and second transactions, wherein the preferred transaction is allowed to continue processing.

Abstract: Embodiments of the invention provide a method, system and computer program product for SLA cognizant database connection management for multi-tenant environments. In an embodiment of the invention, a method for SLA cognizant database connection management for multi-tenant environments includes receiving different requests for data in a database from different application instances executing in memory of a host computing system supporting a multi-tenant computing environment and determining a priority for each of the requests. The method also includes selecting for each request a particular portion of a database connection pool of a multiplicity of database connections to the database, in that the particular portion is associated with a corresponding priority of the request, and each portion of the database connection pool includes one or more of the database connections.

Abstract: Embodiments of the invention provide a method, system and computer program product for SLA cognizant database connection management for multi-tenant environments. In an embodiment of the invention, a method for SLA cognizant database connection management for multi-tenant environments includes receiving different requests for data in a database from different application instances executing in memory of a host computing system supporting a multi-tenant computing environment and determining a priority for each of the requests. The method also includes selecting for each request a particular portion of a database connection pool of a multiplicity of database connections to the database, in that the particular portion is associated with a corresponding priority of the request, and each portion of the database connection pool includes one or more of the database connections.

Abstract: Embodiments of the invention provide a method, system and computer program product for SLA cognizant database connection management for multi-tenant environments. In an embodiment of the invention, a method for SLA cognizant database connection management for multi-tenant environments includes receiving different requests for data in a database from different application instances executing in memory of a host computing system supporting a multi-tenant computing environment and determining a priority for each of the requests. The method also includes selecting for each request a particular portion of a database connection pool of a multiplicity of database connections to the database, in that the particular portion is associated with a corresponding priority of the request, and each portion of the database connection pool includes one or more of the database connections.

Abstract: Embodiments of the invention provide a method, system and computer program product for SLA cognizant database connection management for multi-tenant environments. In an embodiment of the invention, a method for SLA cognizant database connection management for multi-tenant environments includes receiving different requests for data in a database from different application instances executing in memory of a host computing system supporting a multi-tenant computing environment and determining a priority for each of the requests. The method also includes selecting for each request a particular portion of a database connection pool of a multiplicity of database connections to the database, in that the particular portion is associated with a corresponding priority of the request, and each portion of the database connection pool includes one or more of the database connections.

Abstract: Systems and methods to modify a set of connection records are described. A determination is made that an application failed to access a first database via a connection record, where the connection record includes data to access the first database. A determination is made that a second database is accessible, where the second database is a failover database to the first database. A set of connection records associated with the first database is modified to enable access to the second database.

Abstract: A computer system and storage medium that, in an embodiment, receive an allocation request for a resource and registers the resource as a non-voting participant if the resource desires to delegate commit voting to another resource. The registered resource is then prohibited from participating in an enclosing transactional context and instead is informed when the transaction completes. The resource is enlisted as a voting participant if the resource does not desire to delegate commit voting. In this way, when multiple resources are used in a transaction, a resource may be registered and receive notifications of transaction completion instead of being enlisted and voting on commit decisions. The result of a transaction in which a single resource takes responsibility for a number of other resources is that transaction completion avoids the two-phase commit protocol and the resulting performance degradation.

Abstract: Systems and methods to modify a set of connection records are described. A determination is made that an application failed to access a first database via a connection record, where the connection record includes data to access the first database. A determination is made that a second database is accessible, where the second database is a failover database to the first database. A set of connection records associated with the first database is modified to enable access to the second database.

Abstract: A computer system and storage medium that, in an embodiment, receive an allocation request for a resource and registers the resource as a non-voting participant if the resource desires to delegate commit voting to another resource. The registered resource is then prohibited from participating in an enclosing transactional context and instead is informed when the transaction completes. The resource is enlisted as a voting participant if the resource does not desire to delegate commit voting. In this way, when multiple resources are used in a transaction, a resource may be registered and receive notifications of transaction completion instead of being enlisted and voting on commit decisions. The result of a transaction in which a single resource takes responsibility for a number of other resources is that transaction completion avoids the two-phase commit protocol and the resulting performance degradation.

Abstract: Roll back strategies for database deadlock resolution are customized by identifying a first transaction to a database, identifying a second transaction to the database and detecting a deadlock between the first and second transactions with respect to the database. The deadlock is resolved based upon a predetermined roll back strategy associated with at least one of the first or second transactions to identify a select one of the first and second transactions for roll back and a request is conveyed to roll back the selected one of the first and second transactions, wherein the preferred transaction is allowed to continue processing.

Abstract: A method, apparatus, system, and signal-bearing medium that, in an embodiment, receive an allocation request for a resource and registers the resource as a non-voting participant if the resource desires to delegate commit voting to another resource. The registered resource is then prohibited from participating in an enclosing transactional context and instead is informed when the transaction completes. The resource is enlisted as a voting participant if the resource does not desire to delegate commit voting. In this way, when multiple resources are used in a transaction, a resource may be registered and receive notifications of transaction completion instead of being enlisted and voting on commit decisions. The result of a transaction in which a single resource takes responsibility for a number of other resources is that transaction completion avoids the two-phase commit protocol and the resulting performance degradation.

Abstract: An apparatus and method enable batch processing of database updates without modifying generated code, i.e., without redeployment of the application server or application. A batch mechanism intercepts calls from the generated code, compiles updates into batches, and processes the updates to the database in batches. In this manner the batch mechanism takes advantage of the batch processing capabilities of the database without modifying the generated code.