关于new InitialContext(prop)引起的错误

最近在调用JMS出现一些错误,有时候报:org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No,我引用的JAR:wlclient.jar, wljmsclient.jar,程序是一个由main方法启动的JAVA application,
请教各位能否分析问题原因?
错误行:at com.teradata.util.JmsUtil.<init>(JmsUtil.java:20) 源码:
Context ctx = new InitialContext(prop);//20行代码


org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.impl.logging.ORBUtilSystemException.writeErrorSend(ORBUtilSystemException.java:2231)
at com.sun.corba.se.impl.logging.ORBUtilSystemException.writeErrorSend(ORBUtilSystemException.java:2253)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.writeLock(SocketOrChannelConnectionImpl.java:933)
at com.sun.corba.se.impl.encoding.BufferManagerWriteStream.sendFragment(BufferManagerWriteStream.java:78)
at com.sun.corba.se.impl.encoding.BufferManagerWriteStream.sendMessage(BufferManagerWriteStream.java:96)
at com.sun.corba.se.impl.encoding.CDROutputObject.finishSendingMessage(CDROutputObject.java:144)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.finishSendingRequest(CorbaMessageMediatorImpl.java:247)
at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete1(CorbaClientRequestDispatcherImpl.java:342)
at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:323)
at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:129)
at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:213)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
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(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.teradata.util.JmsUtil.<init>(JmsUtil.java:20)
at com.teradata.processor.Processor.<init>(Processor.java:79)
at com.teradata.job.FileJob.start(FileJob.java:35)
at com.teradata.job.FileJob.process(FileJob.java:112)
at com.teradata.job.FileJob.execute(FileJob.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:235)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)


[该贴被wzkl于2010-05-20 13:59修改过]

开始我怀疑wljmsclient.jar和wlclient.jar发送JMS可能有问题,好像只能用weblogic.jar,后来有一篇文件解释说:this is Weblogic JMS thin client:


While the size of the full WebLogic JAR may not be a problem when you run server-side applications,
it does cause a very large footprint for enterprise-level client-server applications that may be running thousands of clients.
Having to deploy the full 20+ MB weblogic.jar file along with a client application can significantly increase the size of the deployed application,
possibly making it too big to be practical, as is the case with a Java applet-based client program.

At around 400 KB, the JMS thin application client (wljmsclient.jar) file provides a much smaller client footprint than the full WebLogic JAR,
by using a client-side library that contains only the set of supporting files required by client-side programs.
The JMS thin client also requires that you use the standard WebLogic thin application client (wlclient.jar),
around 300 KB, which contains the base client support for clustering, security, and transactions.

但是报的错无法解释了
原文:http://edocs.weblogicfans.net/wls/docs81/jms/thin_client.html
[该贴被wzkl于2010-05-20 16:56修改过]