bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

Stateless Clustering --> Configuration

Tasks Additional Documentation Attributes

Overview

Use this tab to specify how WebLogic Server replicates stateless session bean instances in a cluster.

Tasks

Using the EJB Deployment Descriptor Editor

Additional Documentation

(Requires an Internet connection.)

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Stateless Bean Is Clusterable | Specify whether the enterprise bean can be deployed from multiple WebLogic Servers in a cluster. Calls to the home stub are load-balanced between the servers on which this bean is deployed, and if a server hosting the the bean is unreachable, the call automatically fails over to another server hosting the bean. Attribute: StatelessBeanIsClusterable | Default: true Configurable: yes Readable: yes Writable: yes
Stateless Bean Load Algorithm | Specify the algorithm to use for load balancing between replicas of the EJB home. If Stateless Bean Load Algorithm is not specified, WebLogic Server uses the algorithm specified by the server element, weblogic.cluster.defaultaLoadAlgorithm. Attribute: StatelessBeanLoadAlgorithm | Valid values: "RoundRobin" "Random" "WeightBased" Readable: yes Writable: yes
Stateless Bean Call Router Class Name | Specify the name of a custom class to use for routing bean method calls. This class must implement weblogic.rmi.extensions.CallRouter(). If specified, an instance of this class is called before each method call. The router cloass has the opportunity to choose a server to route to based on the method parameters. The class returns either a server name or null, which indicates that the current load algorithm should select the server. Attribute: StatelessBeanCallRouterClassName | Configurable: yes Readable: yes Writable: yes
Stateless Bean Methods Are Idempotent | Specify only if the bean is written so that repeated calls to the same method with the same arguments has exactly the same effect as a single call. This allows the failover handler to retry a falied call without knowing whether the call actually completed on the failed server. Setting stateless-bean-methods-are-idempotent makes it possible for the bean stub to recover automatically from any failure as long as another server hosting the bean can be reached. Attribute: StatelessBeanMethodsAreIdempotent | Default: false Configurable: yes Readable: yes Writable: yes