1

在生产中运行我的代码时出现以下错误。但是在 qa 环境或 dev 环境中不会发生同样的情况。我认为这可能是 jndi 名称中的问题。但我不是百分百确定。谁能告诉我什么会导致这个异常？

 org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No
    at com.sun.corba.se.impl.logging.ORBUtilSystemException.writeErrorSend(Unknown Source)
        at com.sun.corba.se.impl.logging.ORBUtilSystemException.writeErrorSend(Unknown Source)
        at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.writeLock(Unknown Source)
        at com.sun.corba.se.impl.encoding.BufferManagerWriteStream.sendFragment(Unknown Source)
        at com.sun.corba.se.impl.encoding.BufferManagerWriteStream.sendMessage(Unknown Source)
        at com.sun.corba.se.impl.encoding.CDROutputObject.finishSendingMessage(Unknown Source)
        at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.finishSendingRequest(Unknown Source)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete1(Unknown Source)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(Unknown Source)
        at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(Unknown Source)
        at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(Unknown Source)
        at org.omg.CORBA.portable.ObjectImpl._is_a(Unknown Source)
        at weblogic.corba.j2ee.naming.Utils.narrowContext(Utils.java:126)
        at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:94)
        at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)
        at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
        at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
        at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
        at javax.naming.InitialContext.init(Unknown Source)
        at javax.naming.InitialContext.<init>(Unknown Source)
4

1 回答 1

1

这看起来像这个 Java 错误的症状 - http://bugs.sun.com/view_bug.do?bug_id=6553303

如果这是问题所在，那么解决方法是将生产机器上的 JVM 升级到更新的版本。错误报告的关闭细节告诉您修复所需的最低补丁级别（Java 5 和 Java 6）。

于 2012-07-21T11:43:45.813 回答