<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: EDX Command Line Fails but QMC Task Continues to Run When Multiple Docs Are Reloading in Parallel in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/EDX-Command-Line-Fails-but-QMC-Task-Continues-to-Run-When/m-p/978245#M1296309</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unless there is starvation for cores (resources) to execute, you can do polling kind of thing for any long time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming Multi-box environment and QDS is in separate box:&lt;/P&gt;&lt;P&gt;(1) 8 cores in server, can be configured for ~5 concurrent tasks &lt;/P&gt;&lt;P&gt;(2) for 12 cores server ~8 concurrent tasks should be fine.&lt;/P&gt;&lt;P&gt;So depends on the environment configuration.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Oct 2015 22:48:28 GMT</pubDate>
    <dc:creator>prabhu0505</dc:creator>
    <dc:date>2015-10-29T22:48:28Z</dc:date>
    <item>
      <title>EDX Command Line Fails but QMC Task Continues to Run When Multiple Docs Are Reloading in Parallel</title>
      <link>https://community.qlik.com/t5/QlikView/EDX-Command-Line-Fails-but-QMC-Task-Continues-to-Run-When/m-p/978244#M1296306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the last 2-3 years my project has been using the EDX command line to trigger document reloads configured in our QMC.&amp;nbsp; We use an external scheduler (Control-M) to trigger batch files on our QlikView servers and these bacth files in-turn trigger the EDX component and pass to it the task name of the document that we want to reload. (Nothing complicated, quite simple really.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The EDX executable and associated config file are saved in a central location.&amp;nbsp; Every batch file that is triggered uses this single central instance of the EDX component.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Up until recently our batch has had a serial structure where one document reload follows on after the successful completion of another.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have recently introduced a new branch to the batch that reloads a document in parallel to the existing document reloads.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are now seeing regular batch failures on an almost daily basis where EDX fails but the documents reloading in the QMC run through to a successful completion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error details passed back to Control-M seem to suggest that EDX is losing its thread with the active task when it polls the QMC to check the task's status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone on the community have experience of this issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone recommend any best practise regarding EDX command line?&amp;nbsp; For example, is it ok to have multiple documents running in parallel that were trigged from a single central instance of the EDX component?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/EDX-Command-Line-Fails-but-QMC-Task-Continues-to-Run-When/m-p/978244#M1296306</guid>
      <dc:creator>robsilcock</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: EDX Command Line Fails but QMC Task Continues to Run When Multiple Docs Are Reloading in Parallel</title>
      <link>https://community.qlik.com/t5/QlikView/EDX-Command-Line-Fails-but-QMC-Task-Continues-to-Run-When/m-p/978245#M1296309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unless there is starvation for cores (resources) to execute, you can do polling kind of thing for any long time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming Multi-box environment and QDS is in separate box:&lt;/P&gt;&lt;P&gt;(1) 8 cores in server, can be configured for ~5 concurrent tasks &lt;/P&gt;&lt;P&gt;(2) for 12 cores server ~8 concurrent tasks should be fine.&lt;/P&gt;&lt;P&gt;So depends on the environment configuration.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2015 22:48:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/EDX-Command-Line-Fails-but-QMC-Task-Continues-to-Run-When/m-p/978245#M1296309</guid>
      <dc:creator>prabhu0505</dc:creator>
      <dc:date>2015-10-29T22:48:28Z</dc:date>
    </item>
    <item>
      <title>Re: EDX Command Line Fails but QMC Task Continues to Run When Multiple Docs Are Reloading in Parallel</title>
      <link>https://community.qlik.com/t5/QlikView/EDX-Command-Line-Fails-but-QMC-Task-Continues-to-Run-When/m-p/978246#M1296313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Saravana, thanks for your reply - much apprecaited!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please help by confirming if the conclusions I am extracting from your reply are correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(1) The issue that we are seeing is more than likely resource related (i.e. cores and/or RAM) on the host server where the QMC is hosted that is implementing the document reloads?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(2) It is therefore perfectly acceptable to have just a single central instance of the EDX command line component and this can be called by multiple doc reloads that are running in parallel at the same?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards .... Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Oct 2015 14:08:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/EDX-Command-Line-Fails-but-QMC-Task-Continues-to-Run-When/m-p/978246#M1296313</guid>
      <dc:creator>robsilcock</dc:creator>
      <dc:date>2015-10-30T14:08:12Z</dc:date>
    </item>
  </channel>
</rss>

