You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2012/05/08 16:40:14 UTC

[jira] [Commented] (OFBIZ-4864) Mechanism to publish information about connection pools

    [ https://issues.apache.org/jira/browse/OFBIZ-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270493#comment-13270493 ] 

Jacques Le Roux commented on OFBIZ-4864:
----------------------------------------

I like the feature, did not review, nor test, yet
                
> Mechanism to publish information about connection pools
> -------------------------------------------------------
>
>                 Key: OFBIZ-4864
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4864
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: framework
>    Affects Versions: SVN trunk
>            Reporter: Jacopo Cappellato
>            Assignee: Jacopo Cappellato
>            Priority: Minor
>         Attachments: pools-status.patch, pools-status.png
>
>
> Please review the attached patch that I would like to commit to trunk:
> * enabled by default the DebugManagedDataSource wrapper around ManagedDataSource
> * enhanced the DebugManagedDataSource wrapper to:
> ** print log messages only at verbose level (instead of always)
> ** if possible print additional information about the connection status
> ** added new method that returns information about the connection pool settings/status
> * added new static method to DBCPConnectionFactory to return information about the pools
> * new screen in the webtools where information about each pool/helper is shown (see screenshot)
> What do you think? The code is safe and it will not have any impact on performance (unless you enable verbose logging on DebugManagedDataSource). The information provided by the screen can be very useful to analyze the status of the pools.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira