geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bohn (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4369) The new attribute values are overwrote while restarting the DB pool connector
Date Thu, 13 Nov 2008 04:15:44 GMT

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

Joe Bohn commented on GERONIMO-4369:
------------------------------------

I don't know the full rationale, but I know that it has always been a goal to keep the concepts
of load/unload and start/stop independent.  It certainly provides for more flexibility.  
I'm starting to wonder if the problem is really in the portlet itself.    There are several
attributes that are similar between generic and non-generic pools.   User name falls into
that category.  Perhaps we're not updating the name in some local config structure and it
is only update when reloaded.  

This is unrelated but I also noticed something strange with user name when creating an embedded
derby (non-xa) pool.  For some reason we get another attribute called "Shutdown Database"
which seems to be getting confused with User Name since the value for "Shutdown Database"
is by default the user name and the value for "User Name" is null. 

> 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: kernel
>    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.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.


Mime
View raw message