I'm not sure if it will help, but you could try disabling producer
flowControl:
<policyEntry topic=">" memoryLimit="5mb" producerFlowControl="false">
<dispatchPolicy>
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<noSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries>
It would also be interesting to know what ack mode your clients are using to
ACK their messages. Are you using CLIENT_ACK or AUTO_ACK?
If its easy to do, it might be worth running your test with a java consumer
and see if you see the same behaviour. This might allow you to narrow it
down to a problem on the consumer side.
Regards,
/Dave
On Mon, Aug 4, 2008 at 6:05 AM, Mike Gallaher <[EMAIL PROTECTED]>wrote:
>
> I forgot to mention that I am running 5.1.0.
>
> I'll try the latest snapshot, but as we're about to release our project I'd
> rather use a release version of ActiveMQ if possible. Writing
> non-persistent messages to a topic is such a basic use case that I thought
> I
> must be doing something wrong, but at least others are having the same
> problem.
>
>
> --
> View this message in context:
> http://www.nabble.com/QueueSize-and-InFlightCount-on-a-Topic-keeps-growing-tp18446149p18808516.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
