com.ibm.ws.exception.ConfigurationWarning

Exception caught when initializing component

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web5

  • via Coderanch by Anand Bansal, 8 months ago
    Exception caught when initializing component
  • Exception caught when initializing component
  • Exception caught when initializing component
  • Stack trace

    • com.ibm.ws.exception.ConfigurationWarning: Exception caught when initializing component at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1237) at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1099) at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:901) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:776) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:750) at com.ibm.ws.runtime.component.ApplicationServerImpl.initialize(ApplicationServerImpl.java:192) at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1192) at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1099) at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:928) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:776) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:750) at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:333) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:336) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:267) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:730) 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:234) at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96) at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77) 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.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:379) at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:150)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.