[
https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650225#action_12650225
]
Joe Bohn commented on GERONIMO-4369:
------------------------------------
I looked into both the lastest patch attached to this JIRA and the patch
attached to Geronimo-4219. Both have the same behavior and effectively do the
same thing - reloading the configuration during a restart. This seems to work
for the "basic connection properties" (like username and LoginTimeout.
However, it doesn't seem to work for the Connection Pool Parameters like Pool
Min Size, Max Size, Idle Timeout, etc...
Also, I'd still like to learn if there is a better way other than forcing
reload ... just haven't dug in deep enough yet.
> 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: Donald Woods
> 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.
