This content has been marked as final. Show 6 replies
Have you checked whether the bridges work when no selector is specified?
If so, can you post your selector strings?
The bridge works well without Selector, my selector entry is Two it is not boolean expression. I am sending message to source code as Two Test data. As i have selector as Two, my message as well contains Two.
Now bcos of selector, for the above message, the data is not moving to destination queue.
The expected selector syntax is the standard SQL-like JMS syntax. There's an extensive description of the syntax in the javadoc for javax.jms.Message.
Selectors should normally only reference message header fields and message properties. I don't normally recommend using a selector that is based on message body as this requires using a proprietary WebLogic extension based on "xpath" XML expressions, and can have an large impact on performance. (The performance hit is caused by two factors - the need for the JMS server to unmarshal/decompress/page-in the body in order to get at its contents, and the natural cost of scanning a message body to see if it matches a string.)
JMS Selectors normally work om jms headers and not on the message.1 person found this helpful
Apart from the normal headers like corelationid, timestamp, Message id, priority...
JMS allows you to keep additional name value pairs As properties which you can use in the selector.
When creating the message add appropriate proprerties which will help you to use selectors effectively
JMS Selectors normally work om jms headers and not on the message.In my previous post I note that WebLogic provides an "xpath selector" extension in this area, although I recommend using standard selectors whenever possible. See my previous post for details about selector syntax, etc. The best resource on selectors is the javadoc for javax.jms.Message (http://docs.oracle.com/javaee/5/api/javax/jms/Message.html).