[jira] Issue Comment Edited: (AMQ-1806) Selectors are not working properly

["Jarl Totland (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/AMQ-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43902#action_43902 ] 

jarl edited comment on AMQ-1806 at 7/3/08 5:03 AM:
-----------------------------------------------------------

We also have this issue, using ActiveMQ 5.1.0 and 5.2-SNAPSHOT-20080619 on Windows.
Both as embedded and using the default runtime environment, 
using both Kaha and Jdbc(DB2) persistence,
using a single or multple consumers.

This works fine with ActiveMQ 5.0.0.

To reproduce, put the following in a queue:
  100 messages matching your selector
  100 messages not matching your selector
  100 messages matching your selector

The consumers only retrieve the first 100 messages.

Using 98 instead of 100 messages above seems to always work correctly.
With 99 messages we have mixed results.


      was (Author: jarl):
    We also have this issue, using ActiveMQ 5.1.0 and 5.2-SNAPSHOT-20080619 on Windows.
Both as embedded and using the default runtime environment, using both Kaha and Jdbc(DB2) persistence.

This works fine with ActiveMQ 5.0.0.

To reproduce, put the following in a queue:
  100 messages matching your selector
  100 messages not matching your selector
  100 messages matching your selector

The consumer only retrieves the first 100 messages.

Using 98 instead of 100 messages above seems to always work correctly.
With 99 messages we have mixed results.

  
> Selectors are not working properly
> ----------------------------------
>
>                 Key: AMQ-1806
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1806
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>         Environment: Solaris 10
>            Reporter: vik dhawan
>             Fix For: 5.2.0
>
>
> Hi i am testing Selectors on AMQ5.2 latest SNAPSHOT and under the load conditions where lot of consumers are trying to run Selector based messages pull. Its failing and not returning the messages. 
> Similar problem exists in the AMQ5.1 release version but i don't think any body paid any attention to it yet. 
> This is causing a lot of problem at my end. 
> PS: Just to give you point of reference this was working fine in 5.0 Release. 
> any help will be appreciated. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.