Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1642353066.1204705420860.JavaMail.jira@brutus>
Date: Wed, 5 Mar 2008 00:23:40 -0800 (PST)
From: "Bernt M. Johnsen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3435) Add an MBean for monitoring and
 managing the Network Server
In-Reply-To: <277570663.1203436963983.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575267#action_12575267 ] 

Bernt M. Johnsen commented on DERBY-3435:
-----------------------------------------

Dan & Knut: Thanks for the comments. I will fix the precision and threading issue with getBytesRecieved/sentPerSecond.
I agree that adding "Count" or "NumberOf" to attributes adds to usability. Personally I prefer "NumberOf" since I associate "Count" with an monotonous increasing counter. Furthermore "Session" is an implementation detail and for all purposes it maps to an java.sql.Connection, so I think "Connection" is a better name.

I suggest the following attributes:

NumberOfActiveConnections
NumberOfWaitingConnections
SizeOfConnectionThreadPool
ConnectionCounter

> Add an MBean for monitoring and managing the Network Server
> -----------------------------------------------------------
>
>                 Key: DERBY-3435
>                 URL: https://issues.apache.org/jira/browse/DERBY-3435
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JMX
>            Reporter: John H. Embretsen
>            Assignee: John H. Embretsen
>             Fix For: 10.4.0.0
>
>         Attachments: d3435_v01.diff, d3435_v01.stat, derby-3435-live-data-v0.diff, derby-3435-live-data-v0.stat, derby-3435-live-data-v1.zip, derby-3435-live-data-v2.zip
>
>
> Most functionality of and information about a running instance of the Network Server is currently only available from the host running the Network Server, using the NetworkServerControl API.
> With a JMX Management and Monitoring service in place utilizing JMX (DERBY-1387), it is possible to expose some of the Network Server functionality and information through an MBean that is specific to the Network Server, to both local and remote users (JMX clients), subject to security restrictions. Access to Derby libraries on the client side is not even a requirement, potentially making a server administrator's job a lot easier.

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