Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 16629 invoked from network); 3 Mar 2009 12:30:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2009 12:30:33 -0000 Received: (qmail 63153 invoked by uid 500); 3 Mar 2009 12:30:31 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 63128 invoked by uid 500); 3 Mar 2009 12:30:31 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 63117 invoked by uid 99); 3 Mar 2009 12:30:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 04:30:31 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.220.170 as permitted sender) Received: from [209.85.220.170] (HELO mail-fx0-f170.google.com) (209.85.220.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 12:30:19 +0000 Received: by fxm18 with SMTP id 18so2573237fxm.38 for ; Tue, 03 Mar 2009 04:29:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=bKNCAZphHLSNhZzSIzw0j2ycDs2ej4aNWk4HzEqIZ+c=; b=GXDwFHwDqSbGAWgUfarW7iErOYadjPkM8pvWcNvpgMoyqS+nAWKPR9tMBQKXiIisKe FfEBw7mg/v1B0XshR/fa7PttUWZ6Q2zjfbrZ47d3tP+FOFHBGkaWrL3poKgTU5GoQtQE pvYoqwVduVVIJ9DrL0CHjplemodm8YR2ViAEk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ugSxWDP64rfKDRlY6dx41Q83s7yIFfNMVidHYyY2bi7XsPH3LoWdyB6eFJfq56TdYQ 9MNrjZ0nlEGZlttx85c/9ar3ZI4d4jzQAaPlOaTz0RxHZazwqRusjjeHFHL8YsZOIvyK phgB8dtoMqvs7qhn3O84bU8t7sbmCgsQBkXEg= MIME-Version: 1.0 Received: by 10.180.241.8 with SMTP id o8mr2528698bkh.102.1236083397284; Tue, 03 Mar 2009 04:29:57 -0800 (PST) In-Reply-To: <22300064.post@talk.nabble.com> References: <22300064.post@talk.nabble.com> Date: Tue, 3 Mar 2009 12:29:57 +0000 Message-ID: <3a73c17c0903030429y1cd494a3l3a8b36465476491b@mail.gmail.com> Subject: Re: Managing default persistence data? From: Gary Tully To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org There is no way to peek into internals of the sore on disk, but really there is internals of the data store are best left 'internal'. Using JMS browsers or the JMX api or the JMX Console it is possible to understand what is in the store. The broker has a deleteAllMessagesOnStartup attribute that will cause a broker to purge all existing messages on start. Also the JMXConsole and WebConsole support purging messages from particular queues or topics. What exactly do you want to achieve? 2009/3/3 klopus : > > Hi. I'm using AMQ 5.2, but same applies to 5.1 as well. =A0I use default > activemq.xml and thus default (built-in) Persistence Adapter that I > understand has its data store under "${activemq.base}/data" directory. > > I was wondering if there's any way to examine what records got stored the= re > and maybe delete some, etc. > > Sorry if that was asked before but I searched, honestly :) > > -- > View this message in context: http://www.nabble.com/Managing-default-pers= istence-data--tp22300064p22300064.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > --=20 http://blog.garytully.com Open Source SOA http://FUSESource.com