<?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: Deadlock during multiple Talend job execution in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Deadlock-during-multiple-Talend-job-execution/m-p/2333956#M102686</link>
    <description>You can commit your SQL output for each and every row.(using Advanced Settings).That would prevent tables to wait in loop. But this might degrade your performance!</description>
    <pubDate>Fri, 20 May 2016 17:37:58 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2016-05-20T17:37:58Z</dc:date>
    <item>
      <title>Deadlock during multiple Talend job execution</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Deadlock-during-multiple-Talend-job-execution/m-p/2333955#M102685</link>
      <description>&lt;FONT color="#1f3864"&gt;I&lt;/FONT&gt; have talend jobs configured through Talend Admin Console (TAC) in multiple instances through context groups like UK, SA etc. For these instances 
&lt;FONT color="#1f3864"&gt;I&lt;/FONT&gt; have set the file triggers (like source file trigger, confirmation file trigger etc). For Eg, UK instance is dependent on both UK source file and a confirmation file from a dependent process say X.&amp;nbsp; 
&lt;BR /&gt;But these 2 instances can run in parallel (since the UK and SA source files can come in parallel). When these instances 
&lt;FONT color="#1f3864"&gt;am&lt;/FONT&gt; trying to insert/update into the same SQL server 2012 database table at the same time, one of the instance is failing with the deadlock error as below:&amp;nbsp; 
&lt;BR /&gt; 
&lt;B&gt;&lt;FONT color="red"&gt;&lt;FONT face="'Bookman Old Style', serif"&gt;“java.sql.SQLException:Transaction (Process ID 69) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.” &lt;/FONT&gt;&lt;/FONT&gt;&lt;/B&gt; 
&lt;FONT color="red"&gt;&lt;FONT face="'Bookman Old Style', serif"&gt;.&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;BR /&gt;Hence 
&lt;FONT color="#1f3864"&gt;I&lt;/FONT&gt; need to manually run the failed instance again in such cases. 
&lt;BR /&gt;Hence 
&lt;FONT color="#1f3864"&gt;I&lt;/FONT&gt; 
&lt;FONT color="#1f3864"&gt;am&lt;/FONT&gt; looking out for an option on TAC side itself if TAC can handle such type of parallel runs/deadlocks and wait for the other process/instance to complete successfully before proceeding with the current process/instance (so that 
&lt;FONT color="#1f3864"&gt;I&lt;/FONT&gt; do not get this deadlock error and hence avoid this manual re-run). 
&lt;BR /&gt;Also, I need to know if TAC has a “RETRY” job option – which basically re-runs the failed jobs automatically “N” number of times&amp;nbsp; (where “N” can be configured) – This property is present in few other schedulers and hence need to check if TAC has this kind of property. 
&lt;BR /&gt;Any inputs which will help us to resolve this issue is appreciated. 
&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Fri, 20 May 2016 14:51:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Deadlock-during-multiple-Talend-job-execution/m-p/2333955#M102685</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2016-05-20T14:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: Deadlock during multiple Talend job execution</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Deadlock-during-multiple-Talend-job-execution/m-p/2333956#M102686</link>
      <description>You can commit your SQL output for each and every row.(using Advanced Settings).That would prevent tables to wait in loop. But this might degrade your performance!</description>
      <pubDate>Fri, 20 May 2016 17:37:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Deadlock-during-multiple-Talend-job-execution/m-p/2333956#M102686</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-05-20T17:37:58Z</dc:date>
    </item>
  </channel>
</rss>

