Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 3692 invoked from network); 24 Aug 2006 11:01:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Aug 2006 11:01:39 -0000 Received: (qmail 48903 invoked by uid 500); 24 Aug 2006 11:01:39 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 48710 invoked by uid 500); 24 Aug 2006 11:01:38 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 48699 invoked by uid 99); 24 Aug 2006 11:01:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Aug 2006 04:01:38 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Aug 2006 04:01:37 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GGCxY-0007Cs-RZ for activemq-users@geronimo.apache.org; Thu, 24 Aug 2006 04:01:16 -0700 Message-ID: <5961729.post@talk.nabble.com> Date: Thu, 24 Aug 2006 04:01:16 -0700 (PDT) From: pradeep To: activemq-users@geronimo.apache.org Subject: Re: INFO Service - Sync error occurred: java.lang.Ou In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <5943593.post@talk.nabble.com> <5959137.post@talk.nabble.com> <5960761.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I am sending messages using the method Messageproducer.send(message); By default, delivery mode is peristent right ? I am using Oracle database. > Please help me. Thanks, Pradeep James.Strachan wrote: > > We cache things in RAM since consumers will typically need to read the > message too. BTW you're using persistent messaging right? You're > setting the PERSISTENT flag on the producer's delivery mode? > > Are you using Derby? You could switch to another JDBC driver to avoid > the in-RAM JDBC driver using up RAM too. > > > On 8/24/06, pradeep wrote: >> >> James, >> >> When using JDBC persistence I am seeing that the messages are stored in >> memory even after being persisted in database. They are not getting >> removed >> and this is resulting in outofmemory error. >> If I am not wrong, in case of JDBCpersistence adapter the messages will >> not >> be kept in memory after being written to the db ? >> >> Pradeep >> >> James.Strachan wrote: >> > >> > Incidentally you could disable the journal if you have limited RAM and >> > are happy to trade performance for lower RAM usage... >> > >> > use instead in your XML like this example >> > >> > http://incubator.apache.org/activemq/jdbc-master-slave.html >> > >> > its much slower but doesn't require messages to be kept in RAM until a >> > checkpoint. >> > >> > >> > On 8/24/06, James Strachan wrote: >> >> Are you sure you are definitely setting the Java heap size? e.g. its >> >> usually -Xmx1000m not -xmx etc. If you watch the broker in JMX do you >> >> see it using up 1Gb of RAM when you only have a 100Mb usage manager >> >> setting? >> >> >> >> Note that ActiveMQ uses a high performance journal so that messages >> >> are only evicted from RAM when a checkpoint to JDBC occurs, not the >> >> exact second that a message is consumed. >> >> >> >> So you are sending 1000 messages to 5 topics of 100K. So thats about >> >> 500Mb of messages. So I'd try set your memoryManager to be 800mb and >> >> your Java heap to be about 2000M and that should work - use JMX to see >> >> how much memory its using and how many messages get sent to the >> >> queues. >> >> >> >> >> >> On 8/24/06, pradeep wrote: >> >> > >> >> > Thanks James. >> >> > I am using 4.0.1. I tried lowering the memory to 100MB. It did not >> >> work. >> >> > I increased the size to 400 MB, 800mb etc. >> >> > >> >> > It still gives me >> >> > Exception in thread "ActiveMQ Transport: tcp:///127.0.0.1:3116" >> >> > java.lang.OutOfMemoryError: Java heap space >> >> > >> >> > Why doesn't ActiveMQ remove the messages from memory when it has >> >> already >> >> > persisted messages into database. I am seeing the memory problem in >> >> > ActiveMQ and not other JMS server that I am evaluating. >> >> > James, can you please help me here. >> >> > >> >> > Pradeep >> >> > >> >> > >> >> > James.Strachan wrote: >> >> > > >> >> > > FWIW if you use ActiveMQ 4.1 you can configure the memory limit >> via >> >> > > >> >> > > >> >> > > >> >> > > On 8/23/06, James Strachan wrote: >> >> > >> That memory limit looks a bit big; its about 7Gb I'd maybe set it >> to >> >> > >> be around 100Mb insteead >> >> > >> >> >> > >> On 8/23/06, pradeep wrote: >> >> > >> > >> >> > >> > 1. Created a durable subsriber for 5 different topics and >> >> disonnected >> >> > >> the >> >> > >> > clients >> >> > >> > 2. Tried to send 1000 messages to each topic (message size >> =100kb) >> >> in >> >> > >> > parallel >> >> > >> > 5 threads were created each sending messages to different >> >> topics >> >> > >> > (Separate connection Factory lookup and topic lookup) >> >> > >> > I got this error this >> >> > >> > >> >> > >> > INFO Service - Sync error occurred: >> >> > >> > java.lang.OutOfMemoryError: Java heap space >> >> > >> > java.lang.OutOfMemoryError: Java heap space >> >> > >> > >> >> > >> > WARN JournalMessageStore - Message could not be >> added >> >> to >> >> > >> long >> >> > >> > term store: Java heap space >> >> > >> > java.lang.OutOfMemoryError: Java heap space >> >> > >> > >> >> > >> > >> >> > >> > I am running the activemq with -xms 256m -xmx1000m. >> >> > >> > activemq.xml has >> >> > >> > >> >> > >> > >> >> > >> > >> >> > >> > >> >> > >> > Why is the error coming ? >> >> > >> > -- >> >> > >> > View this message in context: >> >> > >> >> >> >> http://www.nabble.com/INFO--Service--------------------------Sync-error-occurred%3A-java.lang.Ou-tf2152180.html#a5943593 >> >> > >> > Sent from the ActiveMQ - User forum at Nabble.com. >> >> > >> > >> >> > >> > >> >> > >> >> >> > >> >> >> > >> -- >> >> > >> >> >> > >> James >> >> > >> ------- >> >> > >> http://radio.weblogs.com/0112098/ >> >> > >> >> >> > > >> >> > > >> >> > > -- >> >> > > >> >> > > James >> >> > > ------- >> >> > > http://radio.weblogs.com/0112098/ >> >> > > >> >> > > >> >> > >> >> > -- >> >> > View this message in context: >> >> >> http://www.nabble.com/INFO--Service--------------------------Sync-error-occurred%3A-java.lang.Ou-tf2152180.html#a5959137 >> >> > Sent from the ActiveMQ - User forum at Nabble.com. >> >> > >> >> > >> >> >> >> >> >> -- >> >> >> >> James >> >> ------- >> >> http://radio.weblogs.com/0112098/ >> >> >> > >> > >> > -- >> > >> > James >> > ------- >> > http://radio.weblogs.com/0112098/ >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/INFO--Service--------------------------Sync-error-occurred%3A-java.lang.Ou-tf2152180.html#a5960761 >> Sent from the ActiveMQ - User forum at Nabble.com. >> >> > > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/INFO--Service--------------------------Sync-error-occurred%3A-java.lang.Ou-tf2152180.html#a5961729 Sent from the ActiveMQ - User forum at Nabble.com.