Received HTTP response code 500 : Internal Server Error using connection Fi

[Former Member]

Hi everybody,

I have configured a file-webservice-file without BPM scenario...as explained by Bhavesh in the following thread:

I have used a soap adapter (for webservice) instead of rfc .My input file sends the date as request message and gets the sales order details from the webservice and then creates a file at my sender side.

I monitored the channels in the Runtime work bench and the error is in the sender ftp channel.The other 2 channel status is "not used" in RWB.

1 sender ftp channel

1 receiver soap channel

1 receiver ftp channel.

2009-12-16 15:02:00 Information Send binary file "b.xml" from ftp server "10.58.201.122:/", size 194 bytes with QoS EO

2009-12-16 15:02:00 Information MP: entering1

2009-12-16 15:02:00 Information MP: processing local module localejbs/AF_Modules/RequestResponseBean

2009-12-16 15:02:00 Information RRB: entering RequestResponseBean

2009-12-16 15:02:00 Information RRB: suspending the transaction

2009-12-16 15:02:00 Information RRB: passing through ...

2009-12-16 15:02:00 Information RRB: leaving RequestResponseBean

2009-12-16 15:02:00 Information MP: processing local module localejbs/CallSapAdapter

2009-12-16 15:02:00 Information The application tries to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.

2009-12-16 15:02:00 Information Trying to put the message into the call queue.

2009-12-16 15:02:00 Information Message successfully put into the queue.

2009-12-16 15:02:00 Information The message was successfully retrieved from the call queue.

2009-12-16 15:02:00 Information The message status was set to DLNG.

2009-12-16 15:02:02 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Internal Server Error using connection File_http://sap.com/xi/XI/System.

2009-12-16 15:02:02 Error The message status was set to FAIL.

Please help.

thanks a lot

Ramya

[former_member187339 · Accepted solution]

Hi Ramya,

Seems to be a problem with the webservice call.. Try doing this:

Remove the requestresponse bean and using a normal file adapter (with QoS as bE) send message to receiver webservice and see whether you can get any further information...

if you are successfull in invoking the webservice using Receiver SOAP Channel then you will get back a response and it may fail in SXMB_MONI (because file adapter will not be able to handle the response back).. but by doing this we can be sure that there is no problem on the SOAP end

Regards

Suraj

[Former Member · Accepted solution]

Hi Suraj,

You are right.The webservice is not invoked.I see the same error in the sender channel and the receiver soap channel status is "never used".

2009-12-16 15:52:25 Information Send binary file "b.xml" from ftp server "10.58.201.122:/", size 194 bytes with QoS BE

2009-12-16 15:52:25 Information MP: entering1

2009-12-16 15:52:25 Information MP: processing local module localejbs/CallSapAdapter

2009-12-16 15:52:25 Information The application tries to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.

2009-12-16 15:52:25 Information Trying to put the message into the call queue.

2009-12-16 15:52:25 Information Message successfully put into the queue.

2009-12-16 15:52:25 Information The message was successfully retrieved from the call queue.

2009-12-16 15:52:25 Information The message status was set to DLNG.

2009-12-16 15:52:27 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Internal Server Error using connection File_http://sap.com/xi/XI/System.

2009-12-16 15:52:27 Error The message status was set to FAIL.

what can I do about this?

thanks,

Ramya

[Former Member · Accepted solution]

I am not sure if this helps, but the HTTP adapter of XI throws an error 500 if the content type is not supported by it, e.g. if you send content-type multipart to it. The error messages could be clearer in this case. Sometimes you will only find out the reason by checking the XI logs, or even worse, the ABAP implementation of the HTTP adapter, for example.

The SOAP adapter also behaves like this (not supported content-type => error 500).

CSY

[former_member187339 · Accepted solution]

Hi Ramya,

Refer this thread and check the reply of Siva Maranani

If the service is stopped activate and restart the adapter engine.. then re-test

Regards

Suraj