Unsupported Token Type: X.509

Hello,
I try to setup a 2-Way SSL connection with a Web Service and run in several problems. Can anybody of you provide me with support. In my opionion the handshake was successful, until the client reports this message. What does it mean?
Interner Anwendungsfehler: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: [S
ecurity:090380]Identity Assertion Failed, Unsupported Token Type: X.509
Detail:
null; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: [Security:090380]Identity Asserti
on Failed, Unsupported Token Type: X.509
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: [Sec
urity:090380]Identity Assertion Failed, Unsupported Token Type: X.509
Detail:
null; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: [Security:090380]Identity Asserti
on Failed, Unsupported Token Type: X.509
at com.itellium.ecom.webservice.EComAMSConnectionPort_Stub.operationalAv
ailability(EComAMSConnectionPort_Stub.java:30)
at Ssl2WayTest.main(Ssl2WayTest.java:122)
Caused by: javax.xml.rpc.soap.SOAPFaultException: [Security:090380]Identity Asse
rtion Failed, Unsupported Token Type: X.509
at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.ja
va:313)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.j
ava:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:443)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:303)
at com.itellium.ecom.webservice.EComAMSConnectionPort_Stub.operationalAv
ailability(EComAMSConnectionPort_Stub.java:25)
... 1 more
Kind regards,
Stefan

I have the same problem, but no solution yet.
With
-Dwblogic.webservice.verbose=true -Dssl.debug=true
-Dweblogic.StdoutDebugEnabled=true
you'll see more details:
22485234 read B returns 483
<!-------------------- RESPONSE TO CLIENT --------------->
URL : https://DBGERWS1421.de.db.com:7004/services/legi
StatusCode : 401
Headers :
WWW-AUTHENTICATE = Basic realm="weblogic"
CONNECTION = Keep-Alive
CONTENT-LENGTH = 483
CONTENT-TYPE = text/xml
DATE = Wed, 16 Mar 2005 154457 GMT
Envelope :
<?xml version="1.0" encoding="utf-8" standalone="yes"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" x
lns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="htt
://www.w3.org/2001/XMLSchema"><env:Body><env:Fault><faultcode>Client.Authentication</faultcode><faultstring>[Security:090380
Identity Assertion Failed, Unsupported Token Type: X.509</faultstring></env:Fault></env:Body></env:Envelope>
<!-------------------- END RESPONSE TO CLIENT ----------->
NEW ALERT with Severity: WARNING, Type: 0
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
at javax.net.ssl.impl.SSLSocketImpl.close(Unknown Source)
at weblogic.webservice.binding.https.HttpsBindingInfo.closeSharedSocket(HttpsBindingInfo.java:145)
at weblogic.webservice.binding.https.HttpsClientBinding.releaseSocket(HttpsClientBinding.java:75)
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:272)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:63)
at weblogic.webservice.core.HandlerChainImpl.handleResponse(HandlerChainImpl.java:231)
at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:243)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:303)
at test.com.db.legi.ejb.LegiConnectorPort_Stub.checkPassword(LegiConnectorPort_Stub.java:27)
at test.com.db.legi.service.WSLegiTestClient.main(WSLegiTestClient.java:75)
avalable(): 22485234 : 0 + 0 = 0
write ALERT, offset = 0, length = 2
Wrong Password !!!
exception:
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: [Security:090380]Identity Assertion Failed, Unsu
ported Token Type: X.509
Detail:
null; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: [Security:090380]Identity Assertion Failed, Unsupported Token Type: X.509
at test.com.db.legi.ejb.LegiConnectorPort_Stub.checkPassword(LegiConnectorPort_Stub.java:38)
at test.com.db.legi.service.WSLegiTestClient.main(WSLegiTestClient.java:75)
Caused by: javax.xml.rpc.soap.SOAPFaultException: [Security:090380]Identity Assertion Failed, Unsupported Token Type: X.509
at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:303)
at test.com.db.legi.ejb.LegiConnectorPort_Stub.checkPassword(LegiConnectorPort_Stub.java:27)

Similar Messages

  • Java.security.InvalidKeyException: Unsupported key type: SunPKCS11-MyPKCS11

    I am having a very strange issue with my CAC card. I wrote a small Java program to login into ProjectForge.mil webservice
    ICollabNetSoap m_sfSoap = (ICollabNetSoap)
    ClientSoapStubFactory.getSoapStub(ICollabNetSoap.class, "https://project.forge.mil/");
    String sessionId = m_sfSoap.login("", "");
    After entering CAC PIN, it is throwing exception saying that "javax.net.ssl.SSLHandshakeException: Received fatal alert: unsupported_certificate".
    More specific exception is:
    Caused by: java.security.InvalidKeyException: Unsupported key type: SunPKCS11-MyPKCS11 RSA private key, 2048 bits (id 39632224, token object, sensitive, unextractable)
    Note: I have asked three of my co-workers to run the same program using their CAC's and seems to be working fine.
    Only the difference between their CACs and mine is CA(Certificate Authority Value. Their's is 24 and where as mine is 25). It looks like JVM was not able to understand the private key of my CAC.
    On the other note, my CAC cworks fine with web service client application that was written in .Net.
    I am using Jdk-1.6.0_26 and I have already downloaded and installed latest jce .jar files.
    Any help is greatly appreciated
    Here are the exception details:
    =======================================
    [java] Tue Aug 02 17:07:54 MST 2011 URL assignment worked
    [java] Tue Aug 02 17:07:54 MST 2011 Trying login...
    [java] Exception in thread "main" AxisFault
    [java] faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    [java] faultSubcode:
    [java] faultString: javax.net.ssl.SSLHandshakeException: Received fatal alert: unsupported_certificate
    [java] faultActor:
    [java] faultNode:
    [java] faultDetail:
    [java] {http://xml.apache.org/axis/}stackTrace:javax.net.ssl.SSLHandshakeException: Received fatal alert: unsupported_certificate
    [java] at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
    [java] at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:136)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1720)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:954)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1138)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1165)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1149)
    [java] at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:186)
    [java] at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
    [java] at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
    [java] at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
    [java] at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
    [java] at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    [java] at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    [java] at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
    [java] at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    [java] at org.apache.axis.client.Call.invoke(Call.java:2767)
    [java] at org.apache.axis.client.Call.invoke(Call.java:2443)
    [java] at org.apache.axis.client.Call.invoke(Call.java:2366)
    [java] at org.apache.axis.client.Call.invoke(Call.java:1812)
    [java] at com.collabnet.ce.soap50.webservices.cemain.CollabNetSoapStub.login(CollabNetSoapStub.java:115)
    [java] at com.collab.examples.LoginTF.main(LoginTF.java:30)
    [java] {http://xml.apache.org/axis/}hostname:GDYL8420N5B
    [java] javax.net.ssl.SSLHandshakeException: Received fatal alert: unsupported_certificate
    [java] at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
    [java] at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
    [java] at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
    [java] at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    [java] at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    [java] at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
    [java] at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    [java] at org.apache.axis.client.Call.invoke(Call.java:2767)
    [java] at org.apache.axis.client.Call.invoke(Call.java:2443)
    [java] at org.apache.axis.client.Call.invoke(Call.java:2366)
    [java] at org.apache.axis.client.Call.invoke(Call.java:1812)
    [java] at com.collabnet.ce.soap50.webservices.cemain.CollabNetSoapStub.login(CollabNetSoapStub.java:115)
    [java] at com.collab.examples.LoginTF.main(LoginTF.java:30)
    [java] Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: unsupported_certificate
    [java] at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
    [java] at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:136)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1720)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:954)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1138)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1165)
    [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1149)
    [java] at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:186)
    [java] at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
    [java] at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
    [java] at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
    [java] ... 11 more
    [java] Java Result: 1
    ==================================================================
    I have captured more specific exception which says
    Caused by: java.security.InvalidKeyException: Unsupported key type: SunPKCS11-MyPKCS11 RSA private key, 2048 bits (id 39632224, token object, sensitive, unextractable)

    Thanks, I have installed OpenSSL.
    Here is the PEM copy of my certificate
    ==================================================
    -----BEGIN CERTIFICATE-----
    MIIElTCCA32gAwIBAgIDG5RgMA0GCSqGSIb3DQEBBQUAMFcxCzAJBgNVBAYTAlVT
    MRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UE
    CxMDUEtJMRIwEAYDVQQDEwlET0QgQ0EtMjUwHhcNMTEwMzI1MDAwMDAwWhcNMTIw
    NTI4MjM1OTU5WjCBjDELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJu
    bWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxEzARBgNVBAsTCkNPTlRS
    QUNUT1IxMjAwBgNVBAMTKVlBUlJBUFVSRUREWS5TT01BU0VLSEFSQS5SRUREWS4x
    Mzg2Nzc5MDM4MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArPjzB0Lk
    FAMegXbka3944sAm2jq7qKGnpIYhL82/gAj7zJzAPJsoE66L9spiEoDfh0osy2pO
    wqH/0NfQdGjgIGjDG2OrKhTxYXBqKZk2p7V84H4RK5duB8JU7B7R7uY+U9RkyiNd
    YuSycGXKULGa5eow/OCCI3iN8A+4NjpvswKhw3WvWhDow4xl1x6E6I89RhscU78z
    D6VtamidLK8mCWDihplmSFtCCCK5RsUjv/KuZcASAHe3Tb7di2Fb68liS5Yhf5v7
    SrezRYHbHpAZMOImy74t1UzcGkHFkE5kO4SPbAcVyhMwzE3aZNubXl5biQCEmxqh
    80HvckcQj+b5TwIDAQABo4IBMjCCAS4wHwYDVR0jBBgwFoAULgtl+dZl3kujJXWk
    oS6FIUBzuQowNQYDVR0fBC4wLDAqoCigJoYkaHR0cDovL2NybC5kaXNhLm1pbC9j
    cmwvRE9EQ0FfMjUuY3JsMA4GA1UdDwEB/wQEAwIGwDAjBgNVHSAEHDAaMAsGCWCG
    SAFlAgELCTALBglghkgBZQIBCxMwHQYDVR0OBBYEFFhzyfk4PpY2JzyrNAH+ka4n
    MDLRMGMGCCsGAQUFBwEBBFcwVTAxBggrBgEFBQcwAoYlaHR0cDovL2NybC5kaXNh
    Lm1pbC9zaWduL0RPRENBXzI1LmNlcjAgBggrBgEFBQcwAYYUaHR0cDovL29jc3Au
    ZGlzYS5taWwwGwYDVR0JBBQwEjAQBggrBgEFBQcJBDEEEwJVUzANBgkqhkiG9w0B
    AQUFAAOCAQEATpknlaaGiKZRNL+8YNgVy2kQDEFgdg/O4tB7NBRq3PiyUodnpOur
    2WbML+ViDMv7IxKEKUGnOgpc9CRNCR3+NERmaeVShlQwfF/3PjZ/DWiSuSMD79qC
    Y+tom4AkV69kLKl/O07Ql+jYh+Uy1x+MGWm46QsdOU5kwXHvPrgBI+5IpOrhXAW9
    DmOfTbdpmQvQHBC8nnLscrolQutLQtOIN60mRZmJG1x762sGNQsFgO8fTOus+C8v
    rlGafWRi/BJxlQCB3qb5nvI1TI68DLlqvgvX8IR7fpL/tq222PDAorpGf23YpSQt
    9x1xD5aZLkgYIICa6/L1Yus9FjtCR6eHug==
    -----END CERTIFICATE-----
    =======================================================

  • Getting 415 Unsupported Media Type error when calling a windows web service

    I have a BPEL process that invokes a windows web service. This process is working currently on the production system. When trying to run the process in a new test clustered environment, I'm getting the error below (bolded).
    We're using 10.1.3.3 Oracle Application Server and BPEL. Please advise on what config files might need to be tweaked to fix this.
    InvokeWindowsLoggingWebService(faulted)
    [2010/04/16 17:26:35] Faulted while invoking operation "WriteLog" on provider "WindowsLoggingWebService". less
    -<messages>
    -<input>
    -<InvokeWindowsLoggingWebService_InputVariable>
    -<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="parameters">
    -<WriteLog xmlns="http://tempuri.org/">
    <FileAbsolutePath>
    R:\CV & RM\upload_from_test.log
    </FileAbsolutePath>
    <Content>
    ||*************************************************************************************|Append to log file 2010-04-16T16:57:08-04:00|*************************************************************************************||START DATE: 2010-04-16T16:57:08-04:00|END DATE: 2010-04-16T17:25:58-04:00|COUNT: 106|TRANSFER OF FILES TO TAS SUCCESSFUL
    </Content>
    <NewLineDelimiter>
    |
    </NewLineDelimiter>
    </WriteLog>
    </part>
    </InvokeWindowsLoggingWebService_InputVariable>
    </input>
    -<fault>
    -<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="summary">
    <summary>
    exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 415 Unsupported Media Type
    </summary>
    </part>
    </remoteFault>
    </fault>
    </messages>
    [2010/04/16 17:26:35] "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. less
    -<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="summary">
    <summary>
    exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 415 Unsupported Media Type
    </summary>
    </part>
    </remoteFault>

    I generated a proxy service in jdev and used the same parms as was done on OAS...
    <WriteLog xmlns="http://tempuri.org/">
    <FileAbsolutePath>
    R:\CV & RM\upload_from_test.log
    </FileAbsolutePath>
    <Content>
    ||*************************************************************************************|Append to log file 2010-04-16T16:57:08-04:00|*************************************************************************************||START DATE: 2010-04-16T16:57:08-04:00|END DATE: 2010-04-16T17:25:58-04:00|COUNT: 106|TRANSFER OF FILES TO TAS SUCCESSFUL
    </Content>
    <NewLineDelimiter>
    |
    </NewLineDelimiter>
    </WriteLog>
    and was able to call the service fine and it returned successful. Just seems to be an issue on the server when I execute it from there.

  • ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type

    Hi All,
    We have a Proxy to SOAP scenario which is throwing the below response.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    We have used XSLT mapping and also used the Message transform bean (ocalejbs/AF_Modules/MessageTransformBean) with the module parameters.
    Please help.

    this is the Audit log... Just in case this helps..
    20.10.2011 09:57:34 Information Transform: successfully transformed
    20.10.2011 09:57:34 Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    20.10.2011 09:57:34 Information SOAP: request message entering the adapter with user J2EE_GUEST
    20.10.2011 09:57:34 Information SOAP: completed the processing
    20.10.2011 09:57:34 Information SOAP: continuing to response message 765df5dd-fb23-11e0-a52b-0000124b6826
    20.10.2011 09:57:34 Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    20.10.2011 09:57:34 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    20.10.2011 09:57:34 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    20.10.2011 09:57:34 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: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error. Setting message to status failed.
    20.10.2011 09:57:34 Error The message status was set to FAIL.

  • Unsupported file type (.mov)

    I am using Adobe After Effects CS4 (9...)
    I am trying to create Andrew Krammer's ,,crumble" effect (http://www.videocopilot.net/tutorial/procedural_crumble/)
    If you skip at 23:44 you will see that he is adding an imported .mov file.
    Everytime i try to import a .mov file, i get the following error: After Effects error: Can't import file "NAME.mov": unsupported file type or extension.     ( 0::1 )
    I think I have what I need: QuickTime 7.7.1 (it's the latest version I found, right from Apple's website)
    (I don't know if this really helps:) When i click File>Export> QuickTime is disabled, not selectable. It says: QuickTime 7.4.1 or later required (even though i have 7.7.1)
    I do not really want to convert the .mov into anything else because I saw that the .mov file (from Andrew Krammer's video) don't display the background, only the dust (in my case). Other video types DO display the black background. The files I try to import to AE work (they can be opened with QuickTime, no errors)

    What is your OS? After Effects requires QuickTime. Is your AE up to date?

  • HTTP 415 Unsupported Media Type with SOAP adapter ?

    Hello All,
    Iam getting  HTTP 415 Unsupported Media Type with SOAP adapter  error while executing the scenario.
    i got one thread which have the solution. iam not getting exactly how to write message transform Bean.
    HTTP 415 Unsupported Media Type with SOAP adapter trying to put SOAP header
    Please tell me where i need to write the MessageTransformBean at sender adapter or receiver file adapter.
    Thanks and regards,
    chinna

    Hi Chinna,
    Have you checked this
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
    Regards
    Ramesh

  • [RPC Fault faultString="HTTP/1.1 415 Unsupported Media Type" faultCode="Server.Proxy.Request.Failed"

    Hi,
    Posting in the 'General' forums as well. Did not yet get any response for the topic posted in the 'Configuration and Getting Started Discussion' forum.
    I am having nightmares to call the POST method of a REST service thru Flex. Initially tried with the HTTPService without any proxy server. Wasn't able to call POST, though the GET method was successfully called. Please see the post here (http://www.flexdeveloper.eu/forums/actionscript-3-0/how-to-acces-post-method-of-rest-web -service-thru-flex/)
    b THEN I tried with BlazeDS
    , but with the same results!
    I have set up BlazeDS with the integrated Tomcat option. I have also set up the Flex project as mentioned in the instructions. It is working fine when I run the sample projects.
    But the problem is that
    i when I try to access a
    b POST for a REST service,
    i I get the "HTTP/1.1 415 Unsupported Media Type" fault.
    b The complete fault I'm getting is: [RPC Fault faultString="HTTP/1.1 415 Unsupported Media Type" faultCode="Server.Proxy.Request.Failed" faultDetail="HTTP/1.1 415 Unsupported Media Type"]
    at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev \3.1.0\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:218]
    at mx.rpc::Responder/fault()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc\Responder.as:53 ]
    at mx.rpc::AsyncRequest/fault()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc\AsyncRequest .as:103]
    at HTTPMessageResponder/resultHandler()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\messagin g\channels\HTTPChannel.as:871]
    at HTTPMessageResponder/completeHandler()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\messag ing\channels\HTTPChannel.as:940]
    at ChannelRequestLoader/callEventCallback()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\mess aging\channels\HTTPChannel.as:1155]
    at ChannelRequestLoader/completeHandler()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\messag ing\channels\HTTPChannel.as:1191]
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at flash.net::URLLoader/onComplete()
    I have added correct entry to the policy-config.xml (I know this because the GET for the same REST service is working).
    b Only the POST thing is giving me the fault!
    Appreciate any inputs. (am in need of 'em badly)
    thanks
    BJG

    My guess is that the Server/Rest service doesn't like the content type of the request. HTTPService uses a content type of application/x-www-form-urlencoded by default. Maybe the Rest service is expecting the request to be XML? If that's the case, you need to set the contentType property of the HTTPService to application/xml.
    Sometimes an HTTP sniffer/proxy such as Charles can be useful for debugging these kinds of issues. If my suggestion doesn't help, capture the HTTP request and response using a HTTP sniffer like Charles and post back to this thread with it and someone will take a look at it for you. Thanks.
    -Alex

  • HTTP 415 Unsupported Media Type with SOAP adapter trying to put SOAP header

    Hello,
    I am trying to put data into soap header using soap receiver adapter. Seems like building the complete soap message is the right way to go. Thus I wrote a java program to build the complete soap message (soap envelop, soap header and soap body which contains the message PI received from the sender). Mapping program works well. However when I ran the scenario, I got Error "SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type" when calling the receiver's web service (the SOAP receiver adapter CC have the "Do Not use SOAP Envelop" checked). Anyone knows why I got this error? From google, seems like this error is because the http's content-type is set to other type, rather than "text/xml". However in soap CC there is no option to control this.
    The message sent to the receiver is (after mapping);
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
    <SOAP-SEC:Signature xmlns:SOAP-SEC="http://schemas.xmlsoap.org/soap/security/2000-12" MyAttr="value">My Test Value</SOAP-SEC:Signature>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    <ns1:UpdateEquipment xmlns:ns1="http://mycomp.com/mywebservice">
    <ns1:EquipmentNumber>000000012345</ns1:EquipmentNumber>
    <ns1:LicensePlate>654321</ns1:LicensePlate>
    </ns1:UpdateEquipment>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Anyone can help?
    Thanks

    When you check "Do Not use SOAP Envelop", the SOAP adapter chooses application/xml instead of text/xml.
    You can change the content type with help of the MessageTransformBean. You put the bean in the module chain of the receiver channel and add the parameter Transform.ContentType = text/xml
    See
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/57/0b2c4142aef623e10000000a155106/frameset.htm

  • 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

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

  • Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text

    Hi I am in trouble with JAX-WS 2.1.2M1
    I try to call my Webservice like this:
    Service service = Service.create(serviceName);
            service.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING, "http://spblue.liberty:8084/SPBlue/GlobalLogoutService");
    Dispatch<SOAPMessage> disp = service.createDispatch(portName, SOAPMessage.class, Service.Mode.MESSAGE);
            SOAPMessage message = XmlUtil.getSOAPMessageFromString(request);
            SOAPMessage response = disp.invoke(message);when my disp invokes I get following Exception which seems to as a little Problem, anyway I don�t know how to get rid of this Exception.
    com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:116)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:158)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400)
    at com.sun.xml.ws.client.Stub.process(Stub.java:234)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:166)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:192)
    at test.service.Logout.requestLogout(Logout.java:115)
    at test.service.Logout.main(Logout.java:149)
    ERROR: JDWP Unable to get JNI 1.2 environment, jvm->GetEnv() return code = -2
    JDWP exit error AGENT_ERROR_NO_JNI_ENV(183): [../../../src/share/back/util.c:820]
    my ServiceClass is:
    @ServiceMode(value=Service.Mode.MESSAGE)
    @WebServiceProvider( targetNamespace="http://spblue.liberty:8084/wsdl/globalLogout")
    public class GlobalLogoutServiceImpl implements Provider<SOAPMessage> {
         * Web service operation
        public SOAPMessage invoke( SOAPMessage logoutRequest ){
            return logoutRequest;
    }So how can I set the Charachter set before invokikng the service.
    Or how can I change the Service to accept UTF-8.
    Well, I don�t know.
    Any help is welcome.

    Hi,
    I don't know if this can help you, but I had a similar problem while invoking a web service. Eventually, I found out that the server was returning an html error page, and not the expected xml answer.
    That's why the client code raises such an error... It means that the MIME type of the anser is text/html (for the html page) and not the text/xml type of the 'nominal' web service answer.
    You can verify this by using a proxy to intercept the http request and answer involved in this web service invocation (use Fiddler for instance). Then, you will see that the server responds by sending an html page saying that something is wrong.
    Hope this helps...
    Sam

  • 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

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

  • Windows Web Services - Unsupported media type

    Hi,
    I'm trying to migrate a web service from .NET WCF to C++ Windows Web Services API. I generated .c and .h files using WSDL, create few wrappers and incorporated it into the C++ code and try it using a gSOAP client. Sadly, it wasn't working.
    Here is the response from the WWS:
    HTTP/1.1 415 Unsupported Media Type
    Server: Microsoft-HTTPAPI/2.0
    Date: Mon, 14 Jul 2014 10:50:23 GMT
    Connection: close
    Content-Length: 0
    I debug it for a while, and found out, that WWS apparentely cannot handle action parameter in Content-Type.
    Content-Type: text/xml; charset=utf-8; action="http://tempuri.org/IReferenceClockWebService/SetRecordTimeLeftDiff"
    After I remove the action parameter, everything is working.
    Why is this happening. Isn't an action parameter common part of SOAP HTTP requests? Is there any workaround?
    Thanks in advance.

    Hi,
    I'm trying to migrate a web service from .NET WCF to C++ Windows Web Services API. I generated .c and .h files using WSDL, create few wrappers and incorporated it into the C++ code and try it using a gSOAP client. Sadly, it wasn't working.
    Here is the response from the WWS:
    HTTP/1.1 415 Unsupported Media Type
    Server: Microsoft-HTTPAPI/2.0
    Date: Mon, 14 Jul 2014 10:50:23 GMT
    Connection: close
    Content-Length: 0
    I debug it for a while, and found out, that WWS apparentely cannot handle action parameter in Content-Type.
    Content-Type: text/xml; charset=utf-8; action="http://tempuri.org/IReferenceClockWebService/SetRecordTimeLeftDiff"
    After I remove the action parameter, everything is working.
    Why is this happening. Isn't an action parameter common part of SOAP HTTP requests? Is there any workaround?
    Thanks in advance.

Maybe you are looking for

  • I have two apple accounts and need to delete one, I have two apple accounts and need to delete one

    I have two apple accounts, one on my iphone and the other ipad & laptop.  I need to delete the iphone account and use only the other.  How do I delete without losing my data.

  • How to collapse unused text field in PDF form

    Hi all, may i know how to collapse unused text field in a PDF form. Etc, we have alot of description line for user to enter the info, but some line will be left unused, so i was wondering whether can i hide those unused text field. But when i need th

  • Keyboard short-cut for Restart and Shutdown?

    Since recent keyboards and Mac OS X doesnt have keyboard short-cuts for Shutdown and Restart, is it possible to create new ones for these functions? Also, why doesnt Mac OS X have these anymore (such as when it had the keyboard with that button you h

  • Itunes and Quicktime Installation issues

    I am getting seriously frustrated! I am tring to install the Itunes 8 version and I already had Quicktime on my computer. It keeps giving me the same error: "There is a problem with this windows installer package. A program required for this install

  • PLD - hide/show fields

    Hi experts. I have a PLD based on sales quotation in SAP B1 2007A PL38. On this pld I currently have 2 amount fields. One is for sub totals and the other one for regular line totals. The reason for two fields is based on the fact that sub totals shou