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.
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.
This topic has been locked.
7 replies Latest Post - 2013-03-12T17:52:26Z by SystemAdmin
Pinned topic internal error
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-12T17:52:26Z at 2013-03-12T17:52:26Z by SystemAdmin
GKReddy 2700033KPM119 Posts
Re: internal error2013-03-08T19:57:33Z in response to GKReddyRequest 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.
Re: internal error2013-03-08T20:29:33Z in response to GKReddyin 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)
kenhygh 120000PD1B1430 Posts
SystemAdmin 110000D4XK6772 PostsACCEPTED ANSWER
Re: internal error2013-03-12T17:52:26Z in response to kenhyghkenhygh 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.