You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org> on 2006/05/05 02:28:17 UTC

[jira] Commented: (GERONIMO-1889) Changing pooling parameters for connector does not persist to config.xml

    [ http://issues.apache.org/jira/browse/GERONIMO-1889?page=comments#action_12377924 ] 

Dain Sundstrom commented on GERONIMO-1889:
------------------------------------------

Aaron, that means we must always use proxies for every object in the console, so the setters can be redirected through the GBean system and persist the values.  Is that the long term plan?

> Changing pooling parameters for connector does not persist to config.xml
> ------------------------------------------------------------------------
>
>          Key: GERONIMO-1889
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1889
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: connector, kernel, console
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Paul McMahan
>     Priority: Blocker
>      Fix For: 1.1
>  Attachments: GERONIMO-1889.patch
>
> To replicate:
> Open the console
> Select Database Pools
> Click the "edit" link to the right of "System Datasource"
> Change pool max size to 119
> Click Save
> Click the "edit" link to the right of "System Datasource"
> Confirm that it shows a pool max size of 119
> Shut down the server
> Grep config.xml for 119, it does not appear
> Start the server
> Edit the System Datasource again, confirm that the pool max size is NOT 119
> Also need to check whether changing the data connection properties is persisted.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira