0 Replies Latest reply on Dec 15, 2003 8:20 AM by furykid

    javax.naming.CommunicationException... / Connection refused

    furykid Newbie

      Hi,

      I know there are several posts around which deal with this problem but now strategy worked for our environment:

      We are using binding-management config ( all services are bound to dedicated IP addresses) and this works for production environment aswell as non-loopback local IPs.

      For developer-workstation configuration we would need to bind all services to 127.0.0.1 otherwise a binding config could not be provided

      any suggestions ?
      thx
      furykid