kalki70 wrote:
Hello,
We are having a problem when using Activemq-cpp (version 2.2.6). This
problem happens with Stomp and Openwire.
We create thousands of message groups dynamically : Create a message
group, send several messages, close message group. The producer is a C
Timothy Bish wrote:
On Tue, 2009-12-01 at 05:57 -0800, kalki70 wrote:
kalki70 wrote:
Hello,
We are having a problem when using Activemq-cpp (version 2.2.6). This
problem happens with Stomp and Openwire.
...
No one has any idea about this problem? We are really
kalki70 wrote:
.
Do you have any idea about when ActiveMQ decides to reassign a Message
Group ? As I said before, when the consumer takes longer to respond, we
see a lot more of these issues. I understand that JBoss doesn't
acknowledge the messages when he consumes them
Hello,
We are having a problem when using Activemq-cpp (version 2.2.6). This
problem happens with Stomp and Openwire.
We create thousands of message groups dynamically : Create a message group,
send several messages, close message group. The producer is a C++
application, the consumer is two
Hi, Dejan,
My opinion is that the functionality of Message Groups is partially broken
if there is no automatic recovery. What should the user do? Restart ActiveMQ
? :-(
I don't think it is so hard to implement. Upon subscription the consumer
could be informed its consumer id, which can be an
Hi, Dejan,
I agree consumers don't know which groups they will be assigned. As you
said, if a consumer goes down, other will take those groups, but the problem
comes when the consumer that went down comes back again. It will never
receive any more messages. So what I proposed was something like
Hi,
I have been looking at this feature, that so far looks great for our
applications.
If I have several consumers, messages with specific JMSXGroupId are routed
to the same consumer.
If a consumer fails, its message groups are now reassigned to a different
consumer, so the service keeps
