UnsupportedMediaException

Hi guys i'm using JAX-WS to consume a WS, but I'm getting this exception while running.
com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html Supported ones are: [text/xml]
the code:
wsclient.ws.AddWSService service = new wsclient.ws.AddWSService();
wsclient.ws.AddWS port = service.getAddWSPort();
result = port.multi(a, b);The rest of code is netbeans 5.5 generated, i just inserted the wsdl file and puff
the remote webservice i don't have access to him, so i suppose something must be changed on client side.
thanks, for any feedback.

Based on the error message it seems like you need to set the request content type to text/xml.
The error is happening from the CommandServlet which will be called before FormHandler logic execution.

Similar Messages

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

Error While Bursting Invoices Through Web Service

Hi All,
In our present implementation, we are using BI Publisher to generate pdf invoices and send them to customer through email. We have three seperate servers say server A (Billing application server running on HP Unix), server B ( File server and other batch application server which is also running on HP Unix) and server c ( BIP Server running on windows). BIP is installed in windows server but the repository and other folders of BIP are located in server B. we have installed samba in server B so that BIP can access it.
The billing application server running on hp unix generates invoice xml. one invoice xml may ontain upto 10k invoices. We transfer this xml to server B and shedule the batch job to generate the pdf invoices. The batch job is a java applicaiton which calls BIP web services after generating xdo files and passes the file name and location to web service.
When we perfomr this task through BIP GUI, it works fine and pdf invocies are generated. However, the webservice call fails during scheduling process and gives foloiwng error.
Exception in thread "main" com.sun.xml.internal.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]
at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:116)
at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:158)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:581)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:540)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:525)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:422)
at com.sun.xml.internal.ws.client.Stub.process(Stub.java:235)
at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:120)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
at $Proxy34.runReportInSession(Unknown Source)
at com.oracle.xmlns.oxp.service.publicreportservice.ConfigHandler.runReport(ConfigHandler.java:416)
at com.oracle.xmlns.oxp.service.publicreportservice.ReportObject.createReportResponse(ReportObject.java:39)
at com.oracle.xmlns.oxp.service.publicreportservice.ControlFileHandler.processSchedule(ControlFileHandler.java:132)
at com.oracle.xmlns.oxp.service.publicreportservice.PublicReportServiceClient.main(PublicReportServiceClient.java:101)
I am desperately looking for help on this and appreciate if you can spare some time to help me to find out the reason.
Thanks
Angshuman

Hi All,
Can any one help me on this please?
Regards
Angsuman

Invoking the web service

I'm trying to call the web service with automatically built service client, the code is like this:
Dispatch<Source> sourceDispatch = null;
            sourceDispatch = service.createDispatch(portQName, Source.class, Service.Mode.PAYLOAD);
            Source result = sourceDispatch.invoke(new StreamSource(new StringReader(req)));where req is String variable containing whole xml message.
but after running I have an error:
Unsupported Content-Type: text/html; charset=UTF-8 Supported ones are: [text/xml]
com.sun.xml.internal.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=UTF-8 Supported ones are: [text/xml]
at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:116)
at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280)
How to change the content-type of the message ? or maybe deal with that in better way ?
I've tried to call the service by using generated object too, this is the code
PersonManagementServiceSync_Service service = new PersonManagementServiceSync_Service();
            PersonManagementServiceSync port = service.getPersonManagementServiceSyncSoap();
            // TODO initialize WS operation arguments here
            CreatePersonRequest parameters = new CreatePersonRequest();
            SyncRequestHeaderInfo headerInfoRequest = new SyncRequestHeaderInfo();
            javax.xml.ws.Holder<CreatePersonResponse> response = new javax.xml.ws.Holder<CreatePersonResponse>();
            javax.xml.ws.Holder<SyncResponseHeaderInfo> headerInfoResponse = new javax.xml.ws.Holder<SyncResponseHeaderInfo>();
            ...parameters setup .....
            port.createPerson(parameters, headerInfoRequest, response, headerInfoResponse);but that's generates another error:
Unable to create StAX reader or writer
Does anybody know how to fix that ??? I'm using NetBeans 6.5 to build the client

Please help me on this !!!

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 ?

Jmc.dll crashes java.exe

First of thanks Sun's engineers for hard work on Java and JavaFX! I really enjoyed the features and demos from javafx.com.
Unfortunatly all of the demos involving media playback are crashing java.exe with jmc.dll being guilty (probably access violation - jmc.dll in the error dialog reports 0.0.0.0 version - but not sure). Well, I think it is my system's fault, because when I got rid of all codecs that could play mp3, java.exe stopped crashing (at least for DraggableMP3Player demo, SimpleVideoPlayer crashes without writing hs_err), but gave me MediaUnsupportedException. Regarding fixing my system - I'd like to avoid the pleasure of reinstalling Windows and I think it would be good for others having this problem to nail the cause of it. Could you explain how jmc.dll is dealing with platform codecs? How it checks what is installed? Does anyone else seen jmc.dll crashing java? Could it be hardware issue (I have nforce2 sound card)?
I've created issue [http://javafx-jira.kenai.com/browse/RT-2530] if you have the same problem please vote for it (you first need to register for free :))

I sure have put some work in this bug. I hope this will be gone soon :). I'm somewhat surprised that nobody seen it beside me - no votes, no blogs about it. But UnsupportedMediaException is known for sure and I believe it is related (that's why I've voted for it). Thanks for all your sweat, tears and blood you put in JavaFX! :)

MediaPlayer does not support mp3 files (amd64 Ubuntu Lucid)

Instead, it throws UnsupportedMediaException.
This problem does not exist on Windows systems, and MP3 files are played ok on Linux, even within web browser - Just not in JavaFx applet.

Hello awy,
there is a global issue on Media playing (audio or video) under amd64 Ubuntu (but not on Ubuntu i386).
Any amd64 user can test it by launching the MediaBox demo and getting "We're sorry, this video can't be played now":
http://javafx.com/samples/MediaBox/index.html
Please see this post for details
http://forums.sun.com/thread.jspa?threadID=5442432
and vote for this bug if like me, you would like to get some sound from javafx under amd64 linux
http://javafx-jira.kenai.com/browse/RT-8964
Regards
Philippe

UnsupportedMediaException

Similar Messages

Maybe you are looking for