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: [Servl
et
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.ApplicationServerColle
ctionAction. getRefId(ApplicationServerCollectionActi
on.java:596)
at
com.ibm.ws.console.servermanagement.applicationserver.ApplicationServerColle
ctionAction. perform(ApplicationServerCollectionActio
n.java:132)
at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va: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(StrictServle
tInstance.java:110)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecy
cleServlet.java:174)
at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServ
let.java:313)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecyc
leServlet.java:116)
at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java
:283)
at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidSer
vletReferenceState.java:42)
at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletIns
tanceReference.java:40)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(
WebAppRequestDispatcher.java:1049)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppReques
tDispatcher.java:600)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequest
Dispatcher.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(C
achedInvocation.java:71)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletReq
uestProcessor.java:182)
at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListene
r.java:334)
at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.jav
a: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)

[ Post a follow-up to this message ]

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

[ Post a follow-up to this message ]

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

[ Post a follow-up to this message ]