geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Assigned: (GERONIMO-1889) Changing pooling parameters for connector does not persist to config.xml
Date Thu, 04 May 2006 22:55:18 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1889?page=all ]

Aaron Mulder reassigned GERONIMO-1889:
--------------------------------------

    Assign To: Paul McMahan  (was: Aaron Mulder)

It should never be necessary for a caller to manually set things on the attribute store like
this patch does.

The logic should be, any time the kernel/gbean infrastructure detects a setter call, it notifies
the attribute store (that should be in place).  When the attribute store gets such a notification,
it should locate the configuration and gbean entries in the file.  The configuration must
be there.  If there is no matching gbean entry in that configuration, one should be created.
 Finally, the new value should be written for the attribute for the gbean, and the method
called that causes the file write to be queued.

It looks like this logic is in place in LocalAttributeManager.setValue.  We need to find out
what's wrong and correct it either there or in the immediate caller, not add manual calls
to the attribute store.

> 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


Mime
View raw message