Unsupported Content-Type: application/soap+xml

I've created a simple composite application with a bpel jbi module using glassfishesbv21.
The bpel process starts when I invoke a webservice (soap-binding).
When I run a test case for the ca everything works fine.
When I call the webservice from an external web application, the client (created with netbeans wizard bundled in glassfishesbv21) obtains the response as expected and doesn't report any exception while the server rises a com.sun.xml.ws.server.UnsupportedMediaException.
Googoling I found that this maybe caused by the use of soap1.1 and soap1.2 but is also true that JAX-WS runtime should look into the WSDL to determine the binding being used and configures itself accordingly.
the stacktrace is:
Finished processing outbound messages.
Request doesnt have a Content-Type
com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:386)
at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:220)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:647)
at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
====[com.sun.xml.ws.assembler.server:request]====
<?xml version="1.0" ?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
<soap-env:Header>
<wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/Get</wsa:Action>
<wsa:To>http://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort</wsa:To>
<wsa:ReplyTo>
<wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
</wsa:ReplyTo>
<wsa:MessageID>uuid:778b135f-3fdf-44b2-b53e-ebaab7441e40</wsa:MessageID>
</soap-env:Header>
<soap-env:Body></soap-env:Body>
</soap-env:Envelope>
============
====[com.sun.xml.ws.assembler.server:response]====
<?xml version="1.0" ?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns="">
<faultcode>S:Server</faultcode>
<faultstring>javax.jbi.messaging.MessagingException: HTTPBC-E00798: Message normalization failed</faultstring>
</S:Fault>
</S:Body>
</S:Envelope>
============
Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
====[com.sun.xml.ws.assembler.server:request]====
<?xml version="1.0" ?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
<soap-env:Header>
<wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/Get</wsa:Action>
<wsa:To>http://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort/mex</wsa:To>
<wsa:ReplyTo>
<wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
</wsa:ReplyTo>
<wsa:MessageID>uuid:778b135f-3fdf-44b2-b53e-ebaab7441e40</wsa:MessageID>
</soap-env:Header>
<soap-env:Body></soap-env:Body>
</soap-env:Envelope>
============
the wsdl is:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<definitions name="coreAnagrafeUpdateService"
targetNamespace="http://service.box.nexus.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://service.box.nexus.com/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <types>
     <xsd:schema>
<xsd:import namespace="http://service.box.nexus.com/" schemaLocation="core_anagrafe.xsd"/>
</xsd:schema>
</types>
<message name="coreAnagrafeUpdateOperationRequest">
<part name="parameters" element="tns:requestParameter"/>
</message>
<message name="coreAnagrafeUpdateOperationResponse">
<part name="parameters" element="tns:coreAnagrafeResponse"/>
</message>
<message name="coreAnagrafeUpdateOperationFault">
<part name="part1" element="tns:faultMessage"/>
</message>
<portType name="coreAnagrafeUpdatePortType">
<operation name="coreAnagrafeUpdateOperation">
<input message="tns:coreAnagrafeUpdateOperationRequest"/>
<output message="tns:coreAnagrafeUpdateOperationResponse"/>
<wsdl:fault name="fault1" message="tns:coreAnagrafeUpdateOperationFault"/>
</operation>
</portType>
<binding name="coreAnagrafeUpdateBinding" type="tns:coreAnagrafeUpdatePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="coreAnagrafeUpdateOperation">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
<wsdl:fault name="fault1">
<soap:fault use="literal" name="fault1"/>
</wsdl:fault>
</operation>
</binding>
<service name="coreAnagrafeUpdateService">
<port name="coreAnagrafeUpdatePort" binding="tns:coreAnagrafeUpdateBinding">
<soap:address location="http://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort"/>
</port>
</service>
</definitions>
Can anyone help me to understand the problem and solve it?
Thanks in advance.

Hi,
Content-Type: application/xml
...check for the content type of the message that is sent ot the WS.....with the above mentioned content-type going to the WS currently...WS is not able to parse the req and hence the error....in other words wrong format being being passed.
Regards,
ABhishek.

Similar Messages

  • CFHTTP request with content-type "application/atom+xml"

    Is it possible to send a HTTP request (method="post")  with a body that has a set content-type (such as "application/atom+xml")?
    using CFHTTP and CFHTTPPRAM, it seems the tag does not accept a content-type.
    <cfhttpparam type="body" value="#myAtomXML#">
    is there anyway to have CFHTTP , post the body with a given content-type?
    IF NOT, could anyone point me to the right direction to accompolish this using Java?

    Hi,
    Have you tried the "mimetype" attribute of the <cfhttpparam> tag?.
    http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=Tags_g-h_10.html

  • 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.

  • Urgent, Please help - UnsupportedMediaException: Unsupported Content-Type

    Hello Fusion Geeks,
    I am trying to call a web service. I am using "create web service proxy" in jdev, generated by JAX-WS. When I am calling the web service using Client java code generated by jdeveloper I am getting exception "Exception in thread "main" com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/octet-stream Supported ones are: [application/soap+xml]" . I did not get any response back from web service.
    However I have some observations :
    1) I switched on HTTP analyzer on my jdeveloper to check what SOAP request is getting passed from my program. I found that the perfect SOAP message has been formed and hitting the correct endpoint. And I found that correct response back in HTTP analyzer.
    2) The error message I got is : "Exception in thread "main" com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/octet-stream Supported ones are: [application/soap+xml]" I looked into oracle support for this error message I found that this error message is listed there. I tried the solution mentioned under document titled "JAX-WS web service that uses SOAP 1.2 binding throws error "Unsupported Content-Type" [ID 844691.1]" . But that did not solve my problem.
    Thanks

    Hello Vlad,
    Thanks for your response. In response I see Content-Type: application/xop+xml; which is different from what you are saying (application/soap+xml). Surprisingly SOAP UI shows response correctly but it fails from java jax-ws proxy.
    Content-ID: <SoapContent>
    Content-Type: application/xop+xml; charset=utf-8; type="text/xml; charset=utf-8"
    Content-Transfer-Encoding: binary

  • What is RFC for "Content-Type: application/HTTP-Kerberos-session-enc"

    Does anybody know how to process HTTP request with content type "Content-Type: application/HTTP-Kerberos-session-enc" ?
    I cannot decode HTTP request:
    -- Encrypted Boundary
         Content-Type: application/HTTP-Kerberos-session-encrypted
         OriginalContent: type=application/soap+xml;charset=UTF-16;Length=1624
    -- Encrypted Boundary
         Content-Type: application/octet-stream
    <octet-stream>-- Encrypted Boundary
    Where <octet-stream> starts with four bytes [47, 0, 0, 0]
    other bytes from <octet-stream> I am trying to decode "context.unwrap()" method ("context" was created on previous request):
                                            GSSHeader gssHeader = new GSSHeader(new ByteArrayInputStream(content));
                                            log.debug("Incoming warped content length: " + content.length);
                                            log.debug("Incoming GSS header OID: " + gssHeader.getOid());
                                            log.debug("Incoming GSS header length: " + gssHeader.getLength());
                                            log.debug("Incoming GSS header MechTokenLength: " + gssHeader.getMechTokenLength());
                                       byte[] newBytes = context.unwrap(content, 0, content.length, msgProp);
    "content" - byte array which was created from <octet-stream> without first four bytes (without [47, 0, 0, 0]).
    "gssHeader" is created correctly because in debug log I see:
    Incoming warped content length: 1671
    Incoming GSS header OID: 1.2.840.113554.1.2.2
    Incoming GSS header length: 15
    Incoming GSS header MechTokenLength: 1656
    but on "unwrap" operation I've got exception:
    GSSException: Defective token detected (Mechanism level: Invalid padding on Wrap Token)
         at sun.security.jgss.krb5.CipherHelper.arcFourDecrypt(CipherHelper.java:1226)
         at sun.security.jgss.krb5.CipherHelper.decryptData(CipherHelper.java:532)
         at sun.security.jgss.krb5.WrapToken.getDataFromBuffer(WrapToken.java:230)
         at sun.security.jgss.krb5.WrapToken.getData(WrapToken.java:195)
         at sun.security.jgss.krb5.WrapToken.getData(WrapToken.java:168)
         at sun.security.jgss.krb5.Krb5Context.unwrap(Krb5Context.java:941)
         at sun.security.jgss.GSSContextImpl.unwrap(GSSContextImpl.java:384)
         at com.myproject.ws_management.WSServer$MyHandler.handle(WSServer.java:361)
         at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
         at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:65)
         at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:68)
         at sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:552)
         at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
         at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:524)
         at sun.net.httpserver.ServerImpl$DefaultExecutor.execute(ServerImpl.java:119)
         at sun.net.httpserver.ServerImpl$Dispatcher.handle(ServerImpl.java:349)
         at sun.net.httpserver.ServerImpl$Dispatcher.run(ServerImpl.java:321)
         at java.lang.Thread.run(Thread.java:619)
    KeyTab instance already exists

    It looks like [47, 0, 0, 0] (hex [2F, 0, 0, 0]) is cipher suite, but on http://www.iana.org/assignments/tls-parameters
    I fount that it is:
    0x00,0x2F TLS_RSA_WITH_AES_128_CBC_SHA [RFC3268]
    So... what does this bytes can mean ?

  • WCF returning "The content type text/html of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8)"

    I have a WCF service I am trying to run on a new installation of 64-bit Windows Server 2008 IIS. Although it runs fine on Windows 2003 IIS, it is throwing the error in the thread title, which appears to be a server config issue, but I am not sure. Googling and searching the MSDN forums did not turn up a solution. I tried running WCF Logging, but that didn't help either.
    Does anyone have any suggestions on how to solve this probelm?
    Here is the error:
    The content type text/html of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
    <title>500 - Internal server error.</title>
    <style type="text/css">

    I have the same issue on Windows 7 machine. The service works fine using a SoapUI client but a .Net client faisl to get a response.
    Hi,
    I have a WCF service which works perfectly when using SoapUI but throws error in my .Net client.
    {"The content type text/html; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first
    1024 bytes of the response were: '<HTML><HEAD><link rel=\"alternate\" type=\"text/xml\" href=\"http://xyz.mysite.com/ysa/Broker.svc?disco\"/><STYLE type=\"text/css\">#content{ FONT-SIZE: 0.7em;
    PADDING-BOTTOM: 2em; MARGIN-LEFT: 30px}BODY{MARGIN-TOP: 0px; MARGIN-LEFT: 0px; COLOR: #000000; FONT-FAMILY: Verdana; BACKGROUND-COLOR: white}P{MARGIN-TOP: 0px; MARGIN-BOTTOM: 12px; COLOR: #000000; FONT-FAMILY: Verdana}PRE{BORDER-RIGHT: #f0f0e0 1px solid; PADDING-RIGHT:
    5px; BORDER-TOP: #f0f0e0 1px solid; MARGIN-TOP: -5px; PADDING-LEFT: 5px; FONT-SIZE: 1.2em; PADDING-BOTTOM: 5px; BORDER-LEFT: #f0f0e0 1px solid; PADDING-TOP: 5px; BORDER-BOTTOM: #f0f0e0 1px solid; FONT-FAMILY: Courier New; BACKGROUND-COLOR: #e5e5cc}.heading1{MARGIN-TOP:
    0px; PADDING-LEFT: 15px; FONT-WEIGHT: normal; FONT-SIZE: 26px; MARGIN-BOTTOM: 0px; PADDING-BOTTOM: 3px; MARGIN-LEFT: -30px; WIDTH: 100%; COLOR: #ffffff; PADDING-TOP: 10px; FONT-FAMILY: Tahoma; BACKGROUND-COLOR: #003366}.intro{MARGIN-LEFT: -15px}</STYLE><TITLE>Broker
    Service</TITLE></HEAD><BODY><DIV id=\"content\"><P class=\"head'."}
    I have the same service hosted on my local machine and when I point to the local service I can execute the operation with no issues. The message encoding is Soap11. I tried changing to Soap12 but I get exact same error. Any ideas greatly appreciated.
    I do have windows Activation Features installed and I am using .Net Framework 4.
    Thanks
    Sofia Khatoon

  • Content-type: application/xml and Application server 9

    I have a web service running on Application server 9, implemented using netbeans and JAX-WS.
    When a client sends a request to it with:
    Content-type: application/xml
    the request is rejected because the server does not recognise the mime type.
    Specifically, the response is:
    HTTP/1.1 415 Unsupported Media Type
    X-Powered-By: Servlet/2.5
    Content-Type: text/plain; charset=iso-8859-1
    Date: Fri, 01 Sep 2006 14:49:04 GMT
    Server: Sun Java System Application Server Platform Edition 9.0
    Connection: close
    Everything works fine when the request has:
    Content-type: text/xml
    Is there a way to make my web service accept content type of 'application/xml'?
    -Tony Beaumont
    Aston University
    beaumoaj

    I have fixed this for myself, i.e. decompile, replace in jar.
    My problem was that most tools define the encoding but code was simply testing
    if( contentType.equalsIgnoreCase( "text/xml" ) )
    so sending xml from other tools that send contentType
    "text/xml;encoding=UTF-8" or some such, like soap tools, would mean no XML was seen.
    Is the proper source available for XSQL?

  • Unsupported Content-Type: text/html; charset=iso-8859-1

    Originally posted on JBI forum -
    It was helpfully suggested there that I check on JAX-WS forum whether this was an issue with utf-8/16 encodings...
    I have been experimenting with the openESB composite application described here
    http://jlorenzen.blogspot.com/2007/08/using-jbi-javaee-serviceengine.html
    This works fine as it appears on this webpage.
    I have tried to adapt it to act as a proxy to a secure version of Hello EJB that runs on the SSL port of glassfish AS.
    To do this I edited the EJB to set up the security properties. Edited the BPEL wsdl file and created a new composite application using the updated BPEL project.
    This leads to an Unsupported Content-Type exception when a test case is run on the composite application from SOAP-UI
    Does anyone know how I can explicitly set the content type of the proxied request to the secure WS?
    Thanks
    Joss Armstrong
    HTTPBC-E00720: Provider for service [{http://j2ee.netbeans.org/wsdl/HelloBPEL}HelloBPELService] endpoint [HelloBPELPort] responded with an error status. Error detail is: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
    BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>
    com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=EJBPartnerLink, portType={http://hellopack/}Hello, operation=sayHello)
    BPCOR-6129:Line Number is 29
    BPCOR-6130:Activity Name is Invoke1
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:968)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:538)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:181)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148)
    at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1001)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:258)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1229)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:407)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:239)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
    *Caused by: com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]*
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:171)
    at com.sun.xml.ws.tx.client.TxClientPipe.process(TxClientPipe.java:177)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.client.Stub.process(Stub.java:248)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:180)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
    at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    Request doesnt have a Content-Type
    com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:372)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:228)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
    at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)

    Jossarm/Jeff,
    The Cryptography forum is not the right forum for this question; have you tried posting to the Glassfish forum on java.net?
    But, here is what I think the problem might be:
    SOAP-based web-service security uses XML Signature and XML Encryption to secure the message - not SSL; as a result it uses text/xml at the start of its message (which is what SOAP messages are). SSL assumes that the secure session has been established and all messages thereafter, are expected to begin with text/html (as expected in HTTP). You cannot mix-and match this - unless the service is an HTTP-based service that expects a SOAP-based message embedded in the HTTPRequest.

  • Unsupported Content-Type

    I have been experimenting with the openESB composite application described here
    http://jlorenzen.blogspot.com/2007/08/using-jbi-javaee-serviceengine.html
    This works fine as it appears on this webpage.
    I have tried to adapt it to act as a proxy to a secure version of Hello EJB that runs on the SSL port of glassfish AS.
    To do this I edited the EJB to set up the security properties. Edited the BPEL wsdl file and created a new composite application using the updated BPEL project.
    This leads to an Unsupported Content-Type exception when a test case is run on the composite application from SOAP-UI
    Does anyone know how I can explicitly set the content type of the proxied request to the secure WS?
    Thanks
    Joss Armstrong
    HTTPBC-E00720: Provider for service [{http://j2ee.netbeans.org/wsdl/HelloBPEL}HelloBPELService] endpoint [HelloBPELPort] responded with an error status. Error detail is: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
    BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>
    com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=EJBPartnerLink, portType={http://hellopack/}Hello, operation=sayHello)
    BPCOR-6129:Line Number is 29
    BPCOR-6130:Activity Name is Invoke1
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:968)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:538)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:181)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148)
    at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1001)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:258)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1229)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:407)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:239)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
    *Caused by: com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]*
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:171)
    at com.sun.xml.ws.tx.client.TxClientPipe.process(TxClientPipe.java:177)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.client.Stub.process(Stub.java:248)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:180)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
    at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    Request doesnt have a Content-Type
    com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:372)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:228)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
    at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    Edited by: jossarm on May 19, 2008 9:37 AM

    Hi,
    You may want to post this question on JAX-WS forum as well. If I remember it correctly, JAX-WS currently supports only utf-8 and urf-16 encodings.
    But checking with the JAX-WS team would definitely clear this up...
    Regards
    --Sherry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Content type in SOAP receiver communication channel

    Hello,
    so far I thought that the SOAP receiver adapter always sets the content type to text/xml. However now I found out the following strange thing:
    If you check the option "without SOAP envelope" then the content type is application/xml. Is there any way to influence this as the receiver of the message only accepts text/xml.
    Have you had any similar experience?

    hi,
    - open SOAP receiver communication channel - module tab
    - add the module "localejbs/AF_Modules/MessageTransformBean" or AF_Modules/MessageTransformBean"  before the standard SOAP module
    - add the parameter = Transform.ContentType with value = text/xml
    I'm just not sure if you need to add value =  text/xml or "text/xml" so try the second one if the first one will not work
    does it work now?
    Regards,
    Michal Krawczyk

  • Unsupported Content-Type: text/html in JAX-WS

    Hi All,
    I was trying to add new WS client proxy using jdeveloper but it gives me some error:
    Exception in thread "main" com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:303)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:135)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:277)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:124)
    at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:121)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
    at com.sun.xml.ws.client.Stub.process(Stub.java:272)
    at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
    at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
    at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
    at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
    at $Proxy28.lovQueryPage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
    at $Proxy29.lovQueryPage(Unknown Source)
    at com.siebel.asi.LS_spcClinical_spcList_spcOf_spcValue_spcServiceClient.main(LS_spcClinical_spcList_spcOf_spcValue_spcServiceClient.java:51)
    Strange thing is that, it works properly when a new client proxy is created in a new Application but it fails when I try to add second proxy to the application where first proxy is already added. Any pointers?
    Thanks,
    Nikunj

    How Can I make this work in the single project. Is there some alternate way to do so ?

  • Invalid content type for SOAP: TEXT/HTML

    Hi guys,
    I’m trying to sending a message via sender soap adapter and I’m receiving this error:
    Exception caught by adapter framework: invalid content type for SOAP: TEXT/HTML
    I already have read most off all posts about this error in this forum. So, if I understand, this error means that my receiver soap adapter can’t reach the web service provider and an HTTP error notification is sent to calling application. Although, the SOAP adapter doesn’t understand this kind of errors (ex. 404 not found -> SOAP call has no error codes and use the HTTP codes for effect) and this happening because the error is in text/html format and SOAP adapter is waiting a response in text/xml.
    This is a simple calculator web service that receives two arguments and returns the sum as a result. (Like Siva Maranani weblog /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi )
    The web service is published on SAP Enterprise Portal and it works fine.
    - The login works fine
        User: ex30268
        Pwd: 12345678
    - We don’t have certificates and proxy server.
    This is the address in my receiver soap adapter: http://intranetcorpdev.edp.pt:54700/CalculatorWebService/Config1?style=document
    I already checked the settings of my receiver soap adapter and did a little test, enabling the parameter Do Not Use SOAP Envelop only in receiver adapter. And the result is an exception during mapping!!! What is means this error?
    Does anybody know how to solve this issue?
    Thanks in advance.
    Cheers,
    Ricardo.

    Hi all,
    Please forgive me for boring you again with this subject, but I haven’t yet solved this issue, I still receive the following message and I’m getting quite worried…
    >>> Invalid content type for SOAP: TEXT/HTML
    I’m following Siva Maranani web log (Invoke Webservices using SAPXI) and I will describe the steps that I did:
    <b>Integration Repository:</b>
    •     An Inbound synchronous Message Interface (CalculatorWS_IN_MI) using the message types in external definition (WSDL from web service hat I want to invoke).
    •     The other necessary data types (Calc_input_DT has 2 parameters>arg1 and arg2. and Calc_out_DT has 1 param> result) and corresponding Message types.
    •     An Outbound synchronous Message Interface (Calc_OUT_MI) using the message types defined in Integration Directory.
    •     2 Message mappings (request and response) and 1 Interface mapping.
    <b>Integration Directory:</b>
    •     A scenario calls WebServices.
    •     2 business services (webservice and webservice_calc).
    •     A Receiver determination with webservice as a sender service (note: this sender is simulated from the WSNavigator from an Enterprise Portal that I have installed locally in my laptop) the interface is (Calc_OUT_MI).
    •     An Interface determination with webservice_calc as a receiver service and the corresponding mapping interface and SOAP receiver channel.
    Configurations of SOAP receiver channel:
    Target URL: http://intranetcorpdev.edp.pt:54700/CalculatorWebService/Config1?style=document
    User: ex30268
    Pwd: 12345678
    I have picked only the parameters “Use Encoded Headers” and “Use Query String” activated. I’m not using any kind of certificates or proxy servers.
    A call tentative:
    Request
    POST /XISOAPAdapter/MessageServlet?channel=:WebService:SOAPSenderChannel&version=3.0&Sender.Service=WebService&Interface=http%3A%2F%2Fswitching%2Fxi%5ECalc_OUT_MI HTTP/1.1
    Host: ed19dci1f.appl.edinfor.pt:54900
    Content-Type: text/xml; charset="UTF-8"
    Connection: close
    Cookie: <value is hidden>
    Cookie: <value is hidden>
    Authorization: <value is hidden>
    SOAPAction: "http://sap.com/xi/WebService/soap1.1"
    Content-Length: 407
    Response
    HTTP/1.1 500 Internal Server Error
    Connection: close
    Server: SAP J2EE Engine/6.40
    Content-Type: text/xml; charset=utf-8
    Date: Fri, 12 May 2006 08:24:18 GMT
    <?xml version='1.0'?>
    <!-- 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><![CDATA[
    com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:451)
         at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:125)
         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(Compiled Code))
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java(Compiled Code))
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java(Compiled Code))
              ]]></text>
            </s:SystemError>
          </detail>
        </SOAP:Fault>
      </SOAP:Body>
    </SOAP:Envelope>
    I think that I have tried everything and read almost of posts, web logs, SDN community contribution and the info in help.sap.com, but I’m feeling unable to solve this kind of issue. I’m afraid that I was missed something. So that’s the reason to describe here all the steps that I have done.
    I hope somebody knows how to solve this issue or give me something that can help me find the end of this road…
    Thanks for all.
    Cheers,
    Ricardo.

  • 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 :/

  • DeliveryException: invalid content type for SOAP: TEXT/PLAIN; HTTP 302 Move

    Hi everyone,
    Hello all,
    I have an RFC->XI->Web Service (SOAP) synchronous scenario.
    I'm trying to send a message from the the RFC, and in the message monitoring (SXMB_MONI) I'm getting this error message:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Inbound Message
      -->
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/PLAIN; HTTP 302 Moved Temporarily</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have as the TARGET URL: http://webservices.iter.dk/calculator.asmx?WSDL
    SOAP ACTION: http://www.iter.dk/webservices/calculator.asmx/Add
    As the content type in the WSDL file: application/text
    What could be wrong? thanks...
    Felipe

    Hi Felipe
    This i think is due to incorrect address or redirection failure which is one of the major reason for 302 as per my knowledge.
    You try to post the content and test it without using XI. Download SOAP UI and test it once and let me know
    http://www.soapui.org/
    helpful blog
    Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 ***
    Thanks
    Gaurav

  • Invalid content type for SOAP: TEXT/HTML on Reciever SOAP

    HI All,
    I have a reciever SOAP channel setup to send a message and its attachments to a supplier. The recieving application is as follows:
    "It just receives the stream or contentStream and print out the content. It's just a test to see what you sent to us. It processes all http/https messages."
    If I leave the SOAP Envelope on I get the content type error in the header. If I turn the Enveloper off, I get a successful post. They are try to trap what I send to build a SOAP processor, so they want the SOAP envelope. What could be causing this?
    Kind Regards,
    Chris

    Hi Richard,
    The web service address that we must type in target URL of receiver soap adapter is the address to the WSDL. To be sure types this address in your browser and you must see a WSDL code of the webservice that you want invoke.
    The reason that you are getting “Delivery Exception: invalid content type for SOAP:TEXT/HTML.” is because you are trying to invoke a web service with wrong address.
    So, when SOAP receiver adapter try to put the message on the target side, it can’t and automatically receives an HTTP acknowledge in HTML format. As SOAP adapter doesn’t understand HTML code only XML code, it can’t recognize what kind of error is and generates an exception indicating that the content type is invalid.
    Delivery Exception: invalid content type for SOAP:TEXT/HTML is equal to any HTTP code, I have almost sure that HTTP code is a 404 Not Found, but you can’t see it...
    Post the URL here for I can check
    Cheers,
    Ricardo.

Maybe you are looking for

  • Few questions about partitioning and formatting in Windows 8

    Hello, I'm very shortly after a Windows 8 reinstall and I want to make use of this moment to finally understand partitioning and formatting in Windows 8. Before using Windows 8, I was an XP user for 5 years and I actually never bothered myself with f

  • Adding 3rd party loops to the GB library (OSX)

    Hope anyone can throw some light on this. On the previous version of GB, I used to unpack the loops, select them as a group and drag to the Loops library in GB. This added them to the library catalogue with no problems so they could be selected, list

  • Flash in the latest nightly build is not working and causing crashes. Help?

    I'm using an Asus Transformer tf101. I updated Nightly today and now flash does not work in the program. Once I attempt to play any flash video, the program crashes and it crashes one or two more times after that before I can use it again. I disabled

  • Can't Turn Of "shake to shuffle"!!!! iTouch 2G iOS 4.2.1

    I feel I have a very unique problem, I can't turn off the Shake to Shuffle mode (I'm going to call it S2S.) Before you say it, I know HOW to turn it off, but it won't actually let me. Actually, I can't change any of the settings in the "music" tab un

  • Why does De-interlacing looks better with MPEG StreamClip?

    For our client we need to render 1080i for TV and 1080p for WEB. After creating graphics in AE we add final touch and audio in PR. If we make it progressive in PR (CC2014.1) the zoom in the packshot does not look good. However if we make the 1080i Pr