[
https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated GERONIMO-4369:
---------------------------
Attachment: Geronimo-4369-01.21.patch
There should be some issues in the reload function of the configuration
manager, if the component which needs to restart has child configurations, the
exception will be threw on the 1186th line
removeConfigurationFromModel(configurationId);
Currently , the solution is first to stop, then start the service, and will try
to start all the stopped service, maybe we need to revert to reload function
once it works properly.
By the way, I found the j2ee-corba-yoko could not be restarted, while we stop
the service, it does not release the port 1050.
Please help to review the patch, 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-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.
