geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-1387) Geronimo Console Applications portlets fail after starting app client.
Date Wed, 11 Jan 2006 21:26:21 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1387?page=all ]

Paul McMahan updated GERONIMO-1387:
-----------------------------------

    Attachment: GERONIMO-1387.patch

Attaching a patch that will prompt the user before starting an application client or any of
the system modules whose confiID begins with "geronimo/client".

Also prompts the user before stopping any of the system modules whose configID begins with
"geronimo/" or the web console EAR (searches for  "geronimo/webconsole*" in the configID).

> Geronimo Console Applications portlets fail after starting app client.
> ----------------------------------------------------------------------
>
>          Key: GERONIMO-1387
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1387
>      Project: Geronimo
>         Type: Bug
>   Components: console
>     Versions: 1.0
>  Environment: Windows JDK 1.4.2_08, Jetty version of 1.0 12182005 test release.
>     Reporter: Neal Sanche
>     Priority: Critical
>  Attachments: GERONIMO-1387.patch
>
> Log into console, and click App Clients navigation link on left. The daytrader-derby-jetty-streamer-client/1.0/car
component is stopped. Click the 'Start' link. The server will throw an exception:
> 22:57:55,161 ERROR [PortletFragment] Error in Portlet
> java.lang.IllegalStateException: More than one configuration mananger was found
> in kernel
>         at org.apache.geronimo.kernel.config.ConfigurationUtil.getConfigurationM
> anager(ConfigurationUtil.java:60)
>         at org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView
> (ConfigManagerPortlet.java:203)
>         at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:250)
>         at javax.portlet.GenericPortlet.render(GenericPortlet.java:178)
>         at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218
> )
>         at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
>         at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153)
>         at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428
> )
>         at org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolde
> r.java:99)
>         at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
> WebApplicationHandler.java:830)
>         at org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170
> )
>         at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
> WebApplicationHandler.java:821)
>         at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
> onHandler.java:471)
>         at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:283)
>         at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:163)
>         at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvoke
> rImpl.java:120)
>         at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvoke
> rImpl.java:73)
>         at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerI
> mpl.java:119)
>         at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPo
> rtlet(PortletContainerWrapperImpl.java:70)
>         at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(Portl
> etFragment.java:168)
>         at org.apache.jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService
> (org.apache.jsp.WEB_002dINF.aggregation.ColumnFragment_jsp:65)
>         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
>         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
> .java:322)
> Then from that point onward, the server will be unable to show any of the following portlets:
> Application EARs
> Web App WARs
> EJB Jars
> J2EE Connectors
> App Clients
> System Modules
> Each of which will throw the above exception, or one remarkably similar.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message