Databases
StackOverflow2013
Postsdbo
POMagento SOAP API - Invalid XML fault(reindex())
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMagento SOAP API - Invalid XML fault(reindex())
    primarykey
    data
    text
    <p>I implemented a reindex API call. For an category index, it works as expected. For a product index (which takes about 3 min. to process), a process is started, but after approx. 45 seconds, I get a response "Invalid XML". As it looks like, there is a problem of execution time. I did change a parameter max_execution_time to 600 (seconds). I enabled logging, but get no exception or error. In index management GUI, I see that reindex process started and is finished successfully 2 minutes after a response (Invalid XML) is returned (total reindex time is approx. 3 min).</p> <p>A code of an API looks ok, because I can update all indexes, except product price and product flat data.</p> <h2>Any idea?</h2> <p>using wireshark: Request: POST /index.php/api/v2_soap/index/ HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.3053) VsDebuggerCausalityData: uIDPo6o2uSDL0oVKpqKJjDrFPsEAAAAAJt2oK8A51UOeAJsKkziyy/q2t81fNIxMnAvF+VaT7jIACQAA Content-Type: text/xml; charset=utf-8 SOAPAction: "urn:Mage_Api_Model_Server_V2_HandlerAction" Host: XXXXXXXXXXX(hidden for a security reason Content-Length: 609 Expect: 100-continue HTTP/1.1 100 Continue</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="urn:Magento" xmlns:types="urn:Magento/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt; &lt;soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"&gt; &lt;tns:iwCoreIndexingReindexById&gt; &lt;sessionId xsi:type="xsd:string"&gt;835cfa019572c1a893b3799eecbc6903&lt;/sessionId&gt; &lt;indexId xsi:type="xsd:int"&gt;4&lt;/indexId&gt; &lt;/tns:iwCoreIndexingReindexById&gt; &lt;/soap:Body&gt; &lt;/soap:Envelope&gt; </code></pre> <p>Response(after 39 seconds!) HTTP/1.1 500 Internal Service Error Date: Fri, 18 May 2012 20:50:22 GMT Server: Apache X-Powered-By: PHP/5.2.17 Content-Length: 269 Connection: close Content-Type: text/xml; charset=utf-8</p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"&gt; &lt;SOAP-ENV:Body&gt; &lt;SOAP-ENV:Fault&gt; &lt;faultcode&gt;Sender&lt;/faultcode&gt; &lt;faultstring&gt;Invalid XML&lt;/faultstring&gt; &lt;/SOAP-ENV:Fault&gt; &lt;/SOAP-ENV:Body&gt; &lt;/SOAP-ENV:Envelope&gt; </code></pre> <p>State of index is <em>processing</em>. So a call is invoked and an action is also in a <em>progress</em>. Api.php looks like(this code is execuded and no exception is logged):</p> <pre><code>public function indexingReindexById( $indexId ){ $process = Mage::getModel('index/process')-&gt;load($indexId); try{ $process-&gt;reindexAll(); } catch(exception $e){ Mage::Log($e-&gt;getMessage()); return false; } return true; } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFrenkR
    1. USFrenkR
    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. COWhat's the response XML code look like that your SOAP client is calling invalid?
      singulars
      1. POMagento SOAP API - Invalid XML fault(reindex())
      1. USAlan Storm
 

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