Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: JDBC Persistance
Date: Mon, 2 Apr 2007 10:56:34 -0700
Message-ID: <6B610AB57E31514E87F9DF80F8EA6AA1017CAE11@dc01.transerainc.com>
In-Reply-To: <ec6e67fd0704020844u32d942d2j8a0bdf68400dfa2b@mail.gmail.com>
Thread-Topic: JDBC Persistance
Thread-Index: Acd1Pc798pMOPBcOTgiuilRm55UHfgAEen2A
From: "Ramesh Bobba" <ramesh@transerainc.com>
To: <users@activemq.apache.org>

Hi James,

Is 4.2 production ready? Also, I switched the JDBC from mysql to
embedded derby db. I still see the disk growth. Is it possible to get
the cleanup of records in the db to happen faster? I guess I am asking
if there is any configuration parameters that I can set? The CPU usage
is minimal. Its just that we produce large sized messages.

I can't use queues because the number of clients varies and they all
want the same data.


Thanks,

Ramesh.

-----Original Message-----
From: James Strachan [mailto:james.strachan@gmail.com]=20
Sent: Monday, April 02, 2007 8:44 AM
To: users@activemq.apache.org
Subject: Re: JDBC Persistance

There is a lag if using the journal based on the journal checkpoint
time; so using pure JDBC and no journal will use less disk (though be
much slower). Also there is a further lag if you are using durable
topics (since the deletion of messages is a background task). You
might want to use queues if you want more immediate deletion & freeing
of resources.

Finally using AMQStore in 4.2 should use less disk space than a JDBC
database.


On 4/2/07, Ramesh Bobba <ramesh@transerainc.com> wrote:
> Hi James,
>
> I do want to use persistent delivery. The problem I am seeing is the
> messages from the persistent store are not being deleted fast enough.
My
> disk is getting full. Is there any way to control this? Do you think
> setAsyncSend(true) will help?
>
>
> Thanks,
>
>
> Ramesh.
>
> -----Original Message-----
> From: James Strachan [mailto:james.strachan@gmail.com]
> Sent: Monday, April 02, 2007 1:27 AM
> To: users@activemq.apache.org
> Subject: Re: JDBC Persistance
>
> On 4/1/07, Ramesh Bobba <ramesh@transerainc.com> wrote:
> > I have three producers producing 80K messages every 2 seconds, I
have
> > three consumers subscribed as durable consumers. I am using mysql as
> > persistence. What I see is that the messages are being written to
the
> > database even when all the subscribers are up.
> >
> > I thought that broker
> > only writes to the datasource if it has to.
>
> It does
>
> If you don't want persistence to take place, don't use persistent
> delivery.
>
http://cwiki.apache.org/ACTIVEMQ/what-is-the-difference-between-persiste
> nt-and-non-persistent-delivery.html
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>


--=20

James
-------
http://radio.weblogs.com/0112098/