[ 
https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665390#action_12665390
 ] 

Ivan commented on GERONIMO-4369:
--------------------------------

I am working on this issue, it seems that the reason is not only that child 
configurations are not started. In the reloadConfiguration function, I found 
that there is no invocations of  configurationModule.stop()/unload() to sync 
the configuration status between the configutationManager and 
configurationModel, which will cause a IllegalStateException threw by 
ConfigurationStatus.destroy().
Any comment ? Thanks !


> 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: Ivan
>            Priority: Blocker
>             Fix For: 2.1.4, 2.2
>
>         Attachments: Geronimo-4369-11.13.patch, Geronimo-4369-11.17.patch, 
> Geronimo-4369-11.19.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.

Reply via email to