| Author |
RAD 6 Port TEst Environment 5.1.0.1 - admind console fails
|
|
|
| The portal in the test environment starts without any errors. When I
try to look at servers or enterprise apps in the admin console I get the
following error(bug) ??: - (all help appreciated)
[9/15/05 6:12:02:828 EDT] 786e67a WebGroup E SRVE0026E: [Servlet
Error]-[Class org/eclipse/emf/ecore/resource/ResourceSet violates loader
constraints: parent and child already loaded different classes]:
java.lang.LinkageError: Class org/eclipse/emf/ecore/resource/ResourceSet
violates loader constraints: parent and child already loaded different
classes
at
com.ibm.ws.console.servermanagement.applicationserver.ApplicationServerCollectionAction. getRefId(ApplicationServerCollectionActi
on.java:596)
at
com.ibm.ws.console.servermanagement.applicationserver.ApplicationServerCollectionAction. perform(ApplicationServerCollectionActio
n.java:132)
at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher. handleWebAppDispatch(WebAppRequestDispat
cher.java:1049)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:600)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:201)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:286)
at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:624)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)
| |
| ohkado 2005-09-15, 6:06 pm |
| If you mean the admin console of Test Environment, you can NOT use it.
I heard there is a conflict about the version of library used by Portal
and Admin and that is why you need to start server1 to use admin console
in regular Portal installation.
ohkado
| |
|
| Thanks a bunch. One would think it should work.
ohkado wrote:
> If you mean the admin console of Test Environment, you can NOT use it.
> I heard there is a conflict about the version of library used by Portal
> and Admin and that is why you need to start server1 to use admin console
> in regular Portal installation.
>
> ohkado
|
|
|
|