Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

That IP and port looks familiar to me.  It looks like some kind of API??   Definitely needs an error rule.

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

Joseph, Thanks for your response. To be honest, I am not sure what you mean by an error rule. We are just trying to allow file attachments to posts through the gateway and are seeing this error. I have a custom JSON setting and it is applied to the XML Manager. Thoughts?

That IP and port looks familiar to me.  It looks like some kind of API??   Definitely needs an error rule.

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

I know I've seen the /echo call before, but cannot recall where exactly.  My brain is telling me I saw it in API logs, but, if that's not what you are doing, maybe it is something else.

What are you using for this integration?   XMLFW, MPG, or other proxy?

Joseph, Thanks for your response. To be honest, I am not sure what you mean by an error rule. We are just trying to allow file attachments to posts through the gateway and are seeing this error. I have a custom JSON setting and it is applied to the XML Manager. Thoughts?

That IP and port looks familiar to me.  It looks like some kind of API??   Definitely needs an error rule.

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

Here is what the consumer sees concerning the error:
{
    "httpCode": "500",
    "httpMessage": "Internal Server Error",
    "moreInformation": "Failed to establish a backside connection"
}

They stated that this took place at  8:58:49 AM EST.

Here is the DataPower log:

8:58:49 AM    xsltmsg            error    278759056    error    172.xxx.xxx.xxx    0x80000001    mpgw (webapi): api-error-response internal error
8:58:49 AM    mpgw            error    278759056            172.xxx.xxx.xxx    0x80e0012b    mpgw (webapi): Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/
8:58:49 AM    mpgw            error    278759056             172.xxx.xxx.xxx    0x80e00626    mpgw (webapi): Error occurred when connecting to URL 'http://127.85.206.251:2444/echo/'

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

Ahh, so it is API Connect. 

I'm surprised that's leaking back to the client.  You may have to ask IBM.  I do remember seeing this at one point in time, but I cannot recall if it was a problem for us.  I don't see it now, but we're up to date on firmware and running API Connect V10.

So, DataPower isn't 5.0.8.7, that's the version of API Connect you are using.  You may have to file a ticket with IBM to find out where you need to be firmware and API Connect version to solve that issue.

Here is what the consumer sees concerning the error:
{
    "httpCode": "500",
    "httpMessage": "Internal Server Error",
    "moreInformation": "Failed to establish a backside connection"
}

They stated that this took place at  8:58:49 AM EST.

Here is the DataPower log:

8:58:49 AM    xsltmsg            error    278759056    error    172.xxx.xxx.xxx    0x80000001    mpgw (webapi): api-error-response internal error
8:58:49 AM    mpgw            error    278759056            172.xxx.xxx.xxx    0x80e0012b    mpgw (webapi): Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/
8:58:49 AM    mpgw            error    278759056             172.xxx.xxx.xxx    0x80e00626    mpgw (webapi): Error occurred when connecting to URL 'http://127.85.206.251:2444/echo/'

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

Joseph,
Thank you for your response. Yes, you are correct in that the version was for API Connect. We are in the process of standing up APIC v10.0.5.2 while we are still operating on v5. The DataPower version is IDG.7.6.0.5. 

Ahh, so it is API Connect. 

I'm surprised that's leaking back to the client.  You may have to ask IBM.  I do remember seeing this at one point in time, but I cannot recall if it was a problem for us.  I don't see it now, but we're up to date on firmware and running API Connect V10.

So, DataPower isn't 5.0.8.7, that's the version of API Connect you are using.  You may have to file a ticket with IBM to find out where you need to be firmware and API Connect version to solve that issue.

Here is what the consumer sees concerning the error:
{
    "httpCode": "500",
    "httpMessage": "Internal Server Error",
    "moreInformation": "Failed to establish a backside connection"
}

They stated that this took place at  8:58:49 AM EST.

Here is the DataPower log:

8:58:49 AM    xsltmsg            error    278759056    error    172.xxx.xxx.xxx    0x80000001    mpgw (webapi): api-error-response internal error
8:58:49 AM    mpgw            error    278759056            172.xxx.xxx.xxx    0x80e0012b    mpgw (webapi): Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/
8:58:49 AM    mpgw            error    278759056             172.xxx.xxx.xxx    0x80e00626    mpgw (webapi): Error occurred when connecting to URL 'http://127.85.206.251:2444/echo/'

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

Joseph,
Thank you for your response. Yes, you are correct in that the version was for API Connect. We are in the process of standing up APIC v10.0.5.2 while we are still operating on v5. The DataPower version is IDG.7.6.0.5. 

Ahh, so it is API Connect. 

I'm surprised that's leaking back to the client.  You may have to ask IBM.  I do remember seeing this at one point in time, but I cannot recall if it was a problem for us.  I don't see it now, but we're up to date on firmware and running API Connect V10.

So, DataPower isn't 5.0.8.7, that's the version of API Connect you are using.  You may have to file a ticket with IBM to find out where you need to be firmware and API Connect version to solve that issue.

Here is what the consumer sees concerning the error:
{
    "httpCode": "500",
    "httpMessage": "Internal Server Error",
    "moreInformation": "Failed to establish a backside connection"
}

They stated that this took place at  8:58:49 AM EST.

Here is the DataPower log:

8:58:49 AM    xsltmsg            error    278759056    error    172.xxx.xxx.xxx    0x80000001    mpgw (webapi): api-error-response internal error
8:58:49 AM    mpgw            error    278759056            172.xxx.xxx.xxx    0x80e0012b    mpgw (webapi): Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/
8:58:49 AM    mpgw            error    278759056             172.xxx.xxx.xxx    0x80e00626    mpgw (webapi): Error occurred when connecting to URL 'http://127.85.206.251:2444/echo/'

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?

DP 7.6 firmware has never been supported by APIC V5 :-)  The 7.6 stream is severals of years out of service.

You will see the similar endpoint used in the V5 Compatibility mode, apigw moves away from that design.

Joseph,
Thank you for your response. Yes, you are correct in that the version was for API Connect. We are in the process of standing up APIC v10.0.5.2 while we are still operating on v5. The DataPower version is IDG.7.6.0.5. 

Ahh, so it is API Connect. 

I'm surprised that's leaking back to the client.  You may have to ask IBM.  I do remember seeing this at one point in time, but I cannot recall if it was a problem for us.  I don't see it now, but we're up to date on firmware and running API Connect V10.

So, DataPower isn't 5.0.8.7, that's the version of API Connect you are using.  You may have to file a ticket with IBM to find out where you need to be firmware and API Connect version to solve that issue.

Here is what the consumer sees concerning the error:
{
    "httpCode": "500",
    "httpMessage": "Internal Server Error",
    "moreInformation": "Failed to establish a backside connection"
}

They stated that this took place at  8:58:49 AM EST.

Here is the DataPower log:

8:58:49 AM    xsltmsg            error    278759056    error    172.xxx.xxx.xxx    0x80000001    mpgw (webapi): api-error-response internal error
8:58:49 AM    mpgw            error    278759056            172.xxx.xxx.xxx    0x80e0012b    mpgw (webapi): Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/
8:58:49 AM    mpgw            error    278759056             172.xxx.xxx.xxx    0x80e00626    mpgw (webapi): Error occurred when connecting to URL 'http://127.85.206.251:2444/echo/'

Hello. In DataPower v5.0.8.7, we have a consumer that is making requests with a large payload. Intermittently, the consumer will see one of the following errors:

{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
or
{ "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to process response headers" }

When looking in the DataPower logs I see:
Backside header ('N/A') failed to parse due to: Failed to establish a backside connection, URL: http://127.85.206.251:2444/echo/

I assume that the IP 127.85.206.251 with the port 2444 is for a loopback call internally?