title: How to disable ReplyTo on Asynchronous "one-way" exchange pattern
body: <p>About Mule 3.3 CE:</p>
  
  <p>Even though I have an asynchronous "one-way" exchange pattern it replies twice to the caller with "empty" messages before my real response. So I get three responses. The first two are just empty "crap" and then I get my real response back.</p>
  
  <p>Can I disable the first two "empty" responses and just get my real response back to where I should reply it. The caller sets up an TEMP-queue for the response from my flow. (As now it gets three respones on that response-queue.)</p>
  
  <p>Do we need to change behaviour in ActiveMQ? It is default as of now.</p>
  
  <pre><code>&lt;jms:activemq-connector name="Active_MQ_Staging" brokerURL="tcp://xxx.xxx.xxx.x:yyyy" validateConnections="true" maxRedelivery="2" doc:name="Active MQ" forceJndiDestinations="true" honorQosHeaders="true" specification="1.1" disableTemporaryReplyToDestinations="true"/&gt;
  &lt;flow name="MyFlow2" doc:name="MyFlow2"&gt;
      &lt;jms:inbound-endpoint queue="myQueue" connector-ref="Active_MQ_Staging" doc:name="JMS" exchange-pattern="one-way"/&gt;
                  &lt;all doc:name="All"&gt;
                      &lt;processor-chain&gt;
                          &lt;jms:outbound-endpoint queue="${queue.mule.levinforequest}" disableTemporaryReplyToDestinations="true" connector-ref="Active_MQ_Staging" doc:name="JMS"/&gt;
                      &lt;/processor-chain&gt;
                      &lt;processor-chain&gt;
                          &lt;logger message="Leaving AppFacade" level="INFO" doc:name="Logger"/&gt;
                      &lt;/processor-chain&gt;
                  &lt;/all&gt;
  ....
  </code></pre>
  
  <p>EDIT:
  Ok, I have not post all in the statement above.</p>
  
  <p>This is what we want to do:
  The Mule-app will receive a JMS Message. The sender (which is a stateless EJB MDB if I'm correct) will setup a few properties that I need to carry with me and I will add a few more properties. The sender gives me the name of the temporary queue setup for a response (where the mule-app (in another flow) will respond after a few other steps and other integration). This first mule-flow have I setup as "one-way" because I do not want it to respond.</p>
  
  <p>This first flow puts the message on another JMS Queue. Then another Mule-app(and muleflow) receives the message (one-way as well) and transform it to another format and put it on another queue. Maybe this doesn't make sense to you but in our environment it does. ;-) Then after receiving a response from a "third party" The second Mule-app receives a response and transform the JMS Message into our own format(we still have the properties with us). Now send it to a topic where the first Mule-app (and a 2nd flow) (or anyone else) can get the message. No we want to respond to the caller. We have properties on who sent the request and to what queue he wants the response to. So all 4 mule-flows(in 2 different mule-apps) are all setup as "one-way" because we want it asynchronous and not a response directly because there are several steps (and queues) on the way.</p>
  
  <p>So we have the actual flow is going from Flow 1 to Flow 3 to external party and then getting a response in Flow 4 and then back to Flow 2 to the caller.</p>
  
  <p>So Flow1->Flow3->Flow4->Flow2</p>
  
  <p>Mule-app1:</p>
  
  <p>Flow1:
  Caller -> Queue -> MuleFlow(one-way) -> Queue</p>
  
  <p>Flow2:
  Topic -> MuleFlow (one-way) -> Reponse to the Temp-queue</p>
  
  <hr>
  
  <p>Mule-App2</p>
  
  <p>Flow3: 
  Queue -> Muleflow(one-way) -> Transform -> Queue -> External Part</p>
  
  <p>Flow4:
  External Part -> Queue-> MuleFlow(one-way) -> Transform -> Topic </p>
  
  <p>I hope you can follow me on this.</p>
  
  <p>I guess the Mule Studio has put those "Processor Chains" there. And the logging is just "logging". I want to know when leaving Flow1 and so on. Just for log/debug.</p>
  
  <p>Thank you for you considerations in this matter.</p>
  
  <p>/Z</p>