Kahadb directory is not cleaned

Hi, i am using activemq 5.4 snapshot (resp. 5.3.1 snapshot) with kahadb in following use-case: - 3 durable topic subscriber, each refuses message using session.recover(), 3 delivery attempts - ActiveMQ.DLQ consumer - persistent message topic producer In such case deadletter consumer should cons

Re: low persistent messaging performance using kahadb

It seems enableJournalDiskSyncs="false" do the trick, but what does this setting actually do? Is it something i should worry about when disabling this feature? Dejan Bosanac wrote: > > Hi Duro, > > kahadb has some trade-offs for scalability and recovery speed vs. > p

low persistent messaging performance using kahadb

using kahadb with amq 5.3, amq 5.4 snapshot and 5.3.1 snapshot. Why is that? Is it possible to somehow configure kahadb (or message producer) to get better results? Duro -- View this message in context: http://old.nabble.com/low-persistent-messaging-performance-using-kahadb-tp26747184p26747184

Re: Memory limit reached on persistent queue

Thanks for answer but unfortunatelly none of these settings work for me despite that message size is only cca 25kb. Thierry H wrote: > > I > I had the same problem , and it seems that you have 2 issues on the 5.3 on > the subject. > I think your problem come from extensive memory usage related

Re: Memory limit reached on persistent queue

no, both versions behave as expected. Gary Tully wrote: > > Does the problem persist with trunk (5.4-SNAPSHOT) or on the 5.3.1-branch > (5.3.1-SNAPSHOT). > https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/ > > 2009/12/9 Duro &g

Memory limit reached on persistent queue

Hi, I'am using ActiveMQ 5.3 with kahaPersistenceAdapter my test case is: - slow consumer(s) - fast producer - persistent queue - producerFlowControl="true" - Win XP (Sles10) after couple thousand of massages stored massages i can find following massge on console: INFO | Usage Manager memory lim

Performace of AMQ 5.3 Broker decreasing with number of stored presistent msgs.

Hello, when I've tried to store more than 500k persistent messages to queue using kahaPersistenceAdapter I've realized that rate of sending immediately falls from cca. 4000msgs/s to cca. 700msgs/s. There is no significant change in heap space usage at this point MemoryPercentUsage is also same as

Problem with setting memoryUsage when using persistent messaging with slow consumers

Hello, i have some problems with configuration when using persistent queue. I have following scenario: - broker running on SUSE Linux Enterprise Server 10 SP1 (x86_64) - Xmx for broker VM set to 800MB - tcp transport - client messages (over 500k msgs * 20kB per msgs) - 4 receivers with Client_Ack

TimeToLive cominated with redelivery hangs

Hi, Using TimeToLive on message producer with redelivery mechanism seems to have a problem. When message expires between delivery and first redelivery (after first calling session recover() - CLINET_ACK) clinet stops to receive and messages aren't post even to DLQ. Any further sending has no effec

Re: persistent messages for durable subscribers are not purged from disc

It looks that there is a problem in activemq journal wich is used by default amqPersistenceAdapter. I have tested this also on amq 4.1.1 journaledJDBC adapter with same bug. When jdbcPersistenceAdapter with 4.1.1(non-journal) or kahaPersistenceAdapter with 5.1 are used with 2 durable topic subscri

Re: persistent messages for durable subscribers are not purged from disc

Hi, I have created jira with two simple java classes. AMQ-1797. rajdavies wrote: > > Hi juraj, > > could you create a jira - with a junit test case attached ? > > thanks, > > Rob > On 12 Jun 2008, at 13:48, Duro wrote: > >> >> Hi all, >

persistent messages for durable subscribers are not purged from disc

Hi all, I have some problems with multiple durable subscribers while persistent delivery is used. If I understand concept of durable/persistent subscription, message should be deleted from disc storage (periodically) after all interested subscribers have received it. In case there was one durable

max redelivery with JMSExpiration

Hello, I have noticed that if I am trying to set maximumRedelivery using RedeliveryPolicy on message consumer, and there is "time to live" for message set on producer, there is possible to receive message even if it is expired. I am using transacted as well as Client_ACKNOWLEDGE mode. Is this a bu