[jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523021
]
Joe Bohn commented on GERONIMO-3401:
{quote}
Agreed. These two cases could be handled separately or we could consider
generalizing the user interface for component lifecycle to address these and
other potentially confusing scenarios that will arise all at one go.I think
that right now the user interface is technically correct but is not intuitive.
{quote}
I'm not as sure that either the UI or the command line are technically correct
today regarding restart ... but it's probably a bike shed issue. I think a
reasonable expectation of a user after a restart is that the system is in the
same state WRT active components prior to the restart. If we choose to keep
the current behavior then we need to do a better job warning the user of the
consequences and help by listing the components that are stopped and not
restarted.
{quote}
For the command line client maybe that is OK, but for the graphical UI we could
allow the user to make more informed decisions by providing a better visual
representation of the component hierarchy. Attaching the lifecycle controls to
the Dependency Viewer might be a good first step.
{quote}
Perhaps ... but the dependency viewer sometimes make it difficult to locate the
module that you want to operate on and the dependencies are actually inverted
from what is needed for these operations (the current dependencies show what
cars/jars this module is dependent upon rather than which modules are dependent
upon it which would be the ones affected by the operation).
{quote}
Also, the lifecycle controls for components that are in the console's
dependency path could be disabled since they are required by the viewer itself
(they can still be controlled from the CLI). Just throwing out some ideas.
{quote}
Yes, that is certainly the quick and easy way out ... which is also why I did
some digging to understand the components that actually create problems for the
console and/or the server. The real answer here is I think I need to take
this discussion to the dev list soon but I'd like to get some more details
first.
> Stop of module from "System Modules" in console should warn user of
> destructive action
> --
>
> Key: GERONIMO-3401
> URL: https://issues.apache.org/jira/browse/GERONIMO-3401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Affects Versions: 2.0, 2.0.x
> Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
> likely affects others as well
>Reporter: Matt Hogstrom
>Assignee: Joe Bohn
> Fix For: 2.0.x
>
>
> When using the Geronimo Console to stop of a module a 404 is received in the
> console. In this case an attempt to stop OpenEJB. The console then becomes
> unusable and also does not survive a restart. It appears the console needs
> to be re-installed.
> {panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> HTTP Status 404 -
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> type Status report
> message
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> description The requested resource
> (/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
> is not available.
> {panel}
> {panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> [] received stop signal
> 00:59:03,833 ERROR [Servlet] Exception caught:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> to gbean:
> org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit()
> at
> org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
> at
> org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
> at
> org.apache.geronimo.tomcat.inte
[jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523009
]
Paul McMahan commented on GERONIMO-3401:
{quote}
However, I think the real issue there is that in a restart scenario we only
"restart" the subject component and do nothing more with components that were
stopped with dependencies upon that component. I think the expected user
behavior in that cause would be to restart not only the subject component but
all components that were subsequently stopped due to dependencies.
{quote}
Agreed. These two cases could be handled separately or we could consider
generalizing the user interface for component lifecycle to address these and
other potentially confusing scenarios that will arise all at one go.I think
that right now the user interface is technically correct but is not intuitive.
For the command line client maybe that is OK, but for the graphical UI we could
allow the user to make more informed decisions by providing a better visual
representation of the component hierarchy. Attaching the lifecycle controls to
the Dependency Viewer might be a good first step. Also, the lifecycle controls
for components that are in the console's dependency path could be disabled
since they are required by the viewer itself (they can still be controlled from
the CLI). Just throwing out some ideas.
> Stop of module from "System Modules" in console should warn user of
> destructive action
> --
>
> Key: GERONIMO-3401
> URL: https://issues.apache.org/jira/browse/GERONIMO-3401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Affects Versions: 2.0, 2.0.x
> Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
> likely affects others as well
>Reporter: Matt Hogstrom
>Assignee: Joe Bohn
> Fix For: 2.0.x
>
>
> When using the Geronimo Console to stop of a module a 404 is received in the
> console. In this case an attempt to stop OpenEJB. The console then becomes
> unusable and also does not survive a restart. It appears the console needs
> to be re-installed.
> {panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> HTTP Status 404 -
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> type Status report
> message
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> description The requested resource
> (/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
> is not available.
> {panel}
> {panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> [] received stop signal
> 00:59:03,833 ERROR [Servlet] Exception caught:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> to gbean:
> org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit()
> at
> org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
> at
> org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
> at
> org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeAfter.after(PolicyContextBeforeAfter.java:70)
> at
> org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.after(UserTransactionBeforeAfter.java:47)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.afterDispatch(DispatchListener.java:86)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.instanceEvent(DispatchListener.java:59)
> at
> org.apache.catalina.util.InstanceSupport.fireInstanceEvent(InstanceSupport.java:275)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:682)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
>
[jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523005
]
Joe Bohn commented on GERONIMO-3401:
Uninstall breaks the server on those components listed regardless of it being
initiated from the console or command line. I haven't yet run through all of
the system modules but for openejb stopping only prevents the console from
functioning and doesn't prevent the server from a restart. The console
function can be easily restored in the stop scenario by a command line start of
the console.
Paul, Geronimo-3443 is somewhat related but I don't think it is directly
related. It's a restart scenario. In our restart we must stop the specified
component and all depent components (such as the console for DOJO) which is
somewhat related to this issue. However, I think the real issue there is that
in a restart scenario we only "restart" the subject component and do nothing
more with components that were stopped with dependencies upon that component.
I think the expected user behavior in that cause would be to restart not only
the subject component but all components that were subsequently stopped due to
dependencies.
> Stop of module from "System Modules" in console should warn user of
> destructive action
> --
>
> Key: GERONIMO-3401
> URL: https://issues.apache.org/jira/browse/GERONIMO-3401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Affects Versions: 2.0, 2.0.x
> Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
> likely affects others as well
>Reporter: Matt Hogstrom
>Assignee: Joe Bohn
> Fix For: 2.0.x
>
>
> When using the Geronimo Console to stop of a module a 404 is received in the
> console. In this case an attempt to stop OpenEJB. The console then becomes
> unusable and also does not survive a restart. It appears the console needs
> to be re-installed.
> {panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> HTTP Status 404 -
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> type Status report
> message
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> description The requested resource
> (/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
> is not available.
> {panel}
> {panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> [] received stop signal
> 00:59:03,833 ERROR [Servlet] Exception caught:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> to gbean:
> org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit()
> at
> org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
> at
> org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
> at
> org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeAfter.after(PolicyContextBeforeAfter.java:70)
> at
> org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.after(UserTransactionBeforeAfter.java:47)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.afterDispatch(DispatchListener.java:86)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.instanceEvent(DispatchListener.java:59)
> at
> org.apache.catalina.util.InstanceSupport.fireInstanceEvent(InstanceSupport.java:275)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:682)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.j
[jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522835
]
Vamsavardhana Reddy commented on GERONIMO-3401:
---
Joe, I guess you are stopping/uninstalling the configurations through admin
console. What happens when you stop/uninstall the configurations through
command line deployer? Is the server broken in that case too?
> Stop of module from "System Modules" in console should warn user of
> destructive action
> --
>
> Key: GERONIMO-3401
> URL: https://issues.apache.org/jira/browse/GERONIMO-3401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Affects Versions: 2.0, 2.0.x
> Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
> likely affects others as well
>Reporter: Matt Hogstrom
>Assignee: Joe Bohn
> Fix For: 2.0.x
>
>
> When using the Geronimo Console to stop of a module a 404 is received in the
> console. In this case an attempt to stop OpenEJB. The console then becomes
> unusable and also does not survive a restart. It appears the console needs
> to be re-installed.
> {panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> HTTP Status 404 -
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> type Status report
> message
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> description The requested resource
> (/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
> is not available.
> {panel}
> {panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> [] received stop signal
> 00:59:03,833 ERROR [Servlet] Exception caught:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> to gbean:
> org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit()
> at
> org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
> at
> org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
> at
> org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeAfter.after(PolicyContextBeforeAfter.java:70)
> at
> org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.after(UserTransactionBeforeAfter.java:47)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.afterDispatch(DispatchListener.java:86)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.instanceEvent(DispatchListener.java:59)
> at
> org.apache.catalina.util.InstanceSupport.fireInstanceEvent(InstanceSupport.java:275)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:682)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68)
> at
> org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164)
> at
> org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82)
> at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
> at
> org.
[jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522829
]
Joe Bohn commented on GERONIMO-3401:
Ahh ... thanks for pointing that out Donald. I spoke with Matt and I thought
he said uninstall but it is true that the JIRA itself says stop. I'll try the
stop scenarios as well. I think we take some action to prevent somebody from
shooting themselves in the foot (without proper warning) for both stop and
uninstall scenarios.
> Stop of module from "System Modules" in console should warn user of
> destructive action
> --
>
> Key: GERONIMO-3401
> URL: https://issues.apache.org/jira/browse/GERONIMO-3401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Affects Versions: 2.0, 2.0.x
> Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
> likely affects others as well
>Reporter: Matt Hogstrom
>Assignee: Joe Bohn
> Fix For: 2.0.x
>
>
> When using the Geronimo Console to stop of a module a 404 is received in the
> console. In this case an attempt to stop OpenEJB. The console then becomes
> unusable and also does not survive a restart. It appears the console needs
> to be re-installed.
> {panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> HTTP Status 404 -
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> type Status report
> message
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> description The requested resource
> (/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
> is not available.
> {panel}
> {panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> [] received stop signal
> 00:59:03,833 ERROR [Servlet] Exception caught:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> to gbean:
> org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit()
> at
> org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
> at
> org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
> at
> org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeAfter.after(PolicyContextBeforeAfter.java:70)
> at
> org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.after(UserTransactionBeforeAfter.java:47)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.afterDispatch(DispatchListener.java:86)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.instanceEvent(DispatchListener.java:59)
> at
> org.apache.catalina.util.InstanceSupport.fireInstanceEvent(InstanceSupport.java:275)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:682)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68)
> at
> org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164)
> at
> org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82)
> at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.a
[jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522791
]
Donald Woods commented on GERONIMO-3401:
Joe, are you uninstalling the config or just stopping the config?
Matt's original text says stopping through the console, so are we comparing the
same things here?
> Stop of module from "System Modules" in console should warn user of
> destructive action
> --
>
> Key: GERONIMO-3401
> URL: https://issues.apache.org/jira/browse/GERONIMO-3401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Affects Versions: 2.0, 2.0.x
> Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
> likely affects others as well
>Reporter: Matt Hogstrom
>Assignee: Joe Bohn
> Fix For: 2.0.x
>
>
> When using the Geronimo Console to stop of a module a 404 is received in the
> console. In this case an attempt to stop OpenEJB. The console then becomes
> unusable and also does not survive a restart. It appears the console needs
> to be re-installed.
> {panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> HTTP Status 404 -
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> type Status report
> message
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> description The requested resource
> (/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
> is not available.
> {panel}
> {panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> [] received stop signal
> 00:59:03,833 ERROR [Servlet] Exception caught:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> to gbean:
> org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit()
> at
> org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
> at
> org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
> at
> org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeAfter.after(PolicyContextBeforeAfter.java:70)
> at
> org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.after(UserTransactionBeforeAfter.java:47)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.afterDispatch(DispatchListener.java:86)
> at
> org.apache.geronimo.tomcat.listener.DispatchListener.instanceEvent(DispatchListener.java:59)
> at
> org.apache.catalina.util.InstanceSupport.fireInstanceEvent(InstanceSupport.java:275)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:682)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68)
> at
> org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164)
> at
> org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82)
> at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContex
[jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522629
]
Joe Bohn commented on GERONIMO-3401:
I've done some more investigation into this to discover the other system
modules that cause problems for the console and/or the server.
There are a number of components that fail with different results. Sometime
the console is just no longer available. Other times the server itself is in a
state where it can not be restarted. I also noticed that sometime a message
precedes the stack trace on the console indicating the server stop signal has
been received (when it really hasn't). Here's a list of the modules that cause
problems when uninstalled and the types of problems. Most of the results are
predictable (those that break the console or server) but there are a few
surprises.
||config uninstalled||console broken||server broken||shutdown message||
|org.apache.geronimo.configs/activemq-broker/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/connector-deployer/2.1-SNAPSHOT/car|X|X| |
|org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car|X| | |
|org.apache.geronimo.configs/j2ee-corba-yoko/2.1-SNAPSHOT/car|X| | |
|org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car|X|X| |
|org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/j2ee-system/2.1-SNAPSHOT/car|X| |X|
|org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car|X| | |
|org.apache.geronimo.configs/jee-specs/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/openejb/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/openjpa/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/server-security-config/2.1-SNAPSHOT/car|X|X|X
|org.apache.geronimo.configs/tomcat6/2.1-SNAPSHOT/car|X| | |
|org.apache.geronimo.configs/tomcat6-deployer/2.1-SNAPSHOT/car|X| | |
|org.apache.geronimo.configs/transaction/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/webservices-common/2.1-SNAPSHOT/car|X|X|X|
|org.apache.geronimo.configs/xmlbeans/2.1-SNAPSHOT/car|X|X|X|
> Stop of module from "System Modules" in console should warn user of
> destructive action
> --
>
> Key: GERONIMO-3401
> URL: https://issues.apache.org/jira/browse/GERONIMO-3401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Affects Versions: 2.0, 2.0.x
> Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
> likely affects others as well
>Reporter: Matt Hogstrom
>Assignee: Joe Bohn
> Fix For: 2.0.x
>
>
> When using the Geronimo Console to stop of a module a 404 is received in the
> console. In this case an attempt to stop OpenEJB. The console then becomes
> unusable and also does not survive a restart. It appears the console needs
> to be re-installed.
> {panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> HTTP Status 404 -
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> type Status report
> message
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> description The requested resource
> (/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
> is not available.
> {panel}
> {panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
> titleBGColor=#F7D6C1| bgColor=#CE}
> [] received stop signal
> 00:59:03,833 ERROR [Servlet] Exception caught:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> to gbean:
> org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit()
> at
> org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
> at
> org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
> at
> org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeA
[jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522550
]
Joe Bohn commented on GERONIMO-3401:
I started to look into this ... and I think the issue is even worse than Matt
indicated.
First off, I get a different exception after I uninstall the openejb.
Secondly, I can not even restart the server after I uninstall openejb. I get
the following exception attempting to load the axis2-deployer car (which is
kind of strange because I noticed after I uninstalled openejb that
axis2-deployer was no longer started so IIUC it shouldn't be attempting to
start on a server restart either).
{panel:title=Failure on restart| borderStyle=dashed| borderColor=#ccc|
titleBGColor=#F7D6C1| bgColor=#CE}
Booting Geronimo Kernel (in Java 1.5.0_07)...
Starting Geronimo Application Server v2.1-SNAPSHOT
[**> ] 38% 6s Starting
org.apache.geronim...10:37:36,058 ERROR [[/]] "Restricted listeners property
file not found
[- ] 57% 8s Startup failed
org.apache.geronimo.kernel.config.LifecycleException: load of
org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car failed
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:297)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:278)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke()
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$1b65b454.loadConfiguration()
at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:153)
at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
Caused by: org.apache.geronimo.kernel.repository.MissingDependencyException:
Unable to resolve dependency org.apache.geronimo.configs/openejb//car
at
org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:120)
at
org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:99)
at
org.apache.geronimo.kernel.repository.DefaultArtifactResolver$$FastClassByCGLIB$$e847b746.invoke()
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.repository.ArtifactResolver$$EnhancerByCGLIB$$ab898279.resolveInClassLoader()
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.resolveParentIds(SimpleConfigurationManager.java:469)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadDepthFirst(SimpleConfigurationManager.java:428)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadDepthFirst(SimpleConfigurationManager.java:435)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadDepthFirst(SimpleConfigurationManager.java:435)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:294)
... 15 more
[- ] 57% 20s Startup failed
tetra:~/g-images/trunk/geronimo-tomcat6-jee5-2.1-SNAPSHOT/
{panel}
And here's the exception I get when I first uninstall op
