Websphere CORBA.BAD_OPERATION错误

时间:2013-10-24 11:33:54

标签: websphere ibm-mq websphere-portal websphere-6.1

我在websphere启动时收到以下错误消息。我真的无法弄清楚我的问题在这里。任何帮助和建议将不胜感激。感谢

最后一次出现的索引计数时间异常SourceId ProbeId ------ + ------ + --------------------------- + -------- ------------------      1 1 24.10.2013 06:35:41:080 GMT org.omg.CORBA.BAD_OPERATION com.ibm.ws.naming.jndicos.CNContextImpl.isLocal 3510 ------ + ------ + --------------------------- + -------- ------------------ + 2 1 24.10.2013 06:35:42:284 GMT java.io.IOException com.ibm.ws.management.discovery.DiscoveryService.sendQuery 165

以下日志来自dmgr_exception.log。

 ------Start of DE processing------ = [24.10.2013 11:24:44:982 GMT] , key = org.omg.CORBA.BAD_OPERATION com.ibm.ws.naming.jndicos.CNContextImpl.isLocal 3510
Exception = org.omg.CORBA.BAD_OPERATION
Source = com.ibm.ws.naming.jndicos.CNContextImpl.isLocal
probeid = 3510
Stack Dump = org.omg.CORBA.BAD_OPERATION: The delegate has not been set!  vmcid: 0x0  minor code: 0  completed: No
    at org.omg.CORBA.portable.ObjectImpl._get_delegate(ObjectImpl.java:80)
    at org.omg.CORBA.portable.ObjectImpl._is_local(ObjectImpl.java:381)
    at com.ibm.ws.naming.jndicos.CNContextImpl.isLocal(CNContextImpl.java:4901)
    at com.ibm.ws.naming.jndicos.CNContextImpl.<init>(CNContextImpl.java:365)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnInitCtxFactory.java:1274)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:934)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:824)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:533)
    at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:117)
    at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:712)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:247)
    at javax.naming.InitialContext.rebind(InitialContext.java:379)
    at com.ibm.ws.management.connector.rmi.RMIConnectorController.start(RMIConnectorController.java:88)
    at com.ibm.ws.management.component.JMXConnectors.startRMIConnector(JMXConnectors.java:664)
    at com.ibm.ws.management.component.JMXConnectors.started(JMXConnectors.java:1653)
    at com.ibm.ws.runtime.workloadcontroller.WorkloadController.startedWorkloads(WorkloadController.java:649)
    at com.ibm.ws.runtime.workloadcontroller.WorkloadController.started(WorkloadController.java:595)
    at com.ibm.ws.runtime.component.WLCImpl.start(WLCImpl.java:94)
    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:526)
    at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:192)
    at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:140)
    at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:461)
    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: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: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: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:339)
    at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:94)

1 个答案:

答案 0 :(得分:1)

您应该有一个包含事件报告的日志文件(至少接近):/WebSphere/AppServer/profiles/default/logs/ffdc/<your server name>

它应包含更多信息(和堆栈跟踪)。

编辑:

Websphere 6.1已经陈旧了,事实上IBM确实not support it anymore since 30 sept 2013

由于在以后的版本中问题似乎是known and fixed,我建议您更新到更新的版本,至少到最近fixpack of 6.1。您可以在this page中详细了解该流程。 6.1.0.47 FixPack是最后一个。您只需下载PAK文件并运行安装程序。