Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6983710D73 for ; Wed, 2 Apr 2014 21:49:50 +0000 (UTC) Received: (qmail 53110 invoked by uid 500); 2 Apr 2014 21:49:20 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 52390 invoked by uid 500); 2 Apr 2014 21:49:15 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 52379 invoked by uid 99); 2 Apr 2014 21:49:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2014 21:49:15 +0000 Date: Wed, 2 Apr 2014 21:49:15 +0000 (UTC) From: "Hadrian Zbarcea (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-5054) Display the number of active transactions and age of oldest transaction on a Connection's JMX info MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5054: --------------------------------- Fix Version/s: 5.9.1 > Display the number of active transactions and age of oldest transaction on a Connection's JMX info > -------------------------------------------------------------------------------------------------- > > Key: AMQ-5054 > URL: https://issues.apache.org/jira/browse/AMQ-5054 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Reporter: Hiram Chirino > Assignee: Hiram Chirino > Fix For: 5.9.1, 5.10.0 > > > Long running transactions can affect the ability of KahaDB to gc log files. Being able to identify which connections have the long running transactions would operations folks deal with these problems. -- This message was sent by Atlassian JIRA (v6.2#6252)