<?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>article Issue in Camel cache component in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Issue-in-Camel-cache-component/ta-p/2151209</link>
    <description>&lt;DIV class="talend-tkb-migrated-content"&gt;&lt;DIV class="lia-message-template-content-zone"&gt; 
 &lt;H1&gt;Problem Description&lt;/H1&gt; 
 &lt;P&gt;When more than one route with a &lt;STRONG&gt;cache&lt;/STRONG&gt; component is deployed in Runtime, a shutdown of one of the routes shuts down the cache in of the all other components.&lt;/P&gt; 
 &lt;P&gt;&amp;nbsp;&lt;/P&gt; 
 &lt;H1&gt;Root Cause&lt;/H1&gt; 
 &lt;P&gt;This is a known bug in Camel version 2.8.5. For details, refer to Apache Camel Bug &lt;A href="https://issues.apache.org/jira/browse/CAMEL-7174" target="_blank"&gt;7174&lt;/A&gt;.&lt;/P&gt; 
 &lt;P&gt;&amp;nbsp;&lt;/P&gt; 
 &lt;H1&gt;Solution&lt;/H1&gt; 
 &lt;P&gt;The bug is fixed in Apache Camel v2.18.0.&lt;/P&gt; 
 &lt;P&gt;&amp;nbsp;&lt;/P&gt; 
 &lt;P&gt;Talend ESB 7.0.1 uses Camel 2.20, which contains the fix. Upgrade to version 7.0.1 or higher to permanently resolve this issue.&lt;/P&gt; 
&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 09 Feb 2024 18:22:49 GMT</pubDate>
    <dc:creator>TalendSolutionExpert</dc:creator>
    <dc:date>2024-02-09T18:22:49Z</dc:date>
    <item>
      <title>Issue in Camel cache component</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Issue-in-Camel-cache-component/ta-p/2151209</link>
      <description>&lt;DIV class="talend-tkb-migrated-content"&gt;&lt;DIV class="lia-message-template-content-zone"&gt; 
 &lt;H1&gt;Problem Description&lt;/H1&gt; 
 &lt;P&gt;When more than one route with a &lt;STRONG&gt;cache&lt;/STRONG&gt; component is deployed in Runtime, a shutdown of one of the routes shuts down the cache in of the all other components.&lt;/P&gt; 
 &lt;P&gt;&amp;nbsp;&lt;/P&gt; 
 &lt;H1&gt;Root Cause&lt;/H1&gt; 
 &lt;P&gt;This is a known bug in Camel version 2.8.5. For details, refer to Apache Camel Bug &lt;A href="https://issues.apache.org/jira/browse/CAMEL-7174" target="_blank"&gt;7174&lt;/A&gt;.&lt;/P&gt; 
 &lt;P&gt;&amp;nbsp;&lt;/P&gt; 
 &lt;H1&gt;Solution&lt;/H1&gt; 
 &lt;P&gt;The bug is fixed in Apache Camel v2.18.0.&lt;/P&gt; 
 &lt;P&gt;&amp;nbsp;&lt;/P&gt; 
 &lt;P&gt;Talend ESB 7.0.1 uses Camel 2.20, which contains the fix. Upgrade to version 7.0.1 or higher to permanently resolve this issue.&lt;/P&gt; 
&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 09 Feb 2024 18:22:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Issue-in-Camel-cache-component/ta-p/2151209</guid>
      <dc:creator>TalendSolutionExpert</dc:creator>
      <dc:date>2024-02-09T18:22:49Z</dc:date>
    </item>
  </channel>
</rss>

