geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "xiezhi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-6377) Couldn't save connection pool parameters change permanently
Date Fri, 10 Aug 2012 02:17:31 GMT

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

xiezhi commented on GERONIMO-6377:
----------------------------------

These parameters couldn't be saved in config.xml. They are "Pool Min Size", "Pool Max Size",
"Blocking Timeout" and "Idle Timeout". I don't know why don't save them in config.xml and
why GenericConnectionManagerGBean.java don't provide a public method "getAbstractName()".
                
> Couldn't save connection pool parameters change permanently
> -----------------------------------------------------------
>
>                 Key: GERONIMO-6377
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6377
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: databases
>    Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 2.1.8, 2.2, 2.2.1,
3.0-M1, 3.0-beta-1
>            Reporter: xiezhi
>            Assignee: xiezhi
>
> When you change connection pool parameters value in admin console, the value seems be
saved. But if restart the server, the value is changed to the default.

--
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

        

Mime
View raw message