Question

在生产中运行我的代码时出现以下错误。但在qa环境或开发环境中也不会发生同样的情况。我想这可能是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)

Answer 1

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

如果这是问题，那么修复方法是将生产盒上的JVM升级到更新版本。错误报告的闭包详细信息告诉您修复所需的最低补丁级别（对于Java 5和Java 6）。

JMS异常这是什么类型的异常？

1 个答案: