Topic
7 replies Latest Post - ‏2013-03-12T17:52:26Z by SystemAdmin
Aprithvi
Aprithvi
52 Posts
ACCEPTED ANSWER

Pinned topic internal error

‏2013-03-08T19:25:05Z |
we have a WS proxy with a static backend. the backend connection is a https webservice . with the test region the connection works and the webservice returns a response. When we change the backend to point to another webservice region we get the following error. the only thing we change is the remote endpoint host.

<env:Fault>
<faultcode>env:Client</faultcode>
<faultstring>Internal Error</faultstring>
</env:Fault>

I dont see any connection or network issues on Datapower. how can I verify if the request reached the server and if it has not where do i see the error message?
Any help on this is greatly appreciated.
Updated on 2013-03-12T17:52:26Z at 2013-03-12T17:52:26Z by SystemAdmin
  • GKReddy
    GKReddy
    119 Posts
    ACCEPTED ANSWER

    Re: internal error

    ‏2013-03-08T19:47:01Z  in response to Aprithvi
    Hi,
    Most of the times when you see internal error from client, it means your request payload is invalid or your URL is incorrect.
    Please try to validate your request to your WSDL and try.
    • GK
    • Aprithvi
      Aprithvi
      52 Posts
      ACCEPTED ANSWER

      Re: internal error

      ‏2013-03-08T19:57:33Z  in response to GKReddy
      Request is correct since we send it to the test WS against the same wsdl and it goes thru. Only when i change the host remote server host I get this message. I changed to debug in the logs and still no error messages. Everything is info or debug. No error messages shown.
    • Aprithvi
      Aprithvi
      52 Posts
      ACCEPTED ANSWER

      Re: internal error

      ‏2013-03-08T20:29:33Z  in response to GKReddy
      in the advanced proxy settings of the WS proxy i changed the Process HTTP Errors to off and now see this in the logs. all the ssl certificates are fine.

      wsgw (Proxy): Failed to establish a backside connection
      Fri Mar 08 2013
      15:24:43 ws-proxy error 1139985 0x80e0012b wsgw (Proxy): Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: https://remote url/uri
      15:24:43 ws-proxy error 1139985 0x80e00626 wsgw (Proxy): Error occurred when connecting to URL 'https://remote url/uri '
      15:24:43 ws-proxy error 1139985 0x80e00640 wsgw (Proxy): HTTP invalid response returned 500 Error, from URL 'https://remote url/uri ' (Method: POST , URI: uri)
      • GKReddy
        GKReddy
        119 Posts
        ACCEPTED ANSWER

        Re: internal error

        ‏2013-03-08T20:48:40Z  in response to Aprithvi
        If the connectivity (tcp test) is good between DP and backend server then I suspect the issue is at the server side.
        • GK
      • kenhygh
        kenhygh
        1336 Posts
        ACCEPTED ANSWER

        Re: internal error

        ‏2013-03-08T21:16:02Z  in response to Aprithvi
        Sorry I responded to a later message and missed this.

        500 was returned from your new backend server. You'll need to talk to the admins of that box to debug.

        Ken
        • SystemAdmin
          SystemAdmin
          6772 Posts
          ACCEPTED ANSWER

          Re: internal error

          ‏2013-03-12T17:52:26Z  in response to kenhygh
          kenhygh is right. We just struggled a bit with this same error. Turned out our WSDL was configured wrong and giving us the wrong backside URL. So moral of the story, if you know your URL is correct, then the issue is with whatever is siting on that URL.
  • kenhygh
    kenhygh
    1336 Posts
    ACCEPTED ANSWER

    Re: internal error

    ‏2013-03-08T19:50:24Z  in response to Aprithvi
    There is always something in the logs for this kind of error. Make sure you're set to 'debug'.

    Ken