[
https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647265#action_12647265
]
Manu T George commented on GERONIMO-4369:
-----------------------------------------
The JIRA is related to https://issues.apache.org/jira/browse/GERONIMO-4219. The
attached patch may not be optimal or working.
Actually the restart functionality in the admin console starts a configuration
and all its child configurations also. That is the functionality of the
restartConfiguration method in the configuration Manager. Does the attached
patch do this?
The issue is that the attribute store is not updated during restart. We should
first decide whether to fix it here or in the configuration manager. Why
shouldn't the restart method in the configurationManager update the attribute
store in case any changes are made?
> 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.
