[ https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647542#action_12647542 ]
Manu T George commented on GERONIMO-4369: ----------------------------------------- But we also need to restart the child configurations I think that the reason that restart doesn't re-read the configuration is to improve the performance. So its faster than stop and start since it just restarts the configuration instead of loading and starting. Also users will be usually restarting webapps etc which may not have gbean updates that need to be picked up most of the time. So I think it may be better to have a new console utility method that does both these things and all the console portlets that want to make changes can call that method. Maybe there is one already and i am not aware of it. Just my 2 cents > The new attribute values are overwrote while restarting the DB pool connector > ----------------------------------------------------------------------------- > > Key: GERONIMO-4369 > URL: https://issues.apache.org/jira/browse/GERONIMO-4369 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console > Affects Versions: 2.2 > Environment: Geronimo 2.2 snapshot > JDK 1.5 > Windows XP > Reporter: Ivan > Assignee: Joe Bohn > Fix For: 2.2 > > Attachments: Geronimo-4369-11.13.patch > > > After editing the values in the db pool, then restart it in the console, the > new values lost. > When saving the new attribute values, such as user name, the gbeandata in > the configurationManager is not updated, so while restarting the connector, > the gbinstance copies those old values from it. So the new persistent values > do not take effect, > Do I miss anything, thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.