Abstract: A system receives a management configuration set defining at least one event to be detected in the application server, and a respective associated action to be taken upon detection of the events. For each of the events to be detected in the application server, the system instantiates an event class to detect the event. For each of the actions to be taken upon detection of the event by the event class, the system instantiates a respective action class to perform that action on behalf of the event class that detects the event. The system operates the instantiated event classes to detect events and to send an event notification to each of the respective action class associated with that event.

Abstract: Embodiments of a request failover mechanism may be used to failover requests from clients of server instances in a cluster to alternative server instances. One embodiment may use cluster-aware remote references that include the IIOP endpoints at which the application server instances forming the cluster listen to IIOP requests. Using a cluster-aware remote reference to an object on an application server instance, a request to the object may be failed-over to an alternate endpoint in the cluster when the primary endpoint is unreachable. In one embodiment, once a request for a referenced object is failed over to a new server instance, all the subsequent requests to that object will continue to go to the same server instance even if the original server instance becomes available. One embodiment may provide client-side IIOP request load balancing in clustered application server environments through a load balancer subsystem using the cluster-aware remote references.

Abstract: System and method for bridging between inter-object communication interfaces, such as RMI and IIOP, may include in one embodiment a bridge mechanism that maintains a cache of reference objects. The key used for hashing in the cache may be based on the object identifier (OID) of the reference objects. In one embodiment, the integer value of the OID is generated and then converted to a string for use in caching the object. In one embodiment, objects are not marked for deletion from the cache until a client calls a remove method. In one embodiment, object references in the cache include a reference to an exported object. In one embodiment, unexport of the exported object is performed by a post-invoke mechanism of the bridge mechanism after the remove method has completed.

Abstract: System and method for bridging between inter-object communication interfaces, such as RMI and IIOP, may include in one embodiment a bridge mechanism that maintains a cache of reference objects. The key used for hashing in the cache may be based on the object identifier (OID) of the reference objects. In one embodiment, the integer value of the OID is generated and then converted to a string for use in caching the object. In one embodiment, objects are not marked for deletion from the cache until a client calls a remove method. In one embodiment, object references in the cache include a reference to an exported object. In one embodiment, unexport of the exported object is performed by a post-invoke mechanism of the bridge mechanism after the remove method has completed.