cancel
Showing results for 
Search instead for 
Did you mean: 

java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK

sud
Discoverer
0 Kudos

Hi All,

I am receiving an HTTP request into XI and then calls out from XI to a web service. I configured my receiver comm channel as SOAP adapter. But when I am testing the web service call, I got this error message: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK.

I am wondering what could cause that. Any help is highly appreciated.

Audit Log for Message: 620a2700-ff97-11dd-9e21-001185b7794d

Time Stamp Status Description

2009-02-20 16:42:35 Success Message successfully received by messaging system. Profile: XI URL: http://ussapxi3:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2009-02-20 16:42:35 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.

2009-02-20 16:42:35 Success Message successfully put into the queue.

2009-02-20 16:42:35 Success The message was successfully retrieved from the request queue.

2009-02-20 16:42:35 Success The message status set to DLNG.

2009-02-20 16:42:35 Success Delivering to channel: CC_WS_Receiver

2009-02-20 16:42:35 Success MP: Entering module processor

2009-02-20 16:42:35 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

2009-02-20 16:42:35 Success SOAP: request message entering the adapter with user J2EE_GUEST

2009-02-20 16:42:36 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK

2009-02-20 16:42:36 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK

2009-02-20 16:42:36 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK

2009-02-20 16:42:36 Error Exception caught by adapter framework: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK

2009-02-20 16:42:36 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK. Setting message to status failed.

2009-02-20 16:42:36 Error The message status set to FAIL.

2009-02-20 16:42:36 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK.

Thanks

Sudhakar Korrapati

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

have solved the problem? how?

former_member750652
Contributor
0 Kudos

Hi sudhakar,

The error must be due to the SOAP-URL that you specify in the receiver communication channel .Chek the URL validity and try to run it again.

Please refer the follwing therad that discusses the same issue ,which has SOAP on the Eeiver side.This should be helpful to you.

Thanks,

Ram.

Former Member
0 Kudos

Hi

The content type should TEXT/XML

that causes the error..

Try to check the target URL in your Soap receiver.

it has to be ur wsdl's url and as a simple test, when you try that in browser you have to see the wsdl code not any other page.

Regards

Vishnu

sud
Discoverer
0 Kudos

Hi Vishnu,

Thanks for your solution. After correcting the URL with wsdl path the earlier error has gone . Now i am getting an another message like "SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault". Do you have any idea on this .

Audit Log for Message: a44ddb40-ffcc-11dd-8e0d-001185b7794d

Time Stamp Status Description

2009-02-20 23:03:49 Success Message successfully received by messaging system. Profile: XI URL: http://ussapxi3:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2009-02-20 23:03:49 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.

2009-02-20 23:03:49 Success Message successfully put into the queue.

2009-02-20 23:03:49 Success The message was successfully retrieved from the request queue.

2009-02-20 23:03:49 Success The message status set to DLNG.

2009-02-20 23:03:49 Success Delivering to channel: CC_WS_Receiver

2009-02-20 23:03:49 Success MP: Entering module processor

2009-02-20 23:03:49 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

2009-02-20 23:03:49 Success SOAP: request message entering the adapter with user J2EE_GUEST

2009-02-20 23:03:50 Success SOAP: completed the processing

2009-02-20 23:03:50 Success SOAP: continuing to response message a558e2a0-ffcc-11dd-aba5-001185b7794d

2009-02-20 23:03:50 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application faul

2009-02-20 23:03:50 Success MP: Leaving module processor

2009-02-20 23:03:50 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.

2009-02-20 23:03:50 Success The message status set to DLVD.

thanks

sudhakar korrapati

Former Member
0 Kudos

Hello

Check the WSDL response message for yur input it looks like theres some error in response message of WSDL itself

Check WSDL with other soap client for your payload like soapUI or,...

Rajesh

Former Member
0 Kudos

Hi,

in ID in SOAP reciever comm channel, in target URL you will have to specify the URL of your target application and not its WSDL..........means if you open your target URL in internet explorer window, then you should see the operations provided by your target application and a link to see its service description........

in SOAP action provide the operation which is to be called which you can find in the WSDL of the target application.

then activate these things and rerun your scenario.

Regards,

Rajeev Gupta