Abstract: A logging last resource (LLR) system can provide a transaction log and transaction data to a LLR resource after a number of two-phase-commit resources have been prepared. The LLR resource manager can operate on the transaction log and transaction data in an atomic fashion so that the one-phase or local commit can be done. The one-phase or local commit can be done by the LLR manager in an atomic manner.

Abstract: An embodiment of the invention allows a software developer or administrator to use their knowledge and/or development of a particular application, to optimize the performance of data access and updates to the database. In order to do this, an embodiment of the invention makes use of the developers knowledge of particular transaction and transaction operations that can be performed in a commutative manner. The overall effect is to perform the operations in a parallel fashion so that one operation does not block or restrict the processing of a second operation. The result is an increase in database access or performance, without any resulting decrease in database reliability.

Abstract: An embodiment of the invention provides an ability to configure the dispatch policy in an application or transaction server. For servlets and JSP's this is configured on a per-URL (Uniform Resource Locator) basis, RMI and EJB it is configured on a per-method basis. Available dispatch options include the ability to execute the request in the same thread that read the request or to enqueue it on a queue which feeds a pool of worker threads. Using this configuration one can control various quality of service parameters of the requests. Requests may be expedited by executing them directly in the thread which read them, thus skipping the queue. Alternatively, some requests may be throttled by assigning them to a queue which is tended by only a limited number of threads.

Abstract: An embodiment of the invention allows a software developer or administrator to use their knowledge and/or development of a particular application, to optimize the performance of data access and updates to the database. In order to do this, an embodiment of the invention makes use of the developers knowledge of particular transaction and transaction operations that can be performed in a commutative manner. The overall effect is to perform the operations in a parallel fashion so that one operation does not block or restrict the processing of a second operation. The result is an increase in database access or performance, without any resulting decrease in database reliability.

Abstract: An embodiment of the invention provides an ability to configure the dispatch policy in an application or transaction server. For servlets and JSP's this is configured on a per-URL (Uniform Resource Locator) basis, RMI and EJB it is configured on a per-method basis. Available dispatch options include the ability to execute the request in the same thread that read the request or to enqueue it on a queue which feeds a pool of worker threads. Using this configuration one can control various quality of service parameters of the requests. Requests may be expedited by executing them directly in the thread which read them, thus skipping the queue. Alternatively, some requests may be throttled by assigning them to a queue which is tended by only a limited number of threads.

Abstract: A method for using available server threads to process resources and reduce the overall time of performing XA interactions in two-phase commit protocol implemented by the transaction manager. A TM processing XA interactions dispatches interaction commands for multiple resources to a thread manager, which dispatches the commands to idle server threads. In one embodiment, the TM attempts to dispatch all but one of the interaction commands to separate threads. The primary thread then processes the remaining resource command. Any commands relating to dispatch requests that were unable to be dispatched to separate threads due to unavailability are processed by the primary thread. Once the primary server has processed its interaction commands and received a signal indicating the threads receiving dispatch requests have completed their respective processing of dispatched commands, the next group of commands is processed in a similar manner.

Abstract: A system for using available server threads to process resources and reduce the overall time of performing XA interactions in two-phase commit protocol implemented by the transaction manager. A TM processing XA interactions dispatches interaction commands for multiple resources to a thread manager, which dispatches the commands to idle server threads. In one embodiment, the TM attempts to dispatch all but one of the interaction commands to separate threads. The primary thread then processes the remaining resource command. Any commands relating to dispatch requests that were unable to be dispatched to separate threads due to unavailability are processed by the primary thread. Once the primary server has processed its interaction commands and received a signal indicating the threads receiving dispatch requests have completed their respective processing of dispatched commands, the next group of commands is processed in a similar manner.

Abstract: An improved resource pool is provided that provides for dynamic configuration and is comprised of code that is configured to be used for different subsystems, including JDBC, Connector, and JMS subsystems. Pool maintenance, resource object creation and timeout, multiple deque management, and pool state transition features are provided. An application server may include at least one resource pool object, wherein each resource pool object represents a resource pool in the application server. An improved prepared statement cache is also provided that works in conjunction with the resource pool implementation to more effectively provide for prepared statement processing.

Abstract: A method for an improved resource pool is provided that provides for dynamic configuration and is comprised of code that is configured to be used for different subsystems, including JDBC, Connector, and JMS subsystems. Pool maintenance, resource object creation and timeout, multiple deque management, and pool state transition features are provided. An application server may include at least one resource pool object, wherein each resource pool object represents a resource pool in the application server. A method for an improved prepared statement cache is also provided that works in conjunction with the resource pool implementation to more effectively provide for prepared statement processing.

Abstract: The performance of a database system can be improved by tracking the way in which data is accessed. By tracking such information, it is possible to load frequently-accessed fields of an entity bean, as well as related beans that are frequently accessed, by optimizing a field group for that entity bean. It is also possible to use the tracking information to prevent infrequently accessed fields from being automatically loaded. Information to be monitored can include how often each field is accessed, how many times a particular entity or application accesses a field, and how often a field is accessed for a given transaction context. By using this information to periodically optimize field groups, the fields and associated entity beans that are most often accessed, such as by the entity and/or transaction causing the entity bean to be loaded, can be automatically loaded when an entity bean is loaded into a container.

Abstract: A runtime architecture for Web services utilizes a container driver to accept an invoke request for Web services. The container driver performs any necessary data binding/unbinding required to process the invoke request and associated message context, utilizing an appropriate plugin component. An interceptor receives the context information and modifies the message context for Web service compatibility. An invocation handler receives the formatted context information and passes parameters from the message context to the target of the request. The invocation handler processes values returned from the target and passes them to the container driver, which can formulate and return a response, along with the message context, to the client or protocol adapter.

Abstract: Transactions are granted concurrent access to a data item through the use of an optimistic concurrency algorithm. Each transaction gets its own instance of the data item, such as in a cache or in an entity bean, such that it is not necessary to lock the data. The instances can come from the data or from other instances. When a transaction updates the data item, the optimistic concurrency algorithm ensures that the other instances are notified that the data item has been changed and that it is necessary to read a new instance, from the database or from an updated instance.

Abstract: A system and a method for dynamic or as-needed activation of Remote Method Invocation (RMI) layer remote objects in response to a client request. Object activation allows the system to clean up or delete currently unused remote objects, and then reactivate them when a client actually needs them. An object implementation can first be created in response to a client request. The client receives a remote reference (remote ref) and an activation identifier (activation id) identifying that particular implementation. The implementation can subsequently be cleaned up or deleted during garbage collection so as to save server resources, or alternatively the object can be reused if the system is set up to maintain a pool of objects. When the client requests the same object at a later point in time, the system activates an object based on the activation ID previously received from the server.

Abstract: The performance of a database system can be improved by tracking the way in which data is accessed. By tracking such information, it is possible to load frequently-accessed fields of an entity bean, as well as related beans that are frequently accessed, by optimizing a field group for that entity bean. It is also possible to use the tracking information to prevent infrequently accessed fields from being automatically loaded. Information to be monitored can include how often each field is accessed, how many times a particular entity or application accesses a field, and how often a field is accessed for a given transaction context. By using this information to periodically optimize field groups, the fields and associated entity beans that are most often accessed, such as by the entity and/or transaction causing the entity bean to be loaded, can be automatically loaded when an entity bean is loaded into a container.

Abstract: An embodiment of the invention allows a software developer or administrator to use their knowledge and/or development of a particular application, to optimize the performance of data access and updates to the database. In order to do this, an embodiment of the invention makes use of the developers knowledge of particular transaction and transaction operations that can be performed in a commutative manner. The overall effect is to perform the operations in a parallel fashion so that one operation does not block or restrict the processing of a second operation. The result is an increase in database access or performance, without any resulting decrease in database reliability.

Abstract: An embodiment of the invention provides an ability to configure the dispatch policy in an application or transaction server. For servlets and JSP's this is configured on a per-URL (Uniform Resource Locator) basis, RMI and EJB it is configured on a per-method basis. Available dispatch options include the ability to execute the request in the same thread that read the request or to enqueue it on a queue which feeds a pool of worker threads. Using this configuration one can control various quality of service parameters of the requests. Requests may be expedited by executing them directly in the thread which read them, thus skipping the queue. Alternatively, some requests may be throttled by assigning them to a queue which is tended by only a limited number of threads.

Abstract: In a traditional application server that uses servlets, when a request is dispatched to a thread the service() method of the appropriate servlet is called. When the service( ) method returns the response is sent. This is sub-optimal in the case that an asynchronous event must occur before the response can be sent, because the thread running the servlet must block until the event occurs. The invention provides for asynchronous processing of such requests. In one embodiment, the invention provides an extension to the Servlet API which allows the service( ) method to return (and thus the thread to be freed) before the response is ready to be sent. Then when the asynchronous event later occurs the response may be completed and sent.

Abstract: In an account transaction such as an ATM transaction, a server in communication with an ATM stores a copy of the account balance. Before processing the transaction, the server reads the balance from memory and determines whether the account contains sufficient funds for the transaction. In order to prevent overdrawing of the account, the server makes any balance update predicated on the fact that the current balance in the account database is the same as the balance of the local copy of the account. If the account balance stored in the database is not the same, the server rolls back the request and updates the account balance stored in the local copy. This process continues until either the account balance is updated or the transaction is aborted.

Abstract: Concurrency can be maintained in cluster caching when processing an update request on network server that is storing a local copy of a data item. The request can be processed using the local copy of the data item. A predicated update request can be sent to a network database storing the data item, wherein the database can commit the update if the local copy is current with the data item. If the local copy is not current, the network server can request a new copy, process the request using the current copy, and try another predicated request. The process can continue until the update is committed to the database or aborted. Once committed, any other servers in the cluster can be notified that the data item has been updated. Those other servers can drop any local copy of the data item and can request an updated copy of the data item.

Abstract: A session replication system provides real-time data replication without unnecessarily slowing down the user experience. A system in accordance with the present invention may utilize a primary server to serve requests from a network client, as well as a secondary server to replicate the session information. When a request is received on the session, an attempt may be made to serve the request on the primary server. If the primary is unable to receive or respond to the request, the request may be served on the secondary server or on a new primary server. If the secondary server receives the request, the secondary server may become the new primary server. If a new primary server is selected, the new primary may request the session information from the secondary server.