geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan (JIRA)" <>
Subject [jira] Updated: (GERONIMO-1889) Changing pooling parameters for connector does not persist to config.xml
Date Fri, 05 May 2006 20:59:29 GMT
     [ ]

Paul McMahan updated GERONIMO-1889:

    Attachment: GERONIMO-1889.patch.2

Thanks to Aaron for the helpful suggestion on a better way to persist attributes.  I was thrown
off when working on the previous patch by the fact that using a proxy didn't help persist
certain attributes.  Turns out those attributes were not specified as manageable by their
corresponding gbeans.  Adding them to the gbean's manageable interfaces and then updating
them from the console via a proxy fixed the problem.

One problem remains, though, which is that the host and port attributes for activemq connectors
don't persist correctly when changed from the console.  I assume its because they are not
specified as manageable in the activemq gbean.  I will investigate further and open an activemq
jira if necessary to get that fixed.

> Changing pooling parameters for connector does not persist to config.xml
> ------------------------------------------------------------------------
>          Key: GERONIMO-1889
>          URL:
>      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, 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:
For more information on JIRA, see:

View raw message