[
https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670726#action_12670726
]
Manu T George commented on GERONIMO-4369:
-----------------------------------------
With patch Geronimo-4369-01.21.patch i faced the following errors
1) On restart from console changes are lost
2) Admin console shows stop start and restart messages
3) Failure to start some modules
4) Significant increase in startup time
5) Stopping and Starting the server also results in all changes being lost
I also think that this is just not a restart problem. There are two separate
issues at work here that I am seeing
1) Changes made are lost during restart from admin console of the connector
This is because the changes made to the attributeStore are not
applied to the configurations on restart. Can be fixed by patch
G-4369-0205.patch
2) Some Changes made are lost on stopping and starting the server or the
connector
Not fixed by any of the patches
1) is fixed with the patch i have supplied. Also changes to some of the fields
like database name and createDatabase are getting reflected even on server
restart of config stop and start.
however 2 is still open and This leads me to believe that this problem is
localized to the db manager portlet. On seeing config.xml I see only a few
values are persisted
<module name="console.dbpool/Testman/1.0/rar">
<gbean
name="console.dbpool/Testman/1.0/rar?J2EEApplication=null,JCAConnectionFactory=Testman,JCAResource=console.dbpool/Testman/1.0/rar,ResourceAdapter=console.dbpool/Testman/1.0/rar,ResourceAdapterModule=console.dbpool/Testman/1.0/rar,j2eeType=JCAManagedConnectionFactory,name=Testman">
<attribute name="DatabaseName">TESTMANT</attribute>
<attribute name="CreateDatabase">false</attribute>
<attribute name="ShutdownDatabase">system</attribute>
<attribute
name="Password">{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwAAAAEHnh03EmiNu4VTuWH+xZiRBwdAADQUVT</attribute>
<attribute name="LoginTimeout">0</attribute>
<attribute name="UserName"/>
</gbean>
</module>
Changes to these values are reflected on stop and start as expected and to the
other fields that are not in config.xml are not reflected
If fix for 1 is acceptable then we can reduce the severity of this JIRA as it
won't affect other portlets with that fix
If not acceptable I think we should revert back to restartConfiguration in the
ConfigManagerPortlet as that seems better than what we have now.
Note:
The geronimo build I am testing on is a few weeks old. I will test with a new
build as soon as I can
I tested the above for an embedded derby datasource . I am not sure whether the
same will occur for other datasources
> 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.
