[ https://issues.apache.org/activemq/browse/AMQ-980?page=all ]
Rob Lugt reopened AMQ-980:
--------------------------
It transpires this is a bug/feature in the .Net client.
The broker correctly dispatches the last image messages to the client, but the
client receives them before the call to Session.CreateConsumer() completes, so
it has not yet had a chance to register its listener. The messages are queued,
and when the client does eventually register its listener, it starts to
dispatch the queued messages. However only one (or perhaps several) messages
are dispatched due to a "fix" we put in recently to prevent thread starvation.
This problem will be rectified if we have a dedicated dispatching thread per
session.
> lastImageSubscriptionRecoveryPolicy does not work with wildcards
> ----------------------------------------------------------------
>
> Key: AMQ-980
> URL: https://issues.apache.org/activemq/browse/AMQ-980
> Project: ActiveMQ
> Issue Type: Bug
> Components: NMS (C# client)
> Affects Versions: 4.0.2
> Environment: Windows, JDK 1.5
> Reporter: Rob Lugt
> Fix For: 4.1
>
>
> The lastImageSubscriptionRecoveryPolicy does not appear to work with
> wildcards.
> In the following example, a new consumer only receives one message for the
> topics covered by the wildcard instead of receiving one message for each
> topic.
>
> config file:-
> <policyEntry topic="PRICES.>">
> <subscriptionRecoveryPolicy>
> <lastImageSubscriptionRecoveryPolicy/>
> </subscriptionRecoveryPolicy>
> </policyEntry>
>
> consumer subscription:-
> GetTopic("PRICES.>?consumer.retrocactive=true");
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
