Why I'm not moving to Leopard

Although I've been looking forward to OS X Leopard for some time now, I just can't make the switch yet. As it turns out, there's one major hurdle to be overcome before Leopard is an option for developers of Java EE 5 applications to be deployed on Glassfish. Here's the problem:

Glassfish encounters an exception that prevents domain startup when connected to the internet via Wireless, not connected at all, or in any other way not connected by the ethernet port (Stack trace below). If, however, I'm connected via the ethernet port, everything is okay. I develop applications to deploy in Glassfish, but I can't limit my development to when I'm tied down by the ethernet cable. So until there's a solution, I'm sticking with Tiger.

Anyone with a solution, please let me know. I haven't seen anything like this since fixing PCs with strange APIPA problems...

Full Exception:

[#|2007-10-29T15:28:48.086-0400|SEVERE|sun-appserver9.1|
  javax.enterprise.system.core|
  _ThreadID=10;
  _ThreadName=main;com.sun.enterprise.admin.server.core.JmxConnectorLifecycle@328cbf;
    com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL
    [rmi://169.254.161.207:8686/management/rmi-jmx-connector]:
      javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException:
      Connection refused to host: 169.254.161.207; nested exception is:
      java.net.ConnectException: Operation timed out
    ];
  _RequestID=69db80be-8146-46bb-a879-157fedee2f87;|
  Service com.sun.enterprise.admin.server.core.JmxConnectorLifecycle@328cbf cannot be started!:
  com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL
  [rmi://169.254.161.207:8686/management/rmi-jmx-connector]:
    javax.naming.ServiceUnavailableException
    [Root exception is java.rmi.ConnectException:
      Connection refused to host: 169.254.161.207; nested exception is:
      java.net.ConnectException: Operation timed out
    ]|
#]