Bugs item #763952, was opened at 2003-07-01 16:52 Message generated for change (Comment added) made by slaboure You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=763952&group_id=22866
Category: Clustering Group: v3.2 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Weiqing Huang (weiqingh) Assigned to: Sacha Labourey (slaboure) Summary: client HA jndi auto-discovery needs to set ttl for datagram Initial Comment: i am using client auto-discovery of clustered servers by setting provider url to null. the client is in a different subnet than the clustered servers. my client failed to find the cluster. debugging info from the router showed that the ttl of the datagram socket is 1, therefore dropped by the router. i am reading the code of org/jnp/interfaces/NamingContext and found out it's using a DatagramSocket, not a MulticastSocket. there seems to be no way to set ttl for the DatagramSocket. maybe we should use a MulticastSocket instead? ---------------------------------------------------------------------- >Comment By: Sacha Labourey (slaboure) Date: 2003-07-02 18:06 Message: Logged In: YES user_id=95900 Fixed. Can you please try now. In fact, the server side was using multicast, only the client side wasn't which is odd (and shows that the real intent *was* to use multicast, so it is really a bug) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=763952&group_id=22866 ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
