<?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 Slave ESB server down with ActiveMQ in bundle and master/slave in Installing and Upgrading</title>
    <link>https://community.qlik.com/t5/Installing-and-Upgrading/Slave-ESB-server-down-with-ActiveMQ-in-bundle-and-master-slave/m-p/2358956#M1926</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We install our Talend Data Services Plateform 6.5.1, with 3 Talend ESB Server. On thoses servers, ActiveMQ is installed as a Bundle, not a stand-alone service.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have the following repartition&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;ESB 1 and ESB 2 share the same kahadb file&lt;/LI&gt;
&lt;LI&gt;ESB 3 use is own kahadb file&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The issue is that the slave ActiveMQ server is always indicated as DOWN in the TAC, with the message "the CommandPort and FiletransfertPort is misconfigured".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If we stop the ESB in master ActiveMQ, the new master, previously DOWN, become up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Why do the ActiveMQ status of master/slave influence the status of the whole server?&lt;/P&gt;
&lt;P&gt;How can we contourn it?&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 07:12:11 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-11-16T07:12:11Z</dc:date>
    <item>
      <title>Slave ESB server down with ActiveMQ in bundle and master/slave</title>
      <link>https://community.qlik.com/t5/Installing-and-Upgrading/Slave-ESB-server-down-with-ActiveMQ-in-bundle-and-master-slave/m-p/2358956#M1926</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We install our Talend Data Services Plateform 6.5.1, with 3 Talend ESB Server. On thoses servers, ActiveMQ is installed as a Bundle, not a stand-alone service.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have the following repartition&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;ESB 1 and ESB 2 share the same kahadb file&lt;/LI&gt;
&lt;LI&gt;ESB 3 use is own kahadb file&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The issue is that the slave ActiveMQ server is always indicated as DOWN in the TAC, with the message "the CommandPort and FiletransfertPort is misconfigured".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If we stop the ESB in master ActiveMQ, the new master, previously DOWN, become up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Why do the ActiveMQ status of master/slave influence the status of the whole server?&lt;/P&gt;
&lt;P&gt;How can we contourn it?&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 07:12:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Installing-and-Upgrading/Slave-ESB-server-down-with-ActiveMQ-in-bundle-and-master-slave/m-p/2358956#M1926</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T07:12:11Z</dc:date>
    </item>
  </channel>
</rss>

