Queues seem to be paused when part of a Topic (Core API)

[ebuddy]

Hi,

I have implemented a topic with the Core api. I created an address and four queues on top of that, the queues are all durable. I am starting up 4 clients that all consume one queue and send to the underlying address. They send a message every two seconds with an expiry of 2 seconds in the future.

The first client I start works fine, I receive my own message via the topic. Now when I start up the next client I see it's messages coming in to the first client but the consumer doesn't seem to work. If I then go to the JMX console and tell the queue to "resume" I will start to receive messages as normal.

All these clients are running on the same machine (different processes) and the HornetQ is running standalone (non-distributed).

Any ideas of what could be wrong?

Thanx

Joost

[timfox]

I'm not sure I understand your explanation. Could you post some code that demonstrates the issue?

Also, you didn't mention what version you are using.

[ebuddy]

Aha, I found this thread:  http://community.jboss.org/message/546753#546753

And enabled flow control and everything seems to work. It does seem strange to me that you would need (consumer) flow control to get this to work?

Kind regards

Joost

[ebuddy]

Hi Tim,

Thanx for the prompt reply! I'm using 2.1.0.Final.

Enabling flow control seems to fix the issue.. Can you explain why I would need flow control to get this to work or is this a possible bug?

Joost

p.s. I am indeed creating and starting the session before I create the consumer

[timfox]

Like it says on the thread you found, this is a bug and it's already fixed.

You don't need to enable flow control if you have the fix. Enabling flow control is a workaround.

There's not usually a good reason for disabling flow control though.

[ebuddy]

Ok thanx,

I think I disabled flow control for my performance tests but I agree normally you probably want it on. Will there be a 2.1.1 that contains this fix or are you saving it for the next update?

Joost

[timfox]

Issues are fixed in TRUNK and go into the next release. (BTW, 2.1.1 was released a couple of weeks ago)

You can see the release version for any fix by viewing the issue in JIRA and looking at the fix version field.