We just recently discovered that MutateJobService stochastically returns XML_STREAM_EXC when sending the exact same xml envelope.
The xml envelope we send looks like this, using the "get" method:
<soap:Header>
<p0:clientCustomerId></p0:clientCustomerId>
<p0:developerToken></p0:developerToken>
<p0:userAgent></p0:userAgent>
</p0:RequestHeader>
</soap:Header>
<soap:Body>
<p0:includeHistory>false</p0:includeHistory>
<p0:includeStats>false</p0:includeStats>
<p0:jobIds>-6078823978290103530</p0:jobIds>
</p0:selector>
</p0:get>
</soap:Body>
</soap:Envelope>
With clientCustomerId, developerToken and userAgent appropriately set.
Most of the time, we get a correct response, saying that the bulk was completed:
<soap:Header>
<requestId>00050200966437580aec5c4792007d59</requestId>
<serviceName>MutateJobService</serviceName>
<methodName>get</methodName>
<operations>0</operations>
<responseTime>400</responseTime>
</ResponseHeader>
</soap:Header>
<soap:Body>
<Job.Type>SimpleMutateJob</Job.Type>
<id>-6078823978290103530</id>
<status>COMPLETED</status>
</rval>
</getResponse>
</soap:Body>
</soap:Envelope>
But sometimes, maybe one out of ten requests, we get this response:
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>XML_STREAM_EXC</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
We get when we post this raw on a socket as well as using our client.
This example is using the "get" method and the MutateJobService, but we seem to be getting the same error for other methods and services as well.
We started seeing this error around 9 am UTC today and have never seen it before.
Erik Mellegård
Campanja AB