can somebody confirm if this is really a bug? if it is, it looks like a
pretty serious one.
elliottjf wrote:
>
> Okay, from what I can tell, when using the ra activation spec driven
> consumer construction, the ConsumerInfo options where getting lost.
>
> Upon removing the err
Okay, from what I can tell, when using the ra activation spec driven consumer
construction, the ConsumerInfo options where getting lost.
Upon removing the errant 'this.' and rebuilding the activemq-core module,
things are now working for me.
snippet from org.apache.activemq.ActiveMQConnection.ja
I'm attempting to create a Jencks JCAConnector around a
"consumer.exclusive=true" marked queue, but the constructed consumer appears
to not be exclusive.
Has anybody attempted a similar use case or know why this shouldn't work?
I'm using Spring 2.0.2, ActiveMQ 4.1, and Jencks 2.0
Here are the r
any chance that this issue could be related to the behavior of "exclusive
consumer" queues on a distributed network? i'm still trying to figure out
if that is supported or not.
- joe
cbu wrote:
>
> NEW FINDING!
>
> if you set this policy - queue messages are not distributed on a network:
