activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <>
Subject [jira] [Commented] (AMQ-5732) Changing message selector leads to blocking message
Date Mon, 20 Apr 2015 18:02:00 GMT


clebert suconic commented on AMQ-5732:

[~Cadmean] it looks like you are using the messaging provider as a database where you are
storing and retrieving data.. (storing file=X, Y and Z.. and later reading for the file you
want). This is the kind of thing a database is a better fit than a message system IMHO.

If you were always having a consumer active for your entire dataset you shouldn't have an
issue with paging...

This has been the case for any messaging system I have worked with.

This issue should be closed unless you provide a working testcase that shows this as an issue..
you start an empty server. Send a few messages and consume them accordingly showing the message
blocked without paging.

> Changing message selector leads to blocking message
> ---------------------------------------------------
>                 Key: AMQ-5732
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.11.1
>         Environment: Suse Linux 11 sp2
>            Reporter: Cadmean
>              Labels: features
> The problem is:
> 1. I create a queue in activemq broker (version 5.11.1) and some message with string
property, for example "filename".
> 2. Use a client to consume the message with message selector "filename='123.tar'" with
consumer.receive(),it works.  After it receive the message, it acks the message and send the
same message back to the broker and commit the session. (client_acknowledge). 
> 3. Use the same client, change the message selector to "filename='456.tar'" with consumer.receive(),
the consumer is blocked. 
> 4. restart the broker and consumer "filename='456.tar'" again, it successfully receive
the message, but if i change the selector back to "filename='123.tar'", it blocked again.
> At first I thought that there might be some rules for message dispatching. However, with
ActiveMQ version 5.10.0, the problem is gone.

This message was sent by Atlassian JIRA

View raw message