Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #5666 [SOAP] Invalid entities in WSDL documentation prevents SOAP communication
    Actions
    Infos
    #5666
    Laurent Delaigue (ldelaigue)
    2013-12-03 15:39
    2013-11-29 17:08
    5784
    Details
    [SOAP] Invalid entities in WSDL documentation prevents SOAP communication
    I'm having an issue with Tuleap 6.7.99.16 (probably had it before but didn't detect it):

    I get the following error when communicating via SOAP with tuleap:
    AxisFault
    faultCode: WSDL
    faultSubcode:
    faultString: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://*****.fr/soap/codendi.wsdl.php?wsdl' : failed to load external entity "

    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}stackTrace:SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://*****.fr/soap/codendi.wsdl.php?wsdl' : failed to load external entity "
    https://*****.fr/soap/codendi.wsdl.php?wsdl

    Maybe comments have been added in the WSDL, and since these comments contain html entities, they should be enclosed between <![CDATA[...]]>?

    This prevents the eclipse connector from working.
    API
    6.7
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2013-12-03
    Attachments
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Laurent Delaigue (ldelaigue)2013-12-03 15:39
    I close the ticket since it seems solved after we fixed our hosts file.
    • Status changed from New to Closed
    • Close date set to 2013-12-03
    User avatar
    Laurent Delaigue (ldelaigue)2013-12-02 16:45
    Hi,
    I investigated a bit, it looks like we are using a TLS certificate that is "self-signed". When I try and wget the WSDL URL, I get an ERROR due to this certificate.
    It seems quite likely that the SOAP problem we meet is due to the same problem.
    Are you aware of a workaround on Tuleap servers with a self-signed SSL certificate?
    User avatar
    Laurent Delaigue (ldelaigue)2013-12-02 13:59
    The generated wsdl is the same than on tuleap.net (except the server names of course). So the problem is probably elsewhere...
    The problem seems to be with a network configuration of our machine. here is an extract of error_log (I anonymized the name of my company):
    [Mon Dec 02 09:30:49 2013] [error] [client 192.168.30.113] PHP Warning: SoapServer::SoapServer(): php_network_getaddresses: getaddrinfo failed: Name or service not known in /usr/share/codendi/src/www/soap/index.php on line 27, referer: https://tuleapappli.****.fr/
    [Mon Dec 02 09:30:49 2013] [error] [client 192.168.30.113] PHP Warning: SoapServer::SoapServer(https://tuleapappli.****.fr/soap/codendi.wsdl.php?wsdl): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /usr/share/codendi/src/www/soap/index.php on line 27, referer: https://tuleapappli.****.fr/
    [Mon Dec 02 09:30:49 2013] [error] [client 192.168.30.113] PHP Warning: SoapServer::SoapServer(): I/O warning : failed to load external entity "https://tuleapappli.****.fr/soap/codendi.wsdl.php?wsdl" in /usr/share/codendi/src/www/soap/index.php on line 27, referer: https://tuleapappli.****.fr/
    [Mon Dec 02 09:30:49 2013] [error] [client 192.168.30.113] PHP Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://tuleapappli.****.fr/soap/codendi.wsdl.php?wsdl' : failed to load external entity "https://tuleapappli.****.fr/soap/codendi.wsdl.php?wsdl"\n in /usr/share/codendi/src/www/soap/index.php on line 27, referer: https://tuleapappli.****.fr/
    User avatar
    Nicolas Terray (nterray)2013-12-02 12:36
    Could you please attach the generated wsdl? It will help us to investigate the issue.
    User avatar
    Laurent Delaigue (ldelaigue)2013-12-02 09:41
    Yes, the problem only occurs in our tuleap instance.
    When we click on the link "Tuleap provides a SOAP API" at the bottom of the home page, we get an error page:

    <SOAP-ENV:Envelope><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>WSDL</faultcode><faultstring>SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://tuleapappli.obeo.fr/soap/codendi.wsdl.php?wsdl' : failed to load external entity "https://tuleapappli.obeo.fr/soap/codendi.wsdl.php?wsdl"
    </faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

    So I think we have set-up something wrong, but I've no idea what!
    Where can I look?
    User avatar
    Manuel Vacelet (vaceletm)2013-11-29 18:29
    I pretty sure it's more a problem with the data themselves, not the WSDL.
    Did you try with another installation (like tuleap.net for instance) ?