geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action
Date Mon, 27 Aug 2007 13:59:30 GMT

    [ 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=#FFFFCE} 
> 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=#FFFFCE}
> [] 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(<generated>)
>         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(StandardContextValve.java:175)
>         at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
>         at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:351)
>         at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:613)
> 00:59:03,835 ERROR [CoyoteAdapter] An exception or error occurred in the container during
the request processing
> 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(<generated>)
>         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.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:50)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:613)
> {panel}
> And the console no longer functions and the console app is unusable even after a restart.

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