Anyone?
bonnyr wrote:
As per subject, if all messages in a queue have been delivered, is there a
housekeeping
mechanism to shrink the index files (in particular the
hash-index-queue-data_... and index-queue-data
files)?
I can see resizing messages as the queue grows, but could
As per subject, if all messages in a queue have been delivered, is there a
housekeeping
mechanism to shrink the index files (in particular the
hash-index-queue-data_... and index-queue-data
files)?
I can see resizing messages as the queue grows, but could not see the
reverese happening. We are
rajdavies wrote:
just for clarification - do you mean all messages delivered to the the
MessageConsumer would be acked on WINDOW_ACK instead of Session wide ?
On 10 Feb 2009, at 23:42, bonnyr wrote:
Rob,
Can I hijack this issue and bring back an issue I have filed in Jira
,
Bonny
Gary Tully wrote:
Bonnie,
in CLIENT_ACK, the list is used on close to deal with duplicate
suppression, these messages will
get redelivered so they need to be removed from audit that tracks
their receipt. That logic is at fault.
Cheers,
Gary.
2009/2/9 bonnyr bon
- agreed - looks like that bit of code has never been
synchronized - will add a fix ...
cheers,
Rob
Rob Davies
http://fusesource.com
http://rajdavies.blogspot.com/
On 9 Feb 2009, at 23:14, bonnyr wrote:
Gary,
Why would the collection be used in CLIENT_ACK mode then?
In our
in a Junit
tests case I think. Could you raise a jira issue for this and if you
have some tests code that demonstrates, please include it.
for more info see: http://activemq.apache.org/contributing.html
Thanks,
Gary.
2009/2/6 bonnyr bon...@optusnet.com.au:
AMQ 5.1 (but problem exists
a jira issue for this and if you
have some tests code that demonstrates, please include it.
for more info see: http://activemq.apache.org/contributing.html
Thanks,
Gary.
2009/2/6 bonnyr bon...@optusnet.com.au:
AMQ 5.1 (but problem exists in the sources of AMQ-5.2 as of today)
My setup
AMQ 5.1 (but problem exists in the sources of AMQ-5.2 as of today)
My setup:
* Broker is configured with a single queue, full with messages, on a host
accessible via the network.
* Application configured with a single consumer, connected to a single
sesssion, running in its own thread.
*
AMQ 5.1 (but problem exists in the sources of AMQ-5.2 as of today)
My setup:
* Broker is configured with a single queue, full with messages, on a host
accessible via the network.
* Application configured with a single consumer, connected to a single
sesssion, running in its own thread.
*
the broker, producers and consumers into a single
java application so that it can be converted into a junit test case it
would be great.
The key to pining this down is the reproducible test case. 1000 m/s
and/or running on a single host should not be a problem.
2008/11/13 bonnyr [EMAIL PROTECTED
Gary,
Thanks for the pointers. I'll try those. In the meantime I'm having other
issues...
I've cleared up the data directory in the broker area (we're using kaha for
persistence)
and restarted the test. I am not able to create the error again !?
However, I've noticed another, more depressing
All,
We've been using AMQ for a while now, and wanted to test the upcoming
release to see if it resolved
a problem we're having with the current version we're using (5.1.0), so I've
setup a test to try
and create the problem in my test environment.
My setup is:
---
1 producer,
bump
--
View this message in context:
http://www.nabble.com/How-to%3A-Slow-consumers-and-CLIENT_ACKNOWLEDGE--tp18356204p18380884.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
All,
We're using AMQ as follows:
A producer is connected to it's own (almost embedded) broker to deliver
messages reliably (using
kaha persistence)
A consumer is connected to the broker and sets the ack mode to
CLIENT_ACKNOLEDGMENT. The
consumer is itself multi threaded and the thread that
14 matches
Mail list logo
