Abstract: A system and method are described in which session objects are organized and managed within a structured hierarchy of session object storage units, referred to herein as “session domains.” The session domains store session objects sharing one or more related characteristics. In one embodiment, a separate hierarchy of session domains is implemented within each layer of an enterprise application server. For example, in a Java 2 Enterprise Edition (“J2EE”) environment, a separate set of hierarchically-arranged session domains are generated for the EJB container, the Web container and the portal container. In addition, in one embodiment of the invention, the lifecycles of each of the session objects are managed based on the relationships between each of the session objects. The relationships may either be explicit or implicit.

Abstract: A system and method to monitor client sessions within a Java virtual machine. Client sessions are established within an application server instance to store session context data for each of the client sessions during the client sessions. At least two Java virtual machines are operated within the application server instance to service client requests received from clients associated with each of the client sessions. Status information about each of the client sessions is reported into shared memory external to the Java virtual machines to monitor each of the client sessions during operation of the Java virtual machines.

Abstract: A cluster includes a plurality of application server instances, a central services instance that includes a message server, and a database. The application server instances each include a dispatcher, a plurality of redundant server nodes, and a socket connection between the dispatcher and each of the server nodes for handling communications relating to processing a client request. A separate socket connection between the message server and each of the server nodes is provided for handling internal communications between the server nodes. Additionally, a third socket connection may be established directly between server nodes.

Abstract: Embodiments include a timeout event management system that registers timeout events and checks for and corrects inaccuracies in timing caused by hibernation or system time changes. The timeout event management system may trigger an event after an intended delay time or at an intended expiration time. A handler program may be called in response to the triggered timeout. In an additional embodiment, the timeout system may track timeout events in a priority queue data structure.