[ 
https://issues.apache.org/jira/browse/CXF-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595427#comment-16595427
 ] 

Amar K commented on CXF-7828:
-----------------------------

[~coheigea]

Thanks for the response. unfortunately I don't have a separate project for this 
implementation. It is part of a bigger project which has lot of other 
dependencies and I can't pull it out easily. I will try to setup a new 
meanwhile please see the exception stacktrace below for this issue.

 
{code:java}
Stacktrace :
Caused by: org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not 
valid when sent to a SOAP 1.1 only endpoint. at 
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:159)
 at 
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:62)
 at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
 at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:835) at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606)
 at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1502)
 at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1309)
 at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) at 
org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:627) at 
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
 at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
 at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:565) at 
org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:474) at 
org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:377) at 
org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:330) at 
org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) at 
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135) ... 98 
more 
{code}
Thanks

Amar.

 

> Increased size of the payload(xml as a string) results - A SOAP 1.2 message 
> is not valid when sent to a SOAP 1.1 only endpoint. - Error
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-7828
>                 URL: https://issues.apache.org/jira/browse/CXF-7828
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.7.7
>         Environment: Production
>            Reporter: Amar K
>            Priority: Major
>         Attachments: image-2018-08-27-10-34-12-193.png
>
>
> SOAP WSDL
> Generated client stub using the apache cxf - wsdl2java feature.
> When invoking the SOAP webservice using the SOAP client stubs generated it 
> results an error - A SOAP 1.2 message is not valid when sent to a SOAP 1.1 
> only endpoint. 
> Upon further analysis we identified *increased size of the xml string results 
> above error*. For the *lower size of the xml string the service works fine*.
> Below is the snippet of the code we are using when observed in debug the 
> *port* object refers to "org.apache.cxf.jaxws.JaxWsClientProxy" class 
> pointing to the client-stub class(FASPSoap).
>  
>  
> {code:java}
> String orderxml = "Order xml constructed as a String";
> final Transfer201210 ss = new Transfer201210();
> ss.addPort(Transfer201210.Transfer201210Port, "Transfer201210Binding", 
> soapapiurl);
> final FASPSoap port = ss.getTransfer201210Port();
> final SubmitRequest r = new SubmitRequest();
> r.setDefinition(orderxml);
> final SubmitResponse _submit__return = port.submit(r);
> {code}
>  
>  
> As per the wsdl the SubmitRequest object accepts the definition attribute as 
> a String. See below.
> !image-2018-08-27-10-34-12-193.png!
>  
> Please help us know if this a "memory intensive" related operation issue. And 
> how should it be addressed.
>  
> Thanks
> Amar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to