SAAJ0537: Invalid Content-Type. Could be an error message instead of a SOAP

Hi,
At present i am using JCAPS version 5.1.1
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-
Type:text/html. Is this an error message instead of a SOAP response?
I got above error message while invoking the webservice.
My intention is to get HttpRequest from user and based on the input from user, a web service should be invoked. For this i am using BusinessProcess[einsight]
In my BusinessProcess, i have HttpServer processRequest service,
to receive HTTP requests and then i am passing the value of parameter received from http[As String] to next partner which is responsible for invoking a webservice.[Used a wsdl in client mode]
I am able to get http request successfully , but i got error while invoking web service.
Please let me know, what to do for rectifying error.

Although this is an aged topic, this is plaguing our development efforts currently. I have successfully created a webservice that can be executed externally using the generated wsdl but I am unable to get a JCD to execute the WS without getting the following error:
[#|2007-10-09T19:51:02.700-0700|SEVERE|IS5.1.2|javax.xml.messaging.saaj.soap|_ThreadID=32606; ThreadName=Worker: 34758;|SAAJ0537: Invalid Content-Type. Could be an error message instead of a SOAP message|#]
[#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-Type:text/html. Is this an error message instead of a SOAP response?|#]
[#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(MessageImpl.java:296)|#]
[#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:146)|#]
[#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.createMessage(SOAPMessageFactory1_1Impl.java:32)|#]
[#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.xml.rpc.client.http.HttpClientTransport.readResponse(HttpClientTransport.java:169)|#]
[#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:83)|#]
[#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:69)|#]
[#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at tp6.ExecutePortType_Stub.opGetControl(ExecutePortType_Stub.java:66)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at tp6.ExecutePortType_opGetControl.invoke(ExecutePortType_opGetControl.java:188)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.stc.wsclient.runtime.impl.WSDLOtdDelegateImpl.invoke(WSDLOtdDelegateImpl.java:78)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at urn_stc_egate_jce_AI_WebServices_GetControl_jcdGetControl.OpGetControl.invoke(urn_stc_egate_jce_AI_WebServices_GetControl_jcdGetControl.OpGetControl:113)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at AIWebServicesTEST_GetControl_WS.jcdTEST_GetControl_WS.start(jcdTEST_GetControl_WS.java:21)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at TEST_GetControl_WS.cmTEST_GetControl_WS_jcdTEST_GetControl_WS1.jcdTEST_GetControl_WS_Runtime_Handler.handleRequest(jcdTEST_GetControl_WS_Runtime_Handler.java:369)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at sun.reflect.GeneratedMethodAccessor4463.invoke(Unknown Source)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at java.lang.reflect.Method.invoke(Method.java:615)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:140)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:135)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at $Proxy108.handleRequest(Unknown Source)|#]
[#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at STC_MDB__eaJCAP_Scheduler_cmTEST_GetControl_WS_jc1527518542.sendMessage(STC_MDB__eaJCAP_Scheduler_cmTEST_GetControl_WS_jc1527518542.java:213)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at STC_MDB__eaJCAP_Scheduler_cmTEST_GetControl_WS_jc1527518542.onContents(STC_MDB__eaJCAP_Scheduler_cmTEST_GetControl_WS_jc1527518542.java:100)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at sun.reflect.GeneratedMethodAccessor4462.invoke(Unknown Source)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at java.lang.reflect.Method.invoke(Method.java:615)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at java.security.AccessController.doPrivileged(AccessController.java:275)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:940)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:948)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:42)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:136)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at $Proxy111.onContents(Unknown Source)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.stc.schedulerotd.scheduleradapter.FileReaderWork.run(FileReaderWork.java:77)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:54)|#]
[#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
 at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)|#]
[#|2007-10-09T19:51:02.704-0700|SEVERE|IS5.1.2|javax.xml.messaging.saaj.soap|_ThreadID=32606; ThreadName=Worker: 34758;|SAAJ0535: Unable to internalize message|#]
[#|2007-10-09T19:51:02.704-0700|INFO|IS5.1.2|STC.eGate.CMap.Collabs.TEST_GetControl_WS.cmTEST_GetControl_WS_jcdTEST_GetControl_WS1.AIWebServicesTEST_GetControl_WS.jcdTEST_GetControl_WS|_ThreadID=32606; ThreadName=Worker: 34758;|+++EXCEPTION = HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message; nested exception is:
 HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message|#]
[#|2007-10-09T19:51:02.704-0700|INFO|IS5.1.2|STC.eGate.CMap.Collabs.TEST_GetControl_WS.cmTEST_GetControl_WS_jcdTEST_GetControl_WS1.AIWebServicesTEST_GetControl_WS.jcdTEST_GetControl_WS|_ThreadID=32606; ThreadName=Worker: 34758;|+++STACK = [Ljava.lang.StackTraceElement;@31de31de|#]
[#|2007-10-09T19:51:02.705-0700|INFO|IS5.1.2|com.stc.codegen.OTDImpl.runtime.ejb.OTDService|_ThreadID=32606; ThreadName=Worker: 34758;|terminate each service|#]
Is anybody else having this same error and how was it resolved? Both my client and server settings seems to be in sync. My only iffy piece is the servlet context. For both client and server external components, host, port, servlet context match. What am I missing??

Similar Messages

SOAP: error occured: java.io.IOException: invalid content type for SOAP: TE

Hi,
We are implementing an XI scenario as follows: Mail Adapter->XI->SOAP Receiver.
Basically, we pass the XML File attachment from the Mail Adapter through XI to the SOAP Adapter. However, we keep getting the following error:
SOAP: error occured: java.io.IOException: invalid content type for SOAP: TEXT/HTML
Any ideas on where we could look to fix this problem?
Thanks,
EC

People,
most of errors like that are 401 (unauthorized), 403 (forbidden), 404 (not found) and so on. To be sure, check the message content that comes back from the webservice, in the Message Monitoring.
Obs: To visualize sync messages payload in Message Monitoring, you'll have to set the Messaging.syncMessageRemover.removebody parameter to false (default is true) in SAP XI AF Messaging service, in the Visual Administrator.
Regards,
Henrique.

Error in soap - Invalid content type

Hi all
In soap lookup, i am getting a error that the content type is invalid.
This is the string from which i have derived the xmlPayload.
<ConversionRate xmlns="http://www.webserviceX.NET/"> <FromCurrency>INR</FromCurrency><ToCurrency>USD</ToCurrency></ConversionRate>
My error message is
invalid content type for SOAP: TEXT/PLAIN: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN'. Cause Exception: 'invalid content type for SOAP: TEXT/PLAIN'.
Can someone please suggest me what could have gone wrong?

url -http://www.webservicex.net/CurrencyConvertor.asmx
action- http://www.webservicex.net/ConversionRate
I have enabled Keep headers, Keep attachments, Use query string.
my code:
AbstractTrace trace=null;
try{
trace=container.getTrace();
Channel soapChannel=LookupService.getChannel("soaplookup_buss","soap_ib");
trace.addDebugMessage("channel created");
SystemAccessor accessor=LookupService.getSystemAccessor(soapChannel);
trace.addDebugMessage("accessor created");
String message="<ConversionRate xmlns=\"http://www.webserviceX.NET/\"><FromCurrency>TRY</FromCurrency><ToCurrency>AFA </ToCurrency></ConversionRate>";
InputStream inputStream = new ByteArrayInputStream(message.getBytes());
XmlPayload reqPayload = LookupService.getXmlPayload(inputStream);
Payload resPayload=accessor.call(reqPayload);
return "success";
catch(Exception e){
trace.addDebugMessage("exception occured"+e);
return "exception occured";

Could not parse XMBMessage due to invalid content type for SOAP: TEXT/HTML

Hi all,
 I am working on a SOAP scenario,
the soap body is as follows
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Body>
 <m:MT_test xmlns:m="http://titan.co.in/test">
 <name>String</name>
 <age>String</age>
 </m:MT_test>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
when i tried to request it using XML spy, following error i am getting ,
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to invalid content type for SOAP: TEXT/HTML
 at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:158)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:916)
 at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
the request is coming to xi, when i am monitoring the communication channel in RWB,
i am getting message, "request received, error occured"
this is anew xi server, is ther any configuration need to do.
Please help me.
Regards
Pradeep P N

I'm getting the same error. Please tell me how do i resolve this?
request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://soap2soap">
 <soapenv:Header/>
 <soapenv:Body>
 <soap:mt_soapreqsender>
 <years>?</years>
 <interest>?</interest>
 <loan>?</loan>
 <tax>?</tax>
 <insurance>?</insurance>
 </soap:mt_soapreqsender>
 </soapenv:Body>
</soapenv:Envelope>
response:
<!see the documentation>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>DeliveryException</code>
 <text>com.sap.aii.af.ra.ms.api.DeliveryException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to invalid content type for SOAP: APPLICATION/OCTET-STREAM
 at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:831)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>

Invalid Content-Type error using JAXM

Hi,
I have deployed sample JAXM application to weblogic server 7.0. When I ran the
client it is throwing following error,
javax.xml.soap.SOAPException: Invalid Content-Type:text/html
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Unable
to internalize message
Following is the SOAP message I am sending to the service,
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Body>
<Item ID="101" NAME="Java" PRICE="$29.99"></Item>
<Item ID="102" NAME="Java 2" PRICE="$39.99"></Item>
<Item ID="103" NAME="JAXM" PRICE="$19.99"></Item>
<Item ID="104" NAME="Web Services" PRICE="$49.99"></Item>
</soap-env:Body>
</soap-env:Envelope>
The above application is working fine in SUN ONE Application server.
--Muthu

Hi Muthu,
Take a look at the SAAJ spec:
http://java.sun.com/xml/downloads/saaj.html
Towards the top part of the doc shows the diffs.
Regards,
Bruce
Muthu wrote:
>
Hi Bruce,
Thanks for your reply. Could I know what is the difference between JAXM and SAAJ?
--Muthu.
Bruce Stephens <[email protected]> wrote:
Hello,
Product management has stated that we have no plans to support JAXM.
Sun
has removed any depencies between JAXM and JAXRPC and created SAAJ as
a
replacement for the JAXM dependencies. JAXM will not be part of J2EE
1.4. We support SAAJ in 8.1.
Thanks,
Bruce
Muthu wrote:
Hi,
I have deployed sample JAXM application to weblogic server 7.0. WhenI ran the
client it is throwing following error,
javax.xml.soap.SOAPException: Invalid Content-Type:text/html
java.security.PrivilegedActionException: javax.xml.soap.SOAPException:Unable
to internalize message
Following is the SOAP message I am sending to the service,
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Body>
<Item ID="101" NAME="Java" PRICE="$29.99"></Item>
<Item ID="102" NAME="Java 2" PRICE="$39.99"></Item>
<Item ID="103" NAME="JAXM" PRICE="$19.99"></Item>
<Item ID="104" NAME="Web Services" PRICE="$49.99"></Item>
</soap-env:Body>
</soap-env:Envelope>
The above application is working fine in SUN ONE Application server.
--Muthu

Reason Of Error java.io.IOException: invalid content type for SOAP: TEXT/HT

Hi All,
I am getting an error, when I am sending message from few BPM's to a common Webservice Synchronously.
Delivery of the message to the application using connection AFW failed, due to: java.io.IOException: invalid content type for SOAP: TEXT/HTML. Setting message to status failed.
Previously, it was working fine. But today I am getting the errors. Could any one please explain, what exactly the reason is. I searched the Forum, but didnt find a proper resolution. We are sending the same set of data to the Webservice, which we were sending before. Please suggest.
Regards,
Subhendu

Hi Vijay,
I am wondering,Without this module, how it was working fine for so many days. Could you please throw light?
Regards,
Subhendu

Invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error

Hi,
I have this error on a SOAP Receiver Channel: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
I've found several threads on SDN Forums about similar errors, but I did not find a solution for my problem yet.
I checked this blog: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009 Pt.6 applies to my situation, but the proposed solution doesn't solve the problem.
TRACE Messaging System
u2026
2011-06-06 10:59:41.822 Success Delivering to channel: CC_SOAP_RCV_XXX
2011-06-06 10:59:41.823 Success MP: entering1
2011-06-06 10:59:41.825 Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2011-06-06 10:59:41.828 Success SOAP: request message entering the adapter with user J2EE_GUEST
2011-06-06 10:59:42.012 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
2011-06-06 10:59:42.014 Success SOAP: sending a delivery error ack ...
2011-06-06 10:59:42.014 Success SOAP: sent a delivery error ack
u2026
Message Details
Address   http://aaa.bbb.be:54000/MessagingSystem/receive/AFW/XI
Credential   PasswordCredential(PIISUSER):password=********
Transport Headers   accept-encoding=gzip sap-xi-messageid=4DEA11FE90003094E10000000AE908B4 content-length=7520 http=POST host= aaa.bbb.be:54000 user-agent=SAP NetWeaver Application Server (1.0;711) content-type=multipart/related;boundary=SAP_4DEA47CEAD3A5138E10000000AE908B4_END;type="text/xml";start="" soapaction="http://sap.com/xi/XI/Message/30"
Configuration Details SOAP Communication Channel
SOAP Receiver Channel
No modules configured
Do not use SOAP Envelope -> NOT checked
If I type the target URL in browser it opens (no login required) and I see the available web services.
Anyone any idea what's the reason for this error?
Thanks in advance
Kind Regards
Edmond Paulussen

Hi Edmond,
We faced similar problem & found alternative.
Try out, if it works for u as well.
1) Use HTTP Adapter instead of SOAP.
Transport Protocol : HTTP 1.0
Message Protocol : XI Payload in HTTP Body
Adapter Engine : Integration Server
Addressing type : URL Address.
Target Host:
Service Number :
Path Prefix:
Authentication type : we hv used Ananymus login, as our login details in payload header.
Content Type : application/soap+xml;charset=UTF-8( this is IMP).
Header Fields.
Name         value
Host           target host
XI Payload Manipulation
XML Code : UTF-8
Hope, this helps...
-santosh.

In HTTP to SOAP scenario. Error i get is "Invalid content type for SOAP"

Hi,
In HTTP to SOAP(synch) scenario. Error i get is "Invalid content type for SOAP"
When pass my data in the HTTP client, I get the following Error.
What may be the cause,How to reslove it.
Response am getting is below............................
Result:
<SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/PLAIN</SAP:AdditionalText></SAP:Error>

hi ,
Just refer following 2 links
Re: Invalid content type for SOAP
Re: invalid content type for SOAP: TEXT/HTML
Regards,
AshwinM
Reward If helpful

Invalid Content Type Error in Receiver SOAP Adapter

Hello Experts,
Is there a solution for this problem?
I am getting the following error in one of my receiver SOAP adapters:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:...:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
I have checked the message I am sending to the receiver adapter and it is XML, ok. After checking this thread: Re: Error in soap receiver adapter and SAP note 856597 I used the TCPGateway program to check what the web service is answering to the adapter request and I found the problem is due to an authentication failure. The TEXT/HTML is an error page the SAP WebAS that hosts the webservice is sending out as response saying no login method succeeded.
However... The webservice URL and basic authentication information, the user and password, are configured correctly. I double checked it and I can also run the webservice using that information directly with wsnavigator on that WebAS.
Checking the request message I found out that the root problem is that the adapter is not sending out a basic authentication request as configured. It is actually sending a header with SAP SSO2 (single signon) ticket instead.
The most strange thing is that I configured another channel exactly the same way and it sends a basic authentication header as it should and works correctly.
So as a workaround I am using this new channel instead of the problematic one but why is the original sending SSO2 tickets? It is configured exactly the same as other channels. I think that SAP SSO authentication is not even supported by XI SOAP channels!!!???
Thanks in advance for your kind responses.
-Sam.

Shabarish:
Thanks for the link, but the real issue is not the request message (regarding your blog) but that the reply from the webservice is the standard HTML page informing no login module succeeded because the adapter is deciding completely on its own that it should use SAP single signon ticket instead of basic authentication as configured.
Volker:
I have performed full and delta cache refreshes to see if the channel performs as configured in the ID but it doesn't. It insists in trying to use SSO2 ticket instead of basic authentication.
I am sure this is an ugly bug in the WEBAS Java, more so because an identically configured channel does use the basic authentication as it should. Anyone knows about a SAP note regarding this? I have performed many searches on the support service but haven't retrieved anything significant.
Thanks for your help guys!
-Sam.

PO 7.4: NW BPM: HTTP Error response for SOAP request or invalid content-type.HTTP 200 OK

Hi Experts
I am trying to call NW BPM scenario(File to BPM) from PI, and using below adapter config.
I am getting below error.
Failed to call the endpoint: Error in call over HTTP: HTTP 200 OK
SOAP: Call failed: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
Any idea how to fix this issue?
Thanks,
Sandeep Maurya.

Hi Sandeep,
Test the URL from your browser and check the proxy settings as well.
Refer the below links
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT
SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection…
Regards
Bhargava Krishna

Error: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request

Hi Gurus,
i am hardly fighting with this error in Communication Channel Monitoring:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
This is my scenario.
I do a File to SOAP Scenario. in SXI_MONITOR everything is fine.
My CommChan is a SOAP Receiver
HTTP
SOAP 1.1
Central Adapter Engine
Target URL is https --> i check url for correctness
Configure User Authentication is checked and username and pw are given and are correct.
Configure Certificate Authentication is checked are working
Configure Proxy is checked and Host and port are povided.
SOAP Action is provided
In Tab Module
if have this Processing Sequence
1 localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean transform
2 sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean Local Enterprise Bean 1
and this Module configuration (and only this)
transform Transform.ContentType text/xml;charset=utf-8
(according to /people/sobhithalaxmi.kata/blog/2009/07/21/cost-free-edi-integration-using-message-transformation-bean)
As far as i understand that my http header should have Content-Type: text/xml;charset=utf-8 now. I don't understand why Communication Channel Monitoring shows an error according to content TEXT/HTML.
Can anyone help me with that?
Is it possible that Transform.ContentType does not work for SOAP Receiver Adapter?
is there any chance to view the HTTP-Header of the outgoing SOAP Request (with PI Transaction / Java Enironment) to convince myself that the HTTP Header is text/xml?
Thank you in advance and Best Regards
Udo

Hi Thanks for your fast replies.
The Provider of the Endpoint tells me that he needs text/xml as content-type. When I sent a message to the given Endpoint via SOAP UI I can see in the HTTP LOG of SOAP UI that the Endpoint is also sending text/xml back.
Below you find the Details log out of the CommChan Monitoring.
2011-04-29 11:37:45 Information The message status was set to TBDL.
2011-04-29 11:37:45 Information Retrying to deliver message to the application. Retry: 3
2011-04-29 11:37:45 Information The message was successfully retrieved from the receive queue.
2011-04-29 11:37:45 Information The message status was set to DLNG.
2011-04-29 11:37:45 Information Delivering to channel: getxxxxx_In <---- name of my SOAP Receiver CommChan
2011-04-29 11:37:45 Information Transform: using Transform.Class: $identity
2011-04-29 11:37:45 Information Transform: transforming the payload ...
2011-04-29 11:37:45 Information Transform: successfully transformed
2011-04-29 11:37:45 Information SOAP: request message entering the adapter with user J2EE_GUEST
2011-04-29 11:37:46 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
2011-04-29 11:37:46 Information SOAP: sending a delivery error ack ...
2011-04-29 11:37:46 Information SOAP: sent a delivery error ack
2011-04-29 11:37:46 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
2011-04-29 11:37:46 Error Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
2011-04-29 11:37:46 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request.
2011-04-29 11:37:46 Error The message status was set to NDLV.
What i am missing is a hint on the Message Transform Bean and a on a successfull sending process.
What i also tried already:
i also activated the checkbox "Do not use SOAP Envelop" in CommChan Configuration. The Result you see below (the last log entry is on first line - so read from bottom to top)
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
error in response
call completed
request entering
Message processing started
As you can see there is a "call completed" and "error in response" log entry. This is missing in in the first Log. So i guess the error is still in the sending process.
Installing additional Software on the PI and use them to find out what the HTTP Request is is not possible as system access is very strict and limited :/

"Invalid content type" error in SOAP receiver

Hi ,
I have ABAP Proxy->XI->Webservice scenario.
I have configured the SOAP receiver with all neccessary information (Target URL pointing to WSDL , proxy details)
However i get the following error when i try sending data to the webservice. "Invalid Content type for SOAP: text/html"
I have seen some forums and blogs on this site on this but still not able to solve the error.
Please advice...

Hi Anand,
Have a look into this thread- similar discussion
DeliveryException:: invalid content type for SOAP: TEXT/HTML
Also check this- in the Reciever SOAP Adapter configuration i.e Target URL must be url of the WSDL.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c73884a3789
Hope this helps.......
Regards,
Abhy

Error message: invalid content type for SOAP: TEXT/HTML; HTTP 403 Forbidd

Hi All,
My scenario is Proxy to File
So in-order to test the scenario i am sending the Data from RWB using TestMessage
i have given the sender and receiver details.
and the payload i am passing is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_QAStatusReport xmlns:ns0="http://XXXX.com/xi/SARERP/IF0100_QAStatusReport/100">
 <RECORD_STRCUTURE>
 <RECORD>
 <INSP_LOT>New for EU</INSP_LOT>
 <MATNR>00000500418</MATNR>
 <SHORT_TEXT> caps SE</SHORT_TEXT>
 <PLANT>0082</PLANT>
 <BATCH>59756</BATCH>
 <VENDOR_BATCH>59756</VENDOR_BATCH>
 <INQUAL_INSP>1940</INQUAL_INSP>
 <SSQUAL_INSP>0</SSQUAL_INSP>
 <VENDOR/>
 <DATELOT_CREA>7/20/2011</DATELOT_CREA>
 <DAYS_QA>26</DAYS_QA>
 <COMMENTS>Pending Import Testing</COMMENTS>
 </RECORD>
 </RECORD_STRCUTURE>
</ns0:MT_QAStatusReport>
the error i am facing is
Error while sending message: invalid content type for SOAP: TEXT/HTML; HTTP 403 Forbidden
can any one suggest me how to solve the isssue
Thanks&Regards
Sai

I had received similar error , request you to also check following,
1. while sending the message from IE placed in RWB, just check the URL in the Test Message tab, its possible that this PI is installed just now and its settings are not done correctly. In this ask the owner or the BASIS to change it to correct URL.
for example it should look something like - http://sdndevdpi001:50100/sap/xi/engine?type=entry

SOAP adapter error: invalid content type for SOAP: TEXT/HTML.

Dear SAP experts,
Need your help again here.
Currently, i am getting this specific error in my RWB logs.
The connection is from SAP XI going to Trading Partner via SOAP adapter.
The specific error is:
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: java.io.IOException: invalid content type for SOAP: TEXT/HTML.
I've already searched on what is causing the issue and it seems majority of the information is that, the error might be due to incorrect/wrong URL that was set in the configurations in the SAP XI communication channel.
Can you confirm this one?
DO you have any thoughts on this error?
Please help.
Thank you very much!
Fred

Hi Freddiesan,
First of all, test your URL acessing it from SAP PI server's local browser to check firewall and router settings.
If it works, check these blogs:
Regards,
Rogério
Edited by: Rogério Tambellini on Jul 3, 2009 12:52 PM

Getting error"invalid content type for SOAP: TEXT/PLAIN; HTTP 503 Not Ready

Hi,
I am getting the below error in Comminication channel
'Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/PLAIN; HTTP 503 Not Ready: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN; HTTP 503 Not Ready
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN; HTTP 503 Not Ready

Hello,
Have you checked if you are passing the correct content type by validating the generated SOAP request against the format the receiver is expecting? You can try using an HTTP diagnostic tool to analyze the HTTP header e.g fiddler.
Hope this helps,
Mark

SAAJ0537: Invalid Content-Type. Could be an error message instead of a SOAP

Similar Messages

Maybe you are looking for