You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2006/05/13 08:12:08 UTC

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

     [ http://issues.apache.org/jira/browse/GERONIMO-1889?page=all ]
     
Aaron Mulder resolved GERONIMO-1889:
------------------------------------

    Resolution: Fixed

This patch is definitely progress.  However, I don't like the console part of the patch.  For one thing, I don't like the client being in a position of needing to manually create a proxy because the underlying service didn't do it and should have.  On top of that, the security reproxying doesn't appear to be necessary (only for connectors).

Applied the non-console parts of the patch and updated the connector code to return a proxy for the ConnectionManager if it's not already (which, currently, it's not).  That should do it.

> 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: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1
>  Attachments: ACTIVEMQ-gbean.patch, GERONIMO-1889.patch, GERONIMO-1889.patch.2
>
> 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