I have seen that too but haven't looked into it yet. I suspect its
because installing the pluto-container plugin automatically pulls the
pluto-1.2 jars into the repository, and then the admin console
automatically picks up these jars (which it is incompatible with)
because it uses versionless dependencies in its deployment plan. If
that's right then we can probably make these two portal apps coexist
peacefully by providing the specific pluto version in the admin
console's deployment plan.
Best wishes,
Paul
On Jun 19, 2007, at 9:29 AM, Daniel Larsen wrote:
I am having some trouble with the regular Admin console after I
install this Pluto1.2 stuff as Paul has outlined.
I get the following error the first time I come to the regular
console after I restart the server:
HTTP ERROR: 404Initialization of one or more services failed.
RequestURI=/console/portal/welcome
Caused by:javax.servlet.UnavailableException: Initialization of one
or more services failed.
at org.apache.pluto.portalImpl.Servlet.init(Servlet.java:84)
at org.mortbay.jetty.servlet.ServletHolder.initServlet
(ServletHolder.java:433)
at org.mortbay.jetty.servlet.ServletHolder.getServlet
(ServletHolder.java :342)
at org.mortbay.jetty.servlet.ServletHolder.handle
(ServletHolder.java:463)
at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle
(InternalJettyServletHolder.java:65)
at org.mortbay.jetty.servlet.ServletHandler.handle
(ServletHandler.java:367)
at org.mortbay.jetty.security.SecurityHandler.handle
(SecurityHandler.java:216)
at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle
(JettySecurityHandler.java:114)
at org.mortbay.jetty.servlet.SessionHandler.handle
(SessionHandler.java:181)
at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle
(ThreadClassloaderHandler.java:46)
at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle
(InstanceContextHandler.java :58)
at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle
(UserTransactionHandler.java:48)
at org.mortbay.jetty.handler.ContextHandler.handle
(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle
(WebAppContext.java:405)
at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle
(ComponentContextHandler.java:47)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle
(ContextHandlerCollection.java :211)
at org.mortbay.jetty.handler.HandlerCollection.handle
(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle
(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java :295)
at org.mortbay.jetty.HttpConnection.handleRequest
(HttpConnection.java:503)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete
(HttpConnection.java:827)
at org.mortbay.jetty.HttpParser.parseNext (HttpParser.java:511)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
at org.mortbay.io.nio.SelectChannelEndPoint.run
(SelectChannelEndPoint.java :361)
at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201)
at org.apache.geronimo.pool.ThreadPool
$ContextClassLoaderRunnable.run(ThreadPool.java:331)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
then if i refresh i get a broken admin console with no portlets.
(basically a top bar and a nav bar)
any ideas? is anyone else running into the same problem?
I'll keep playing around with different senarios and see if I can
isolate the problem.
