weblogic.messaging.dispatcher.DispatcherException: CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 (Doc ID 1375989.1)

Last updated on DECEMBER 24, 2013

Applies to:

Oracle WebLogic Server - Version 10.3.5 and later
Information in this document applies to any platform.
***Checked for relevance on Dec 24th, 2013***

Symptoms

When testing the maximum JMS message size that WebLogic JMS can process, only messages with a maximum size of around 100MB are getting processed successfully. Once the message size exceeds 100MB below error is thrown on the JMS client side even though the maximum JMS Message size is configured to 300MB.

weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079691 Maybe; nested exception is: 
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: Maybe
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:116)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1293)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:796)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:548)
at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:401)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:385)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
at tc_msg_03.TC_MSG_03.startTest(TC_MSG_03.java:117)
at main.TestRunnerGUI$2.actionPerformed(TestRunnerGUI.java:103)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2319)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.Component.processMouseEvent(Component.java:6289)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3268)
at java.awt.Component.processEvent(Component.java:6054)
at java.awt.Container.processEvent(Container.java:2042)
at java.awt.Component.dispatchEventImpl(Component.java:4652)
at java.awt.Container.dispatchEventImpl(Container.java:2101)
at java.awt.Component.dispatchEvent(Component.java:4483)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Component.dispatchEvent(Component.java:4483)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
at java.awt.EventQueue.access$000(EventQueue.java:85)
at java.awt.EventQueue$1.run(EventQueue.java:604)
at java.awt.EventQueue$1.run(EventQueue.java:601)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
at java.awt.EventQueue$2.run(EventQueue.java:618)
at java.awt.EventQueue$2.run(EventQueue.java:615)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:175)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:162)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: weblogic.messaging.dispatcher.DispatcherException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079691 Maybe; nested exception is: 
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: Maybe
….

 

Snippet from Config.xml which shows the maximum JMS message size configured to 300MB.
<server>
   <name>osb_server1</name>
 
   <jms-thread-pool-size>0</jms-thread-pool-size>
    <max-message-size>300000000</max-message-size>
   <complete-message-timeout>60</complete-message-timeout>
   
   ....
 </server>
After upgrading the SUN JDK to the latest, the CORBA.COMM_FAILURE exception is thrown when the JMS message size reaches to 120-140 MB.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms