Databases
StackOverflow2013
Postsdbo
POOnly SOAP12 is configured, but got error "Incoming SOAP message protocol is version 1.1"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOnly SOAP12 is configured, but got error "Incoming SOAP message protocol is version 1.1"
    primarykey
    data
    text
    <p>I've configured WebService in WebSphere (7) using JAX-WS. In the last week everything was tested, but today, after cleanup and refresh, I get an error:</p> <blockquote> <p>Caused by: javax.xml.ws.soap.SOAPFaultException: Incoming SOAP message protocol is version 1.1, but endpoint is configured for SOAP 1.2. This is not supported. at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1310) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1036) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.demarshalFaultResponse(DocLitBareMethodMarshaller.java:412) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:529) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:470) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:377) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:185)</p> </blockquote> <p>What is the most suprising, SOAP 1.1 was never configured there. From begin only SOAP 1.2 was used. Here is the digest from my WSDL:</p> <pre class="lang-xml prettyprint-override"><code>&lt;wsdl:definitions name="ucmdbservice" targetNamespace="http://service.my/v3" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://service.my/v3" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt; &lt;wsdl:binding name="binding_soap12_v3" type="tns:v3"&gt; &lt;soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt; &lt;wsdl:operation name="getResult"&gt; &lt;soap12:operation soapAction="http://service.my/v3/getResult" /&gt; &lt;wsdl:input&gt; &lt;soap12:body use="literal" /&gt; &lt;/wsdl:input&gt; &lt;wsdl:output&gt; &lt;soap12:body use="literal" /&gt; &lt;/wsdl:output&gt; &lt;/wsdl:operation&gt; &lt;/wsdl:binding&gt; &lt;wsdl:service name="service_v3"&gt; &lt;wsdl:port name="port_soap12_v3" binding="tns:binding_soap12_v3"&gt; &lt;soap12:address location="http://host.my/v3"/&gt; &lt;/wsdl:port&gt; &lt;/wsdl:service&gt; &lt;/wsdl:definitions&gt; </code></pre> <p>This are the header annotations of Servlet class:</p> <pre><code>@javax.jws.WebService(wsdlLocation = "wsdl/myservice_v3.wsdl", endpointInterface = "my.service.V3", targetNamespace = "http://service.my/v3", serviceName = "myservice_v3", portName = "port_soap12_v3") @javax.xml.ws.BindingType(value = javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING) </code></pre> <p>and the annotations of client, generated from the same WSDL:</p> <pre><code>@WebServiceClient(name = "myservice_v3", targetNamespace = "http://service.my/v3", wsdlLocation = "../../wsdl/myservice_v3.wsdl") </code></pre> <p>Everything was already worked. It is tested in IBM RAD 8.0, so I suppose some RAD-issue, rather then WebSphere-issue or JAX-WS-issue, but it could be so, I don't see something obvious missing in definition.</p> <p>Notice: service names and namespaces are changed for the confidentiality reason, so don't look for namespace mismatches :)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDanubian Sailor
    1. USDanubian Sailor
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COIf your SOAP client is issuing a SOAP 1.1. request, then this is the message you should expect in your server. It seems the focus of your investigation should be the SOAP client. Why is it sending SOAP 1.1 request payloads instead of respecting the SOAP 1.2 bindings mandated in your WSDL?
      singulars
      1. POOnly SOAP12 is configured, but got error "Incoming SOAP message protocol is version 1.1"
      1. USpglezen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload