Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 213A517FA7 for ; Mon, 28 Sep 2015 14:44:30 +0000 (UTC) Received: (qmail 91247 invoked by uid 500); 28 Sep 2015 14:44:20 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 91208 invoked by uid 500); 28 Sep 2015 14:44:20 -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 91192 invoked by uid 99); 28 Sep 2015 14:44:20 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Sep 2015 14:44:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8B20DC6A75 for ; Mon, 28 Sep 2015 14:44:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.869 X-Spam-Level: ** X-Spam-Status: No, score=2.869 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=wellsfargo.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id loYoCQCDlYla for ; Mon, 28 Sep 2015 14:44:08 +0000 (UTC) Received: from mxdcmx01e.wellsfargo.com (mxdcmx01e.wellsfargo.com [167.138.239.98]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 144C842B5D for ; Mon, 28 Sep 2015 14:44:08 +0000 (UTC) Received: from mxidlv02.wellsfargo.com (mxidlv02.wellsfargo.com [162.101.146.198]) by mxdcmx01e.wellsfargo.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id t8SEhQUh005758 for ; Mon, 28 Sep 2015 14:44:01 GMT DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wellsfargo.com; s=2011-05-wfb; t=1443451441; bh=AyHhrsyCBWq3FmBgr11RbN3xybRvSpnM2MgCuaV6GRg=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=k4VjN1WmSVzIqyFqY9FW4Tg8PfByGp7hOS/BNR8AoAR+t/lMUiJVpt/uqu8WI9AwV Z8EQnm31mDKluoT66eTmSMUyoYUTBsZWxT8BgzxWHn6U7tJkvUH4sPArKrAAPjaD5V HEVABovFLCKFHJAZufZeuJqI9Ji6NbZpqau0eQHo= Received: from mxidli01.wellsfargo.com ( [162.103.179.209]) by mxidlv02.wellsfargo.com (postmaster@wellsfargo.com) with SMTP id B8.33.08775.F2259065; Mon, 28 Sep 2015 15:43:59 +0100 (BST) X-AuditID: a26592c6-f798e6d000002247-a6-5609522fca04 Received: from mxicmx01.wellsfargo.com ( [162.102.137.58]) by mxidli01.wellsfargo.com (postmaster@wellsfargo.com) with SMTP id 2E.85.01422.F2259065; Mon, 28 Sep 2015 15:43:59 +0100 (BST) Received: from MSGEXSIL4101.ent.wfb.bank.corp (msgexsil4101.wellsfargo.com [162.103.216.30]) by mxicmx01.wellsfargo.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id t8SEhixN005445 for ; Mon, 28 Sep 2015 14:43:58 GMT Received: from MSGEXSIL1119.ent.wfb.bank.corp ([169.254.1.12]) by MSGEXSIL4101.ent.wfb.bank.corp ([162.103.216.30]) with mapi id 14.03.0224.002; Mon, 28 Sep 2015 10:43:54 -0400 From: To: Subject: Nothing on queues, Journal files not getting cleaned up Thread-Topic: Nothing on queues, Journal files not getting cleaned up Thread-Index: AdD5/BXxYj6Y+MUwRjmfzK4bgCOdeQ== Date: Mon, 28 Sep 2015 14:43:53 +0000 Message-ID: <443BCE38E921434394B45FF0813FA578504A4504@MSGEXSIL1119.ent.wfb.bank.corp> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [170.13.180.70] Content-Type: multipart/alternative; boundary="_000_443BCE38E921434394B45FF0813FA578504A4504MSGEXSIL1119ent_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKIsWRmVeSWpSXmKPExsWyKO1Ctq5BEGeYwbUmJYuT92YwOTB6dNw7 yBbAGKVok5Kak1mWWqRvZ5NUWZBYXKybnKaQmJNjq1RSVJqqpG+XoJgxd0cPU8En/oqVT2ew NDDu5e1i5OSQEDCR2DpnMTOELSZx4d56ti5GLg4hgb2MEq3TGlhhim4enMEKkdjDKHHm7mQm COc/o8SFqSuYIZwtjBK/Op8xgrSwCahI7J+4AMwWEZCXuHf2HguILSzgILHky19WiLirxNwt 34CaOYBsPYmLk/lBwiwCqhKfN84AK+EVCJW4OOMumM0IdN73U2uYQGxmAXGJW0/mM0FcJyCx ZM95qBdEJV4+/gd1taLE5dOf2CDq8yUuzdzKBDFTUOLkzCcsIDdLCLSzSyztW8QI0SAkMfXC InYIW1Li4IobLBMYJWYh2TcLyaxZSGZBxHUkFuz+xAZha0ssW/iaGcY+c+AxE7L4Akb2VYzi uRWZKTllBkZ65ak5OcVpiUXp+XrJ+bmbGEGxnTrp2A7GRUucDzEKcDAq8fAeW2MbKsSaWFZc mXuI0RQYShOZpUST84EJJK8k3tDEwMLY0sTUyNDU0kRJnHc6SLFAemJJanZqakFqUXxRaU5q 8SFGJg5OqQbGjb5frzKFZui+tl9V6XJ3UuThbaquOR/dE0o9HP7/P32zT+qlbe+BCFa+DOMq uemfDKz+r5Xren6g9enBO1LCYX6BT5N1F6gHfLqyvsw5mdN96W1d1a/FnxrZmEwMFKIf/Frb vFj6se7+INYAabZrWxlKug2vGr77c0nxy6FSw453KrGlno1KLMUZiYZazEXFiQBQBEnx6AIA AA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGIsWRmVeSWpSXmKPExsWyKK3TSlc/iDPMYOsybouT92YwOTB6dNw7 yBbAGOVgk5GamJJapJCal5yfkpmXbqvkGeyva2FhaqlrqKSQl5ibaqsUoRvu5qTr4hOgG+Lv rqRQlphTChSNdA1W0rdLcMiYu6OHqeATf8XKpzNYGhj38nYxcnJICJhI3Dw4gxXCFpO4cG89 WxcjF4eQwB5GiTN3JzNBOP8ZJS5MXcEM4WxhlPjV+YwRpIVNQEVi/8QFYLaIgLzEvbP3WEBs YQEHiSVf/rJCxF0l5m75BtTMAWTrSVyczA8SZhFQlfi8EWIzr0CoxMUZd8FsRqArvp9awwRi MwuIS9x6Mp8J4joBiSV7zjND2KISLx//g7paUeLy6U9sEPX5EpdmbmWCmCkocXLmE5YJjMKz kIyahaRsFpIyiLiOxILdn9ggbG2JZQtfM8PYZw48ZkIWX8DIvopRPLciMyUn08BQrzw1J6c4 LbEoPV8vOT93EyMoOtM3X9zB2LbE+RCjAAejEg9v3q8JIUKsiWXFlbmHGE2BATCRWUo0OR+Y AvJK4g1NDCyMLc0NTM0sjcyUxHlln9qFCgmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamDs5Ln/ 6Me0rlfsM4vyKiTsBf2DDJO+vvdPZbpyztJCb1Upj9KVSl6muh9yFzy9I+d07Nro8aXWILOW 4eaZ/UZK+x3Ut/JnMUotij/2avffLqmpFpdy1llpG3AtzT77ICowNUzwuu6TmIj3Sw1SP65z M5JqXlRnMMO5Kn2DWeDnMyut6ziCupVYijMSDbWYi4oTAQ7vj8zJAgAA X-WFB-DLP-TOG: YES X-CFilter-Loop: Reflected --_000_443BCE38E921434394B45FF0813FA578504A4504MSGEXSIL1119ent_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, How is it that our journal files continue to grow, yet no messages are on t= he queues? ActiveMQ 5.11.1, Using KahaDB (not levelDB). How can you tell if a kahaDB scheduler is waiting, and in need of clearing? Nothing on the Advisory queues (no network of brokers), nothing on the DLQ.= Where else can I look? Our txlogs are very large as well. Application T= eams advise their transaction processing IS committing on gets and puts, et= c.. Regards, Barry --_000_443BCE38E921434394B45FF0813FA578504A4504MSGEXSIL1119ent_--