Axis2
  1. Axis2
  2. AXIS2-2990

WSDL port address is not correctly generated for machines having multiple network interfaces

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 1.2
    • Fix Version/s: None
    • Component/s: wsdl
    • Labels:
      None
    • Environment:
      Windows

      Description

      WSDL portAddress is filled with machines IP address. The code to get the IP address org.apache.axis2.transport.http.sever.HTTPUtils.getIpAddress() always takes the first available network interfaces ip address.

      This may not work in machine which has vmvare installed, or machines having multiple network interfaces or just a laptop which has wireless and wired lan. I believe that Correct way to do that it, is to use the hostName and resolve it to ipAddress.

        Issue Links

          Activity

          Show
          Nandana Mihindukulasooriya added a comment - http://svn.apache.org/viewvc?view=rev&revision=686828
          Hide
          Keith Godwin Chapman added a comment -

          No This was not introduces after Sankas change. I've had problems when running axis2 on machines with VMWare too (even before sankas change)

          Show
          Keith Godwin Chapman added a comment - No This was not introduces after Sankas change. I've had problems when running axis2 on machines with VMWare too (even before sankas change)
          Hide
          Deepal Jayasinghe added a comment -

          Hi Sanka,
          Seems like this is a problem arise due to your recent changes , so please have a look at and see whether you have a quick fix.

          Thank you!
          Deepal

          Show
          Deepal Jayasinghe added a comment - Hi Sanka, Seems like this is a problem arise due to your recent changes , so please have a look at and see whether you have a quick fix. Thank you! Deepal
          Hide
          Dietmar Gaertner added a comment -

          This issue is not resolved in Axis2 1.4. I have th eoriginal Axis2 1.4 axis2.war deployed in a vanilla Tomcat 6.
          http://localhost:8080/axis2/services/Version?wsdl as well as http://myhost:8080/axis2/services/Version?wsdl
          return:
          ...
          <wsdl:service name="Version">
          <wsdl:port name="VersionHttpSoap11Endpoint" binding="ns:VersionSoap11Binding">
          <soap:address location="http://10.20.125.14:8080/axis2/services/Version.VersionHttpSoap11Endpoint"/>
          </wsdl:port>
          <wsdl:port name="VersionHttpSoap12Endpoint" binding="ns:VersionSoap12Binding">
          <soap12:address location="http://10.20.125.14:8080/axis2/services/Version.VersionHttpSoap12Endpoint"/>
          </wsdl:port>
          <wsdl:port name="VersionHttpEndpoint" binding="ns:VersionHttpBinding">
          <http:address location="http://10.20.125.14:8080/axis2/services/Version.VersionHttpEndpoint"/>
          </wsdl:port>
          </wsdl:service>
          ...
          Regards, Dietmar

          Show
          Dietmar Gaertner added a comment - This issue is not resolved in Axis2 1.4. I have th eoriginal Axis2 1.4 axis2.war deployed in a vanilla Tomcat 6. http://localhost:8080/axis2/services/Version?wsdl as well as http://myhost:8080/axis2/services/Version?wsdl return: ... <wsdl:service name="Version"> <wsdl:port name="VersionHttpSoap11Endpoint" binding="ns:VersionSoap11Binding"> <soap:address location="http://10.20.125.14:8080/axis2/services/Version.VersionHttpSoap11Endpoint"/> </wsdl:port> <wsdl:port name="VersionHttpSoap12Endpoint" binding="ns:VersionSoap12Binding"> <soap12:address location="http://10.20.125.14:8080/axis2/services/Version.VersionHttpSoap12Endpoint"/> </wsdl:port> <wsdl:port name="VersionHttpEndpoint" binding="ns:VersionHttpBinding"> <http:address location="http://10.20.125.14:8080/axis2/services/Version.VersionHttpEndpoint"/> </wsdl:port> </wsdl:service> ... Regards, Dietmar
          Hide
          Deepal Jayasinghe added a comment -

          seems like issues is fixed.

          Thanks
          Deepal

          Show
          Deepal Jayasinghe added a comment - seems like issues is fixed. Thanks Deepal
          Hide
          Davanum Srinivas added a comment -

          Haneef,

          Please Use Axis2 1.3 RC2, don't use hostname, the correct name is picked up from the http header "host1" or "host2"

          thanks,
          dims

          Show
          Davanum Srinivas added a comment - Haneef, Please Use Axis2 1.3 RC2, don't use hostname, the correct name is picked up from the http header "host1" or "host2" thanks, dims
          Hide
          Haneef Ali added a comment -

          Though I haven't tested this, not sure how this will work. Consider the following scenario.

          1) Weblogic with two servers running in host1 and host2.
          2) If i have MyWebapp.war , single war can be deployed in both host1 and host2
          3) axis.war is now deployed in both host1 and host2. Hostname is part of axis.xml. Do you want me to hardcode the hostname. If it is hardcoded, then it breaks the concept of deploying single war in many servers.

          Haneef

          Show
          Haneef Ali added a comment - Though I haven't tested this, not sure how this will work. Consider the following scenario. 1) Weblogic with two servers running in host1 and host2. 2) If i have MyWebapp.war , single war can be deployed in both host1 and host2 3) axis.war is now deployed in both host1 and host2. Hostname is part of axis.xml. Do you want me to hardcode the hostname. If it is hardcoded, then it breaks the concept of deploying single war in many servers. Haneef
          Hide
          Deepal Jayasinghe added a comment -

          Try to use hostname parameter , then you will be able to generate the wsdl with the corrcte host name , then no need to wory abt the IP addresses

          Show
          Deepal Jayasinghe added a comment - Try to use hostname parameter , then you will be able to generate the wsdl with the corrcte host name , then no need to wory abt the IP addresses

            People

            • Assignee:
              Sanka Samaranayake
              Reporter:
              Haneef Ali
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development