Bugs item #666154, was opened at 2003-01-11 11:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=666154&group_id=22866
Category: Clustering Group: v3.0 Rabbit Hole >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Sacha Labourey (slaboure) Assigned to: Sacha Labourey (slaboure) Summary: HA-Home not refreshed in JNDI Initial Comment: When a clustered container starts, it creates its home proxy and binds it in JNDI. In the clustered case, this proxy contains: - the list of currently available target containers - the version id used to keep track of the evolution of the cluster topology. The hypothesis that was made at first when coding that, is that the JNDI server do *not* marshall the home proxy that is bound in JNDI so that when the list of target containers is updated, the proxy always contain the last available information (the proxy as a reference to the list). Nevertheless, it appears that the JNDI service *do* serialized content at binding time. Consequently, the target list available in the proxy is the one that was available at container start time. Consequently, when getting the home for the first time, the list may not be up-to-date anymore. This has two important consequences: 1) homes that are used only once may always make invocations against the same set of nodes 2) (more important) when the list of target contains a proxy to a *dead* node, when the clustered proxy is unserialized by RMI, the RMI subsystem attempts to contact that node (!!). If the instance is simply dead, that's ok because it will quickly receive an answer from the target OS (port not open), but if the *host* is not reachable (not only the service), then the socket will have to wait on TCP timeout which may be quite long!!! Work in progress. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=666154&group_id=22866 ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
