[
https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670974#action_12670974
]
Ivan commented on GERONIMO-4369:
--------------------------------
Thanks for your comments, Manu.
I partly agreed your suggestions,
1. On restart from console changes are lost
what I did in the patch Geronimo-4369-01.21 is the same with the previous
one, except for trying to restart all the stopped configurations. Not sure
which changes will be lost (except for those properties mentioned in 2))?
2. Admin console shows stop start and restart messages.
I just want to show the full cycle about the restart process, maybe I
print two much messages.
3. Failure to start modules.
Not sure which modules are not started ?
4. Significant increase in startup time
It is sure, I have no idea about it, anyway, it needs time to restart so
much components.
5. Stopping and Starting the server also results in all changes being lost
Not sure which changes are lost ? Could you please give an example.
For your solution, basicly, it is better. Only one concern is that, if I
restart configuration A, and A has a child configurtion B, only applies the
changes to A may be not enough, some changes on B maybe lost.
I have not try it, wish I made a mistake, ^_^
> 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: Manu T George
> Priority: Blocker
> Fix For: 2.1.4, 2.2
>
> Attachments: G-4369-0205.patch, Geronimo-4369-01.21.patch,
> 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.