Patches item #758213, was opened at 2003-06-20 16:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=758213&group_id=22866
Category: JBossMQ Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Ken Seymour (kenseymour) Assigned to: Nobody/Anonymous (nobody) Summary: jbossmq dual nic patch Initial Comment: We are using jboss-3.2.0 for JMS only. All of our clients are standalone java applications. This patch fixes a problem you might have if you are a jboss JMS client on a machine that has two active TCP/IP network interfaces (two nics). The jboss JMS client code might use the wrong IP address for the client end of the connection to the JMS server, causing errors when jboss tries to ping (or is it pong?) back to the client. With this patch, if you specify a host name or ip address as the system property "ws.jms.localhost", it will force the use of that address instead of the possibly incorrect address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=758213&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
