Hi Holger,

The selector expression you have provided in your post is correct and
should work with Qpid JMS client.

I suspect that in your java code you specified wrong quotes.

Could you please check in you code that standard ACII single quotes
are used in a selector expression?

Kind Regards,
Alex

On 29 August 2012 12:00, Caesar Holger (KGQI 1)
<[email protected]> wrote:
> The full output is:
>
> javax.jms.InvalidSelectorException: cannot create consumer because of
> selector issue
> at
> org.apache.qpid.client.BasicMessageConsumer_0_10.<init>(BasicMessageCons
> umer_0_10.java:95)
>         at
> org.apache.qpid.client.AMQSession_0_10.createMessageConsumer(AMQSession_
> 0_10.java:545)
>         at
> org.apache.qpid.client.AMQSession_0_10.createMessageConsumer(AMQSession_
> 0_10.java:87)
>         at
> org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2067)
>         at
> org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2040)
>         at
> org.apache.qpid.client.AMQConnectionDelegate_0_10.executeRetrySupport(AM
> QConnectionDelegate_0_10.java:369)
>         at
> org.apache.qpid.client.AMQConnection.executeRetrySupport(AMQConnection.j
> ava:586)
>         at
> org.apache.qpid.client.failover.FailoverRetrySupport.execute(FailoverRet
> rySupport.java:102)
>         at
> org.apache.qpid.client.AMQSession.createConsumerImpl(AMQSession.java:203
> 8)
>         at
> org.apache.qpid.client.AMQSession.createConsumer(AMQSession.java:1004)
>         at general.Sub.<init>(Sub.java:128)
>         at general.Sub.startTest(Sub.java:432)
>         at general.TestCase.runTestCase(TestCase.java:73)
>         at general.TestCase.main(TestCase.java:205)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:57)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:616)
>         at
> org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader
> .java:58)
>
>
> -----Original Message-----
> From: Gordon Sim [mailto:[email protected]]
> Sent: Mittwoch, 29. August 2012 12:55
> To: [email protected]
> Subject: Re: Evaluation of requirements
>
> On 08/29/2012 10:52 AM, Caesar Holger (KGQI 1) wrote:
>
>>>> 8) SQL92-compliant message selectors as defined in the JMS standard
>> are not
>>>> supported
>>> They are not yet supported by the c++ broker, but the JMS client can
>>> evaluate them on the client side. So logically the feature is there,
>>> though less efficiently implemented than if they were evaluated
> server
>> side.
>> I tried using a message selector in the client using an SQL92
> compatible
>> string from the Oracle JMS API ("NewsType = 'Sports' OR NewsType =
>> 'Opinion'"). However I get the following exception:
>> "javax.jms.InvalidSelectorException: cannot create consumer because of
>> selector issue"
>> Do you have any idea why this is?
>
> No, I don't see why that should be invalid. Its not a particularly
> helpful error message either... Was there a linked exception tied to
> that with any more detail.
>
> Anyone on the JMS side able to suggest anything here?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to