Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <19018460.300211281602476494.JavaMail.jira@thor>
Date: Thu, 12 Aug 2010 04:41:16 -0400 (EDT)
From: "Damian Hofmann (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-4769) Log disconnects and count of active
 connections
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Log disconnects and count of active connections
-----------------------------------------------

                 Key: DERBY-4769
                 URL: https://issues.apache.org/jira/browse/DERBY-4769
             Project: Derby
          Issue Type: Improvement
          Components: Network Server
            Reporter: Damian Hofmann
            Priority: Minor


If the option "derby.drda.logConnections" is enabled, the network server logs new connections, but doesn't log disconnects. There seems to be no way to enable logging of disconnects. But having disconnects also logged would be useful to analyse, if applications do properly disconnect from the server or if there is a resource leak.

Maybe consider a second option (e.g. "derby.drda.logDisconnects") if you want to keep the existing option "pure".

It would also be helpful if the log shows how many connections are currently active or even better a list where one could see the active connections per database. This feature might be enabled using an option like "derby.drda.traceConnections"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.