Jarry Shao created CXF-7577:
-------------------------------

             Summary: CXF [Async Client] Didn't finished to  package the SOAP 
Message.
                 Key: CXF-7577
                 URL: https://issues.apache.org/jira/browse/CXF-7577
             Project: CXF
          Issue Type: Bug
          Components: Transports
    Affects Versions: 3.1.11
            Reporter: Jarry Shao


{color:red}Here is the tcpdump:{color}

Accept: */*
User-Agent: Apache CXF 3.1.11
SOAPAction: "*******"
Transfer-Encoding: chunked
Content-Type: multipart/related; type="application/xop+xml"; 
boundary="uuid:5697c391-f4ff-41b0-8674-d92b30fac633"; 
start="<root.mess...@cxf.apache.org>"; start-info="text/xml"
Connection: Keep-Alive

3e13
--uuid:5697c391-f4ff-41b0-8674-d92b30fac633
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: binary
Content-ID: <root.mess...@cxf.apache.org>

<soap:Envelope xmlns:soap=**********
{color:red}/**
* The Content
**/{color}
+...'..b).>.....h...K.Xx..c1V,....[.X.$..b....XxrM+..v......V..B.s...........}.2..j....)a..+.P.h_..5..u.P.._n.....B...X.3...<V,..,V,.....7.c...c.X.-......b.F+V,<.JNk....gM.Xx.k....Z...3Z....Z...
.Xx.H+......'..b.I<....Ih..[..O.r.;Z.s..sWZ.F..w.X..2wb....X.psgE......"C..]B.jv...Psi.7.Z.]~.......[.t.]gyg.X..9%V.....c...r.Xx......H.S+....
HTTP/1.1 400 Bad Request
Date: Sun, 03 Dec 2017 06:26:04 GMT
Content-Length: 226
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
</p>
</body></html>

As you can see, there're some missings for the SOAP message.
The Attachment hadn't finished packageing for the SOAP message, even didn't 
have a boundary at the end of the message.
So, what's the problem?
It's weird and strange....
Did it a Bug ?

And that's my client Properties:

httpClientPolicy.setConnectionTimeout(40000);
httpClientPolicy.setAllowChunking(true);
httpClientPolicy.setAsyncExecuteTimeout(80000);
httpClientPolicy.setAsyncExecuteTimeoutRejection(true);
httpClientPolicy.setReceiveTimeout(60000);







--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to