(WebSphere 7.0) Fehler beim Parsen ein Dokument Coregroup

Question

Ich versuche derzeit ein Websphere 7.0-Serverlocaly in Rational Application Developer (RAD ) laufen zu lassen. Immer wenn ich den Server starte, bekomme ich "Fehler bei der Analyse eines Stammdokuments". Hat jemand mit dieser Art von Problem konfrontiert? Wenn ja, was ist ein Kerngruppe Dokument und natürlich, was ist die Lösung?

Stacktrace:

com.ibm.ws.exception.ConfigurationError: com.ibm.wsspi.hamanager.HAException: Error parsing a CoreGroup document 
    at com.ibm.ws.hamanager.runtime.config.Config.initialize(Config.java:184) 
    at com.ibm.ws.hamanager.runtime.CoordinatorComponentImpl.initialize(CoordinatorComponentImpl.java:204) 
    at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1166) 
    at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1073) 
    at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:874) 
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:780) 
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:754) 
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:350) 
    at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:280) 
    at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214) 
    at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666) 
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:59) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) 
    at java.lang.reflect.Method.invoke(Method.java:611) 
    at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213) 
    at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93) 
    at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74) 
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) 
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) 
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) 
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) 
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) 
    at java.lang.reflect.Method.invoke(Method.java:611) 
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340) 
    at org.eclipse.core.launcher.Main.basicRun(Main.java:282) 
    at org.eclipse.core.launcher.Main.run(Main.java:981) 
    at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:330) 
    at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:108) 
Caused by: com.ibm.wsspi.hamanager.HAException: Error parsing a CoreGroup document 
    at com.ibm.ws.hamanager.runtime.config.CoreGroupConfig.<init>(CoreGroupConfig.java:124) 
    at com.ibm.ws.hamanager.runtime.config.StateBlobBuilder.buildBlob(StateBlobBuilder.java:103) 
    at com.ibm.ws.hamanager.runtime.config.Config.initialize(Config.java:180) 
    ... 32 more 
Caused by: java.lang.NullPointerException 
    at com.ibm.ws.hamanager.runtime.config.CoreGroupLiveness.<init>(CoreGroupLiveness.java:70) 
    at com.ibm.ws.hamanager.runtime.config.CoreGroupConfig.<init>(CoreGroupConfig.java:110) 
    ... 34 more 

Answer 1

Haben Sie wandern von WAS V6.1? Wenn dies der Fall ist, sehen Sie das in APAR PK82319, http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK82319 Upgrade von WAS V7 auf 7.0.0.3 oder höher beschriebene Problem und führen die Migration erneut durch.

Wenn keine Migration, dann schauen Sie auf die Dokumente Coregroup hier: /config/cells // coregroups