[
https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575381#action_12575381
]
Bernt M. Johnsen commented on DERBY-3435:
-----------------------------------------
Ok. So established practice would then be e.g.
ActiveConnectionCount
WaitingConnectionCount
AccumulatedConnectionCount (I felt "total" might be interpreted as
active+waiting, so I suggest "accumulated)
"Active" means that it is not queued/waiting, and all connections will be
active when derby.drda.maxThreads==0, if maxThreads>0 connections will be
queued if the number of active connections reach this value. As long as
derby.drda.timeSlice==0 the getConnection will return when the connection
becomes active. If timeSlice > 0 (and the number of actual connections >
msxThreads), the connections will alternate "active" and "waiting" according to
the (somewhat primitive) timeslicing algortthm in the network server.
Maybe
ConnectionCount and
WaitingConnectionCount?
PS: Wrt ZIP, sorry about that. I have automated the patch generation in a
script to avoid some netbeans quirks. Since it seems to be awkward for others,
I'll stop using the script for small patches.
> 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-fix-v0.zip, 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.
