cancel
Showing results for 
Search instead for 
Did you mean: 

TCP Gateway - 500 Internal Server Error

Former Member
0 Kudos

Hi,

Scenario is File - XI - SOAP.

It is successful in sxmb_moni. RWB Message monitoring shows system error.

I tried getting the trace from TCPGateway. It is showing:

Response ====

HTTP/1.1 500 Internal Server Error

Any suggestion why this could happen.

Thanks,

Prateek

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi prateek,

this error may have occured due to some internal problem in j2ee engine.

u may check sap note 807000 if it helps.

regards,

latika.

prateek
Active Contributor
0 Kudos

I already had a look at the note u provided. Here is the trace description

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>No handler for body element</faultstring><detail><detail><transportUri>http://localhost:9998/MyCompany/FunctionName</transportUri><soapAction/><element>IDOC</element></detail></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

Thanks,

Prateek

udo_martens
Active Contributor
0 Kudos

Hi Prateek,

your SOAP receiving application cant handle the request. Take a SOAP request tool (f e SoapUI) and test the webService. If you have success, compare the message with msg outgoing from PI.

Regards, Udo

Former Member
0 Kudos

hi prateek,

there mite b a problem in calling the webservice from XI. as ur msg is successfull on IE but failin on AE.

r u sure there is no problem in accessing ur webservice like network access/authorization problem or something like that.

regards,

latika.

prateek
Active Contributor
0 Kudos

<i>r u sure there is no problem in accessing ur webservice like network access/authorization problem or something like that.</i>

That is where the problem lies. We are trying to connect to the webservice which lies outside our network and across the firewall. When we are trying to test the scenario, we got stuck at receiver SOAP.

Could any1 suggest me ways to test whether webservice is accessible from our network? Directly pasting the url in browser is saying page cannot be displayed

Thanks,

Prateek

prateek
Active Contributor
0 Kudos

Hi Udo,

The webservice is in the client s network. Should some SOAP tool be provided to them to test the webservice? We are still not sure whether the webservice is accessible in our network or not.

Thanks,

Prateek

udo_martens
Active Contributor
0 Kudos

Hi Prateek,

it is. Who else wrote: "No handler for body element" ?

Regards, Udo

Former Member
0 Kudos

Hi Prateek,

See if your able to access the webservice when you give the SOAP Address in your IE.

Cheers,

Abhy

prateek
Active Contributor
0 Kudos

Directly pasting the url in browser is saying "page cannot be displayed"

An update: We have another scenario SOAP - XI - File Async. This was also not working earlier. But now its working. So i think there are no more firewall and network issues.

Thanks,

Prateek

Former Member
0 Kudos

>>Directly pasting the url in browser is saying "page cannot be displayed"

this gives me an idea that there is something wrong with the webserver URL itself,may be server name,port etc.

also can you please paste the trace file you got from TCPGateway.

to me it looks like the URL address is wrong somewhere.

Thanx

Aamir

prateek
Active Contributor
0 Kudos

There are 2 parts of the trace

1. Request

2. Response

Request part shows the complete payload and it is OK.

Response part:

==== Response ====

HTTP/1.1 500 Internal Server Error

Date: Wed, 21 Nov 2007 08:53:39 GMT

Server: Apache Coyote/1.0

Content-Type: text/xml; charset=utf-8

Content-Length: 466

Connection: close

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>No handler for body element</faultstring><detail><detail><transportUri>http://localhost:9998/MyCompany/FunctionName</transportUri><soapAction/><element>IDOC</element></detail></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

Thanks,

Prateek

Former Member
0 Kudos

request is OK means PI is atleast able to reach the web server hence you can negate the issues with Firewall,the issue is in getting the response from webserver,as you are unable to load the URL from the browser as well,its an issue with their system,try to get in touch with the external partner guys and see if they are able to open the URL at their end

Thanx

Aamir

Message was edited by:

Aamir Suhail

Former Member
0 Kudos

Hi

If the request id OK, then i feel there is some problem from the Web Service side only..

Your scenario seems fine.

Thanks

prateek
Active Contributor
0 Kudos

Hi Aamir,

They are able to open the URL at their browsers.

Thanks,

Prateek

prateek
Active Contributor
0 Kudos

<i>your SOAP receiving application cant handle the request. Take a SOAP request tool (f e SoapUI) and test the webService. If you have success, compare the message with msg outgoing from PI.</i>

The webservice was tested with SoapUI. It is able to send request and receive response properly. I tried comparing the message. The only difference i found is the location of namespace:

PI Trace:

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body><ns0:IDOC xmlns:ns0='http://myComp/delvry02' BEGIN=''><ns0:EDI_DC40 ....................

SoapUI Trace:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://myComp/delvry02">

<soapenv:Header/>

<soapenv:Body>

<ns0:IDOC BEGIN="1">

But i think this is created by PI itself and should be proper.

Thanks,

Prateek

prateek
Active Contributor
0 Kudos

Problem Solved Guys... It was the SOAP Action

The receiver informed ur recently that they were expecting SOAP Action in the header.

Thanks All,

Prateek

Answers (1)

Answers (1)

Shabarish_Nair
Active Contributor
0 Kudos

is the SOAP call sync ? In that case if you havnt handled the response, you can expect such a behaviour.

prateek
Active Contributor
0 Kudos

It is File to SOAP Async scenario.

There couldnt be a possibility to made it sync from the receiver SOAP adapter. And even the receiver has not received any data from PI.

Thanks,

Prateek