Possible bug with Mule AMQP transport 3.6.2 community
问题 I've been tracking down some strange behavior and I've finally managed to isolate it, and I believe that it is a bug. To reproduce the behaviour I have created 4 test flows (in 4 different mule files): <flow name="testhttpFlow"> <http:listener config-ref="HTTP_Listener_AMIAB" path="/testsend" allowedMethods="GET, POST" doc:name="HTTP"/> <amqp:outbound-endpoint exchangeName="AMQP.DEFAULT.EXCHANGE" routingKey="masterMeep" exchangeType="direct" responseTimeout="10000" exchange-pattern="request