Home >> All >> org >> jboss >> ha

•	org.jboss.ha.framework.* (39)	•	org.jboss.ha.hasessionstate.* (8)	•	org.jboss.ha.httpsession.* (13)
•	org.jboss.ha.jmx.* (6)	•	org.jboss.ha.jndi.* (4)	•	org.jboss.ha.singleton.* (7)

Package Samples:

• org.jboss.ha.framework.interfaces
• org.jboss.ha.framework.server
• org.jboss.ha.framework.test
• org.jboss.ha.hasessionstate.interfaces
• org.jboss.ha.hasessionstate.server
• org.jboss.ha.httpsession.beanimpl.ejb
• org.jboss.ha.httpsession.beanimpl.interfaces
• org.jboss.ha.httpsession.interfaces
• org.jboss.ha.httpsession.server
• org.jboss.ha.jndi
• org.jboss.ha.jmx.examples
• org.jboss.ha.singleton.examples
• org.jboss.ha.framework.server.util
• org.jboss.ha.jmx
• org.jboss.ha.singleton

Classes:

• TopologyMonitorService: A cluster parition membership monitor. It can be used to view how the nodes in a cluster are seeing the topology change using either email or a centralized log server. To use this to send email on change notifications use the following log4j.xml fragments: You can also have this service notify another MBean of the change to perform arbitrary checks by specifying the MBean name as the TriggerServiceName attribute value. This MBean must have an operation with the following signature: param: removed ArrayList of nodes that were removed param: added ArrayList of nodes that were added param: members ...
• DistributedState: DistributedState is a service on top of HAPartition that provides a cluster-wide distributed state. The DistributedState (DS) service provides a tuple map. Thus, any service, application, container, ... can request its own DS "private space" by working* in its own category (a string name). You work in a category like a Dictionary: you set values by key within a category. Each time a value is added/modified/removed, the modification is made cluster-wide, on all other nodes. Reading values is always made locally (no network access!) Objects can also subscribes to DS events to be notified when some ...
• HARMIProxyCallback: DistributedState is a service on top of HAPartition that provides a cluster-wide distributed state. The DistributedState (DS) service provides a tuple map. Thus, any service, application, container, ... can request its own DS "private space" by working* in its own category (a string name). You work in a category like a Dictionary: you set values by key within a category. Each time a value is added/modified/removed, the modification is made cluster-wide, on all other nodes. Reading values is always made locally (no network access!) Objects can also subscribes to DS events to be notified when some ...
• HANamingServiceMBean: * HA-JNDI service that provides JNDI services in a clustered way. * Bindings are replicated cluster-wide. * Lookups are: * - first resolved locally in the cluster-wide tree * - if not available, resolved in the local underlying JNDI tree * - if not available, the query is broadcast on the cluster and each node determines * if it has one in its local JNDI tree * * The HA-JNDI service also provides an automatic-discovery feature that allow clients * to resolve the service through multicast. * * @author Bill Burke * @author Sacha Labourey * @version $Revision: 1.10.4.5 $ * * Revisions:
• FirstAvailableIdenticalAllProxies: LoadBalancingPolicy implementation that always favor the first available target i.e. no load balancing occurs. Nevertheless, the first target is randomly selected. This does not mean that fail-over will not occur if the first member in the list dies. In this case, fail-over will occur, and a new target will become the first member and invocation will continously be invoked on the same new target until its death. Each proxy using this policy will *not* elect its own prefered target: the target *is* shared with all proxies that belong to the same family (for a different behaviour please take a look ...
• FirstAvailable: LoadBalancingPolicy implementation that always favor the first available target i.e. no load balancing occurs. Nevertheless, the first target is randomly selected. This does not mean that fail-over will not occur if the first member in the list dies. In this case, fail-over will occur, and a new target will become the first member and invocation will continously be invoked on the same new target until its death. Each proxy using this policy will elect its own prefered target: the target is not shared accross the proxy family (for this behaviour please take a look at FirstAvailableIdenticalAllP ...
• HAServiceMBeanSupport: Management Bean for an HA-Service. Provides a convenient common base for cluster symmetric MBeans. This class is also a user transparent extension of the standard NotificationBroadcasterSupport to a clustered environment. Listeners register with their local broadcaster. Invoking sendNotification() on any broadcaster, will notify all listeners in the same cluster partition. TODO: The performance can be further optimized by avoiding broadcast messages when remote listener nodes are not interested (e.g. have no local subscribers) or by iterating locally over filters or remote listeners.
• DistributedTimedCachePolicy: An implementation of a timed cache. This is a cache whose entries have a limited lifetime with the ability to refresh their lifetime. The entries managed by the cache implement the TimedCachePolicy.TimedEntry interface. If an object inserted into the cache does not implement this interface, it will be wrapped in a DefaultTimedEntry and will expire without the possibility of refresh after getDefaultLifetime() seconds. This is a lazy cache policy in that objects are not checked for expiration until they are accessed.
• SerializableHttpSession: Tag interface to make HttpSession serializable. Used to store the clustered HttpSession in an entity bean. Furthermore, it adds an areAttributesModified method used by the entity bean to determine if the content attributes have been modified. WARNING: the areAttributesModified method should not compare the creation and last access time but only the attributes and other specific values. Otherwise the state will be considered as changed for every request (which will cause to much cluster traffic.
• FamilyClusterInfo: Maintain information for a given proxy family. Proxies can statically reference objects implementing this interface: only the content will change as the cluster topology changes, not the FamilyClusterInfo object itself. Proxies or LoadBalancing policy implementations can use the cursor and object attribute to store arbitrary data that is then shared accross all proxies belonging to the same family. Initial access to this object is done through the ClusteringTargetsRepository singleton.
• HASingletonMBean: HA-Singleton interface. Only one mbean is active at any point of time cluster-wide. The abstract service provides a simple way for a concrete mbeans to detect whether or not it is the active one in the cluster. Concrete mbeans would usually do activities like regular clean up of database tables or saving statistics about cluster usage.
• GenericClusteringException: Generic clustering exception that can be used to replace other exceptions that occur on the server. Thus, only this class is needed on the client side and some specific server side exceptions class are not needed on the client side (such as JMX exceptions for example). Furhtermore, it has support for "COMPLETED" status flag a la IIOP.
• HAManagementService: This class enables a client to get a management view (JSR-77) on a JBoss Cluster. It contains the entire logic to map all the {@link org.jboss.management.j2ee.J2EEManagedObject Managed Object (MO) of all the nodes in the cluster to one MO. The same applies to State Management and Performance Statistics.
• ClusterNode: Replacement for a JG IpAddress that doesn't base its representation on the JG address but on the computed node name added to the IPAddress instead. This is to avoid any problem in the cluster as some nodes may interpret a node name differently (IP resolution, name case, FQDN or host name, etc.)
• ClusteringTargetsRepository: JVM singleton that associates a list of targets (+ other info) contained in a FamilyClusterInfo to a proxy family. For example All remote proxies for a given EJB in a given cluster are part of the same proxy family. Note that home and remote for a same EJB form *2* proxy families.
• HANotificationBroadcasterClientExample: This MBean is an example that shows how to delegate notification services to a HANotificationBroadcaster. Use the sendNotiication() operation to trigger new clustered notifications. Observe the status of each instance of this mbean in the participating cluster partition nodes.
• TreeHead: This class extends the JNP JNDI implementation. binds and unbinds will be distributed to all members of the cluster that are running HAJNDI. lookups will look for Names in HAJNDI then delegate to the local InitialContext This class is fully serializable for GET_STATE
• HANotificationBroadcasterExample: This MBean is an example showing how to extend a cluster notification broadcaster Use the sendNotiication() operation to trigger new clustered notifications. Observe the status of each instance of this mbean in the participating cluster partition nodes.
• HARMIServer: When using HA-RMI, the RMI communication end-point on the server-side is an instance of this class. All invocations are sent through this servant that will route the call to the appropriate object and call the appropriate Java method.
• LoadBalancePolicy: Base interface for load-balancing policies. It is possible to implement many different load-balancing policies by implementing this simple interface and using it in the different clustered services (home interface of SLSB for example)
• HAJNDI: This class extends the JNP JNDI implementation. binds and unbinds will be distributed to all members of the cluster that are running HAJNDI. lookups will look for Names in HAJNDI then delegate to the local InitialContext

Home | Contact Us | Privacy Policy | Terms of Service