Global Variable
2012-07-02 23:46:24 UTC
I have the same issue... I am on MULE standalone 3.3 (released).
<br /><br />
I have a flow which sets JMS properties in a JMS outbound endpoint:
<br />
<code>
<br />
<flow>
<br />
<jms:outbound-endpoint queue="XXX" exchange-pattern="request-response" connector-ref="jmsConnector">
<br />
<message-properties-transformer>
<br />
<add-message-property key="operation" value="destroySession"/>
<br />
</message-properties-transformer>
<br />
</jms:outbound-endpoint>
<br />
...
<br />
...
<br />
</flow>
<br />
</code>
<br /><br />
When I go to my ActiveMQ queues, I see the message and it has the property set correctly.
<br /><br />
Now I have another JMS inbound-endpoint which has a corresponding selector defined:
<br />
<code>
<br />
<flow>
<br />
<jms:inbound-endpoint queue="XXX" exchange-pattern="request-response">
<br />
<jms:selector expression="operation=destroySession" />
<br />
</jms:inbound-endpoint>
<br />
</flow>
<br />
</code>
<br /><br />
Again, in ActiveMQ Queues I see that the consumers have the right selector property. But the messages keep on accumulating, never get collected.
<br /><br />
My question is:
<br />
1. Is this the right pattern to set JMS messages properties and having consumers filter the messages based on properties?
<br />
2. If not, what is the right pattern?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
<br /><br />
I have a flow which sets JMS properties in a JMS outbound endpoint:
<br />
<code>
<br />
<flow>
<br />
<jms:outbound-endpoint queue="XXX" exchange-pattern="request-response" connector-ref="jmsConnector">
<br />
<message-properties-transformer>
<br />
<add-message-property key="operation" value="destroySession"/>
<br />
</message-properties-transformer>
<br />
</jms:outbound-endpoint>
<br />
...
<br />
...
<br />
</flow>
<br />
</code>
<br /><br />
When I go to my ActiveMQ queues, I see the message and it has the property set correctly.
<br /><br />
Now I have another JMS inbound-endpoint which has a corresponding selector defined:
<br />
<code>
<br />
<flow>
<br />
<jms:inbound-endpoint queue="XXX" exchange-pattern="request-response">
<br />
<jms:selector expression="operation=destroySession" />
<br />
</jms:inbound-endpoint>
<br />
</flow>
<br />
</code>
<br /><br />
Again, in ActiveMQ Queues I see that the consumers have the right selector property. But the messages keep on accumulating, never get collected.
<br /><br />
My question is:
<br />
1. Is this the right pattern to set JMS messages properties and having consumers filter the messages based on properties?
<br />
2. If not, what is the right pattern?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email