Hi Andreas, I fixed this in the Apollo [1] implementation of the STOMP protocol. The selector evaluation automatically casts Strings to Ints as needed to make the comparison work. We would need to double check that this is allowed in the JMS spec before doing the same change in ActiveMQ so that we don't break JMS compatibility there.
[1]: http://activemq.apache.org/apollo/ Regards, Hiram FuseSource Web: http://fusesource.com/ Connect at CamelOne May 24-26 The Open Source Integration Conference On Tue, Apr 12, 2011 at 10:55 AM, andras <andras.szerdahe...@netmining.com> wrote: > Hello all, > > i am trying to set up a header in my messages (submitted to my activemq > queue through STOMP) for selecting (in a polling consumer/worker) only items > with a numeric value in this header that is lower than the current > microtime. However, as i understand every header coming from a STOMP message > will be treated as String and no attempt is made to parse numeric values > into an integer type > > So my question(s).. > > - am i wrong and is this actually happening and the problem is.. in.. my.. > selector? ( header>123 - thats difficult to screw up, right ) > - should i be using scheduling and delay the actual insertion of these > messages? Are "scheduled" messages persisted if i have a persistence > provider configured ( kaha ) ? How does having hundreds of thousands of > messages scheduled for the same 1-2 seconds affect load on the broker? > worse/better than straight insertion? do i effectively double my load with > this? > - should i just modify the Stomp transport so it runs a simple regex on the > header values and casts to Int as necessary ? > > thanks! > Andras > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Integer-header-in-STOMP-submitted-message-for-numeric-selector-header-n-string-tp3444817p3444817.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
