[Scott Anderson]

Glad you found it. Please see the WebLogic 6 configuration document for a little more help if you need it as well:
http://www.myeclipseide.com/images/tutorials/quickstarts/websphere6/

[Mayfair]

Hi,
We have WAS6.1 server installed with security Enabled and it is working fine when we start the server outside of workbench, however when we configure and start the server from MyEclipse IDE. it is giving the below Exception.
*************************************************************************************
WSVR0100W: An error occurred initializing, com.ibm.ws.runtime.config.BaseServerConfigLocator@794c794c
com.ibm.ws.exception.ConfigurationError: java.io.FileNotFoundException: C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\amfamserver\config\cells<!– [display] –>0000369787PCNode01Cell\nodes<!– [display] –>0000369787PCNode01\servers\server1\server.xml (The system cannot find the path specified.)
at com.ibm.ws.runtime.config.BaseServerConfigLocator.initialize(BaseServerConfigLocator.java:30)
at com.ibm.ws.runtime.WsServerImpl.bootConfigLocators(WsServerImpl.java:300)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:120)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:460)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:183)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:90)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:72)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:264)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:75)
*****************************************************************************************************
Let us know if there is a solution to fix this. If not, we need to know when you are going to fix this and the security is enabled on was6.1 using “CustomRegistry”.

[Riyad Kalla]

WSVR0100W: An error occurred initializing, com.ibm.ws.runtime.config.BaseServerConfigLocator@794c794c
com.ibm.ws.exception.ConfigurationError: java.io.FileNotFoundException: C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\amfamserver\config\cells<!– [display] –>0000369787PCNode01Cell\nodes<!– [display] –>0000369787PCNode01\servers\server1\server.xml (The system cannot find the path specified.)

Mayfair, does this file exist?

Are you sure you have your NODE name setup correctly under the WebSphere 6.1 connector settings?

[Mayfair]

I found the issue was with Server Preferences dialog. when I browse the was server folder location it is taking the wrong node name & cell name, due to this we are getting that exception.

[Riyad Kalla]

Mayfair,
Were you able to adjust these values to correct the server launch?

[Mayfair]

MyEclipse console is throwing this exception when we configure a new WAS server
*********************************************************************************************
WSVR0501E: Error creating component null [class com.ibm.ws.asynchbeans.J2EEServiceManager]
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:205)
at com.ibm.ws.asynchbeans.services.tx.JTAServiceWithContext.<clinit>(JTAServiceWithContext.java:101)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:187)
at com.ibm.ws.asynchbeans.J2EEServiceManager.start(J2EEServiceManager.java:638)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:977)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:673)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:191)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:977)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:673)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:485)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:191)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:139)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:460)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:183)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:90)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:72)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:245)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:73)
Caused by: java.lang.IllegalStateException: com.ibm.ws.uow.UOWManagerImpl is not a valid class.
at com.ibm.ws.util.ImplFactory.loadImplFromClass(ImplFactory.java:349)
at com.ibm.ws.util.ImplFactory.loadImplFromKey(ImplFactory.java:323)
at com.ibm.ws.util.ImplFactory.loadImplFromKey(ImplFactory.java:327)
at com.ibm.ws.uow.UOWManagerFactory$1.run(UOWManagerFactory.java:53)
at java.security.AccessController.doPrivileged(AccessController.java:242)
at com.ibm.ws.uow.UOWManagerFactory.<clinit>(UOWManagerFactory.java:47)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:187)
… 33 more
***********************************************************************************************

[Mayfair]

Yes We manually modified the values and now i am getting another error

[Riyad Kalla]

Caused by: java.lang.IllegalStateException: com.ibm.ws.uow.UOWManagerImpl is not a valid class.

By default the MyEclipse connectors will pickup the *default* set of JARs for each application server. Some servers, when run in different modes, require addition JARs to be added to their classpaths.

Given the exception above, it’s possible that you might need to go to the “Paths” sub-preference under the WebSphere 6.1 connector, and add the JAR from the WebSphere install dir that contains the com.ibm.ws packages.

[Mayfair]

There are several packages whose name starts with “com.ibm.ws”. Can you specify what files are specifically need to fix this error.
Aprreciate your help

[Jeff Kottke]

What was the remedy for this? I see that it works with the connector now, but I am trying to get an instance of 6.1 to run from the debug configuration (debug dialog) and I am getting the same error as above.
com.ibm.ws.exception.ConfigurationError: couldnt register ComponentManager

[Riyad Kalla]

Guys with my preliminary digging I don’t know that I ever drilled down the specific JAR that this class came from, it’s possible the original poster did if he didn’t mind circling back here.

[Author]

Posts