2012-07-21 57 views
0

在生產中運行我的代碼時出現以下錯誤。但是在qa環境或開發環境中也是如此。我認爲這可能是jndi名稱中的一個問題。但我不是100%確定的。任何人都可以告訴我什麼會導致此異常?JMS異常這是什麼類型的異常?

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) 

回答

0

這看起來像這樣的Java缺陷的症狀 - http://bugs.sun.com/view_bug.do?bug_id=6553303

如果是這樣的問題,那麼解決方法是在您的生產箱升級JVM到較新的版本。錯誤報告的關閉細節會告訴您最低修補程序級別(對於Java 5 & Java 6),您需要修復此問題。