Proxy error - HTTP status code 500

[Former Member]

Hi,

Scenario: Asynchronous Proxy (R/3 4.7) to 3rd Party (JDBC)

We applied patches to JAVA on the XI side to fix a bug, the process worked before the patches. I am now getting an error on R/3 i.e. the data is not reaching XI.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Call Integration Server

  -->

- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">

  <SAP:Context />

  <SAP:Code p1="500" p2="Error during conversion of XI message" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>

  <SAP:Text language="EN">HTTP status code 500 : Error during conversion of XI message</SAP:Text>

  </SAP:ErrorHeader>

Any ideas. Thanks,

Leanne

[Former Member]

Hi Thanks we did a full cache refresh. All is fine now.

[Former Member]

Hi Leanne Fourie

We are having the same issue you have reported in this forum. It looks you have applied some patch as requested by SAP to resolve it. Please kindly share bit more information to resolve our problem.

Many Thanks

Regards

Dhina

[Former Member]

Hi all,

Any hints about this solution?

We are having the same the problem.

Regards.

[Former Member]

Hi Leanne,

There are a couple of SAP notes that describe the solution...... Below are the note numbers.

804124 (The fully qualified host name does make a difference, I have personally seen it)

807000 (especially the point on applying the note 1048692 when the ICM forwards messages to the web dispatcher)

Cheers,

Abhy

[Former Member]

Hi,

SAP requested we implement patches, this sorted out the proxy issue. The message now arrives in XI.

I have now encountered another problem, this process was working prior to the patches being implemented. I noticed that the communication channels now look different, any ideas?

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Inbound Message

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: JDBC Adapter configuration not initialized: null</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Thanks,

Leanne

[nisarkhan_n]

it might be a connection issue....also chck the URL of the IS is proper or not...can u psste that?

[Former Member]

Hi Nisar,

I am not technically minded, how can I check the connection, URL, etc?

I have tested the HTTP connection (PI_CONNECTION) and I get the following message which I understand to be correct.:

~response_line HTTP/1.0 500 Empty HTTP request received

~server_protocol HTTP/1.0

~status_code 500

~status_reason Empty HTTP request received

Thanks,

Leanne

[nisarkhan_n]

this is not an Error status code 500 with empty request received is not an error.

[Former Member]

Hi Leanne.

Check out OSS note : 513703, 916417.

Hope this will help.

Nilesh