geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay D. McHugh (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3269) Console:some parameters remains original when restarted
Date Fri, 29 Jun 2007 01:13:04 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508978
] 

Jay D. McHugh commented on GERONIMO-3269:
-----------------------------------------

I think that this is a bigger problem than just blocking the unload/load configuration calls.

Here is the 'big picture' of what is going on:
1) A new database pool is created - Geronimo creates and deploys a RAR for the pool.
2) The pool is edited - Geronimo stores the override values directly in the config.xml file.

If the server is shutdown, the config.xml changes are retained.
If the database pool is 'restarted', the config.xml changes are retained.

If the database pool is stopped, the config.xml changes are wiped when the configuration is
unloaded.
And, the next time the pool is started, it will have returned to its originally created values.

It looks like the edit/save database pool will need to update the RAR rather than just putting
the
override values into the config.xml.

Or, we need to warn users that if they ever stop the database pool from the j2ee connectors
screen then any changes they have made will be lost.

Comments anyone?  Should we be updating the RAR or just warning the users?

> Console:some parameters remains original when restarted  
> ---------------------------------------------------------
>
>                 Key: GERONIMO-3269
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3269
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 2.0-M6
>         Environment: Windows 2003/XP
>            Reporter: Song
>         Attachments: geronimo-3269.patch
>
>
> steps as below can reproduce the error:
>  1) create database pool "EmployeeDatasource" from console successfully
>  2) Click on "edit" link next to "EmployeeDatasource"
>  3) Modify some parameters like Pool Max Size from 10 to 50, Idle Timeout from 15 to
30, click on "Save" button
>  4) Under J2EE Connectors,click on "Stop", then click "Start"
>  5) parameters "Pool Max Size" return to 10, and "Idle Timeout" also changed to original
15
>  
>  6) If skip 4),click on "restart", the modification will take effect. 

-- 
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