[
https://issues.apache.org/jira/browse/GERONIMO-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664103#action_12664103
]
Manu T George commented on GERONIMO-4509:
-----------------------------------------
This is not a defect with the Ejb Server Portlet. Actually the restart
functionality of the admin console has been broken. Previously on restart of a
configuration all child configurations would also be started. Currently the
child configurations are not being started and so restarting openejb does not
start its childs and so the problem.
You can try restarting any other configuration and you will see that the
children are not restarted. This is a regression of the functionality
> Two EJB server portlet issues
> -----------------------------
>
> Key: GERONIMO-4509
> URL: https://issues.apache.org/jira/browse/GERONIMO-4509
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.2
> Environment: JDK 1.6
> Ubuntu 8.04
> AG 2.2 snapshot 20090110
> Reporter: Forrest Xia
> Assignee: Manu T George
>
> For the new EJB server portlet, there are these problems:
> 1. Message prompt just restarting openejb module cause several console
> exceptions and EJB server portlet disappear in admin console at next time
> restart server.
> Steps:
> 1.1 Change value of a EJB container parameter, then it prompts OpenEJB module
> should be restarted for effectiveness. So I use expert mode to restart module
> org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car, confirm restart, then
> several exceptions are thrown out as following:
> 2009-01-14 09:35:45,546 ERROR [ConfigManagerPortlet] Exception
> java.lang.IllegalStateException: Configuration
> org.apache.geronimo.configs/axis2-ejb/2.2-SNAPSHOT/car still has children
> at
> org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
> at
> org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
> ...
> 2009-01-14 09:35:45,965 ERROR [[SystemModules]] Servlet.service() for servlet
> SystemModules threw exception
> java.lang.NullPointerException
> at
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.getConfigurationState(ConfigManagerPortlet.java:325)
> at
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:272)
> ...
> 2009-01-14 09:37:08,300 ERROR [[SystemModules]] Servlet.service() for servlet
> SystemModules threw exception
> java.lang.IllegalStateException: Configuration
> org.apache.geronimo.configs/jaxws-ejb-deployer/2.2-SNAPSHOT/car still has
> children
> at
> org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
> at
> org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
> ...
> 2009-01-14 09:37:19,125 ERROR [[SystemModules]] Servlet.service() for servlet
> SystemModules threw exception
> java.lang.IllegalStateException: Configuration
> org.apache.geronimo.configs/openejb-deployer/2.2-SNAPSHOT/car still has
> children
> at
> org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
> at
> org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
> ...
> Anyway, the openejb module finally restarted, but no children modules appear
> anymore. Consequently the EJB server portlet disappears from the admin
> console. No way to check if the changed parameter takes effect.
> 2.2 Followed by step 1, restart geronimo by no change of config.xml, still
> the EJB server portlet is not there. Then check the config.xml, the portlet
> module <module
> name="org.apache.geronimo.plugins/openejb-console-tomcat/2.2-SNAPSHOT/car"/>
> is load=false
> Based on the symptom, I think it might be better to suggest user to restart
> geronimo server as a whole, not just openejb module.
> 2. Another issue is the parameter value seems be changed only once. For
> example, if you changed strictpooling from default true to false, then you
> want to change it back without restarting server, there is no way. This
> behavior is better to be improved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
