Bugs item #666150, was opened at 2003-01-11 11:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=666150&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: Cannot use discover for a HA-JNDI for another partition Initial Comment: If a JBoss service wants to lookup another service that is reference in the HA-JNDI service running in another HA-Partition, automatic discovery cannot be used and the only way to lookup this service is by using an explicit PROVIDER_URL string. Currently, when PROVIDER_URL is not specified, the NamingContext will try to use the local server if available or do a discoverServer otherwise, independently of any JNP_PARTITION_NAME parameter that could have been specified in the naming properties. The source complain can be found here (as well as a start of resolution): http://www.jboss.org/modules.php? op=modload&name=phpBB_14&file=index&action=viewt opic&topic=26920&1 Work in progress. The fixed solution will most probably keep a table of (partition name => locally available HA- JNDI service) so that if the HA-JNDI service also runs locally, no network broadcast is necessary. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=666150&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
