Receiver file channel giving http 500 error.

[manemahesh]

Hi

My scenario is IDOC to File and my receiver file adapter is showing below error.

I reprocessed the message but still messages are giving the same error and falling in system error queue in RWB.

Below is the error.

Transmitting the message to endpoint http://TREPRDABC:8002/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Internal Server Error.

Please help to get it resovled.

Also i have attached screenshot.

[Former Member · Accepted solution]

Hi Mahesh,

Http code : 500 error normally occurs whenever cache is full. I guess you java cache must be full. So please perform cache refresh.

For cache refresh, kindly refer to the below link:

http://sapbasisanswers.blogspot.in/2014/01/sap-pi-how-to-refresh-java-cache.html

Kind Regards,

Souvik

[manemahesh · Accepted solution]

Hi All,

The error which i was facing got resolved by adding extra tablespace to  XI database tablespace.

As XI database tablespace was full i was facing below error.

Error:-Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Internal Server Error.

You can goto tcode db02 and check tablespace overview and if it is full add extra tablespace by your basis person and then retry messages stuck in XI.

[pvishnuvardan_reddy · Accepted solution]

Hi Mahesh,

Glad that your issue has resolved and thanks for letting us know.

Can you please close this thread discussion which would help other SCN members.

Regards

Vishnu

[former_member183908 · Accepted solution]

cool finally issue got resolved.I wonder how come the table space full? does your PI environment does not enable background jobs which will archive message periodically.Why don't you recommend this option to your basis team if they already did not do.also if you have solution manager in your landscape please enable early watch reports which will give complete picture about the system,may be if you are POC of PI you can receive those alerts which notifies the DB space etc....

Thanks

[iaki_vila]

Hi Mahesh,

Go to SICF transaction a check if it is active:

Also, test the service and check if the port is 8000 instead of 8002 as you have in your audit log.

That port is usually configurable in the transaction sm59 transaction in the connection SAPISU_XID. Please, don't change this parameter without consulting your basis team first.

Regards.

[manemahesh]

Hi Inaki,

Http port is  8002 only and its correct.

Also integration engine service is also activated.

[former_member183908]

any recent changes to the PI server like applying patches or upgrading etc......

Thanks

[manemahesh]

Hi Pavan,

No any upgrade has done.

[former_member183908]

okay can you please check the Pipe line URL in the RWB--->Integration Engine are same...if the issue still persists ask your basis team to re run the post installation steps

I bet you are facing this issue not in PROD.

Thanks

[former_member183908]

also please check whether the service users in PI which help to communicate between runtime components were not locked and they are valid.

Thanks

[Harish]

Hi Mahesh,

Please check the below threat

http://scn.sap.com/thread/1559146

It seems you need receiver SOAP adapter instead of file adapter. File adapter can not handle the response.

regards,

Harish

[manemahesh]

Hi

Actually as its IDOC to File Scenario message is showing put in send queue and when this idoc is getting into xi engine URL at that time it it showing the error.

Its not error at recevier file channel.

It is while coming the IDOC in integration engine because in recevier channel it shows messages successfully put in receive queue.

So please help what could be the cause of this http 500 while idoc is getting trasmitted to xi engine URL.

[pvishnuvardan_reddy]

Hi Mahesh,

Can you please elaborate a little more or share screen shots of the issue, since this is a IDOC to File scenario, and for sender IDOC communications, we don't need a Sender Agreement or the message goes to RWB. Then, how can you get the error at sender channel.

Regards

Vishnu

[manemahesh]

Hi

Screenshot is shared in first post.

Yes you are correct that IDOC to file would not have sender channel i am not saying its sender channel but its send queue.

PFA screenshot to get more on it.

[pvishnuvardan_reddy]

Hi Mahesh,

Can you please check the below thread.

Let us know if you struck anywhere.

Regards

Vishnu