title: MQ - COA correlation issue after change of remote destination from Queue to Topic
body: <p>Seeking for an advise on the below faced COA correlation issue. </p>
  
  <p><strong>Background</strong>: there is an application A which is feeding data to an application B via MQ (nothing special - remote queue def pointing to the local q def on remote QM). Where the sending app A is requesting COAs. That is a stable setup working for years: </p>
  
  <p>App A -> QM.A[Q1] -channel-> QM.B[Q2] -> App B </p>
  
  <p>Here:</p>
  
  <ul>
  <li>Q1 is a remote q def pointing to the Q2. </li>
  </ul>
  
  <p><strong>Problem</strong>: there is an application C which requires exactly the same data feed which A is sending to B via MQ. => it is required to duplicate data feed considering the following constraint. </p>
  
  <p><strong>Constraint</strong>: <strong>neither code, nor app config of applications A and B could be changed</strong> - duplication of the data feed from A to B should be transparent for applications A and B - A puts messages to the same queue Q1 on QM.A; B gets messages from the same queue Q2 on the QM.B </p>
  
  <p><strong>Proposed solution</strong>: duplicate the feed on the MQ layer by creation of the Topic/subscirbers configuration on the QM of the app B: </p>
  
  <p>App A -> QM.A[Q1] -channel-> QM.B[QA->T->{S2,S3}->{Q2,Q3}] -> {App B, QM.C[Q4] -> App C} </p>
  
  <p>Here:</p>
  
  <ul>
  <li>Q1 - has the rname property updated to point to the QA for Topic
  instead of Q2</li>
  <li>QA - Queue Alias for Topic T </li>
  <li>T - Topic </li>
  <li>S2, S3 - subscribers publishing data to the Q2 and Q3 </li>
  <li>Q2 - unchanged, the same local queue definition where App B consumes from </li>
  <li>Q3 - remote queue definition pointing to the Q4 </li>
  <li>Q4 - local queue definition on the QM.C, the queue with copy of messages sent from A to B</li>
  </ul>
  
  <p>With this set up duplication of the messages from the app A to the app B and C works fine. 
  But ... there is an issue.</p>
  
  <p><strong>Issue</strong>: application A is not able to correlate COAs and that is the problem. 
  I'm not sure if app A is not able to correlate COAs at all, or (what is more likely guess) it is not able to correlate additional COAs e.g. from the QM.C </p>
  
  <p>Any idea or advise is very much appreciated.</p>