Menu
▾
▴
[JBoss-dev] [ jboss-Bugs-632328 ] Typos in JBoss Clustering Manual
|
From: <no...@so...> - 2002-11-01 23:00:18
|
Bugs item #632328, was opened at 2002-11-01 17:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=632328&group_id=22866 Category: JBossDoc Group: v3.0 Rabbit Hole Status: Open Resolution: None >Priority: 3 Submitted By: Fred Hartman (fredh666) Assigned to: Nobody/Anonymous (nobody) Summary: Typos in JBoss Clustering Manual Initial Comment: The following are some typos in Edition 2 Date: 2002-09-27, 12:22:36 PM 1. Page 12 "Load balancing is a mean to obtain better performance by dispatching incoming requests to different servers." "Load balancing is a means to obtain better performance by dispatching incoming requests to different servers." 2. Page 14 "JBoss currently provides full clustering support for stateless session beans, stateful session beans entity beans and JNDI, and partial support for JMS and message driven beans." "JBoss currently provides full clustering support for stateless session beans, stateful session beans, entity beans and JNDI, and partial support for JMS and message driven beans." 3. Page 21 "A Channel is a mean by which a node can join a group of other nodes and exchange reliable messages in unicast or multicast." "A Channel is a means by which a node can join a group of other nodes and exchange reliable messages in unicast or multicast." 4. Page 25 Figure 4-1, Page 26 Figure 4-2 and Page 32 Figure 5-2 name="JBOSS-SYSTEM:service=HAJNDI" name="jboss:service=HAJNDI" is in cluster-service.xml 5. Page 27 "If a binding is only made available on a few nodes on the cluster (for example because a bean is only deployed on a small subset of nodes in the cluster), the probability to lookup a HA-JNDI server that do not owns this binding is higher and the lookup will need to be forwarded to all nodes in the cluster." "If a binding is only made available on a few nodes in the cluster (for example because a bean is only deployed on a small subset of nodes in the cluster), the probability to lookup a HA-JNDI server that does not own this binding is higher and the lookup will need to be forwarded to all nodes in the cluster." 6. Page 29 "But in this case, the downloaded smart stub does not know how to fail-over and does not update its view of the cluster (it simply ignore the notion of cluster)." "But in this case, the downloaded smart stub does not know how to fail-over and does not update its view of the cluster (it simply ignores the notion of cluster)." 7. Page 30 "While it is possible to split the beans on different nodes (B1 and B2 on Node 1 and 2 and B3 on node 2 and 3 for example), this may have a serious, negative performance impact." 8. Page 33 Figure 5-3 <clustered> tag is missing from the example. 9. Page 34 "[>= 3.1 only]" "[>= 3.0.1 only]" there is no CVS tag for 3.1, but there is for 3.0.1. 10. Page 36 "JBoss ≥3.2" "JBoss ≥3.0.2" there is no CVS tag for 3.2, but there is for 3.0.2. 11. Page 36 "the policy will re-elect a target node only if the currently elected node is no more available." "the policy will re-elect a target node only if the currently elected node is no longer available." 12. Page 37 two times "JBoss 3.2 (and upper)" "JBoss 3.0.2 (and greater)" there is no CVS tag for 3.2, but there is for 3.0.2. 13. Page 37 Proxy Ffamily Proxy Family 14. Page 37 "Such structure can also contain some arbitrary information stored by the proxies themselves or their associated load-balancing policy." "This structure can also contain some arbitrary information stored by the proxies themselves or their associated load-balancing policy." 15. Page 37 "Thus each proxy (home or remote) has a mean to share information with other proxies of the same family." "Thus each proxy (home or remote) has a means to share information with other proxies of the same family." 16. Page 38 "HTTP session replication is used to replicate the state associated with your web clients on other nodes of a cluster Thus, in the event one of your node crashes, another node in the cluster will be able to recover." "HTTP session replication is used to replicate the state associated with your web clients on other nodes of a cluster. Thus, in the event one of your nodes crashes, another node in the cluster will be able to recover." 17. Page 38 "State replication is directly handled by JBoss whereas load balancing of invocations needs an additional software or hardware." "Load-balancer State replication is directly handled by JBoss whereas load balancing of invocations requires additional software or hardware." 18. Page 39 "In other situations, loosing a client session is not possible and, in this case, the session state replication is the price to pay." "In other situations, loosing a client session is not acceptable and, in this case, session state replication is the price one has to pay." 19. Page 52 "This allows, for example, a client to determine if its view of a particular set of replicant is up to date." "This allows, for example, a client to determine if its view of a particular set of replicants is up to date." 20. Page 54 "Note that the target object no more needs to be a exported through RMI!" "Note that the target object no longer needs to be a exported through RMI!" Cheers, Fred ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=632328&group_id=22866 |