CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed Error | Weblogic

Java

Environment : WLS 10.3.5, Solaris, SUN JDK 1.6.0_26

While testing the maximum JMS message size that WebLogic JMS can process.
However, only messages with a maximum size of around 100MB can be processed.
Then we see an error message on the JMS client side:

weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.MarshalException: CORBA COMM_FAILURE 1378079691 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 1378079691 Maybe; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: Maybe

 

Settings Snippet from config.xml:

<server>
<name>techpaste_server1</name>

<jms-thread-pool-size>0</jms-thread-pool-size>
<max-message-size>200000000</max-message-size>
<complete-message-timeout>60</complete-message-timeout>

....
</server>

Solution:

CORBA in the error message that WLS is using the IIOP client, which relies on the ORB in the JDK. That could be the source of the issue here.
Switch from wlclient.jar to wlthint3client.jar to bypass CORBA errors.

There are three options:

-wlthint3client.jar T3 Thin client (recommended)
-wlfulclient (full functionality but very large)
-wlclient.jar + wljmsclient.jar IIOP client (not recommended unless IIOP protocol is explicitly required; tends to be slower than other clients)

 

ClientTypeLanguageProtocolClient Class RequirementsKey Features
WL Full Client (T3)RMIJavaT3wlfullclient.jarSupports most WebLogic Server-specific features.
Supports WebLogic Server clustering.
Supports Certicom SSL.
Faster and more scalable than IIOP clients.
Supports most JavaEE features.
WL Thin T3 ClientRMIJavaT3wlthint3client.jarSmall Footprint
Supports WebLogic Server clustering.
Supports JSSE SSL, except with HTTP tunnelling.
Faster and more scalable than IIOP clients.
Supports most of WebLogic Server JMS (the major exception is the JMS SAF feature)
Supports most JavaEE features.
WLS-IIOP
(Introduced in WebLogic Server 7.0)
RMIJavaIIOPwlfullclient.jarSupports WebLogic Server-specific features.
Supports WebLogic Server clustering.
Supports Certicom SSL, except with HTTP tunnelling.
Faster and more scalable than IIOP thin clients.
Not ORB-based.
Does not support WebLogic Server JMS (use T3 protocol with same Jar instead).
Thin ClientRMIJavaIIOPwlclient.jar
JDK 1.5 and higher
Supports WebLogic Server clustering.
Supports many Java EE features, including security and transactions.
Supports SSL.
Uses CORBA 2.4 ORB.
CORBA/IDLCORBALanguages that OMG IDL maps to, such as C++, C, Smalltalk, COBOLIIOPno WebLogic classesUses CORBA 2.3 ORB.
Does not support WebLogic Server-specific features.
Does not support Java.
J2SE (or JSE)RMIJavaIIOPno WebLogic classesProvides connectivity to WebLogic Server environment.
Does not support WebLogic Server-specific features. Does not support many Java EE features.
Uses CORBA 2.3 ORB.
Requires use of com.sun.jndi.cosnaming. CNCtxFactory.
JMS Thin ClientRMIJavaIIOPwljmsclient.jar
wlclient.jar
JDK 1.5 and higher
Thin client functionality
WebLogic JMS, except for client-side XML selection for multicast sessions and JMSHelper class methods.
Supports SSL.
JMS SAF Client
(Introduced in WebLogic Server 9.2)
RMIJavaIIOPwlsafclient.jar
wljmsclient.jar
wlclient.jar
JDK 1.5 and higher
Locally stores messages on the client and forwards them to server-side JMS destinations when the client is connected.
Supports SSL.
JMS C Client
(Introduced in WebLogic Server 9.0)
JNICAnyAny WebLogic JMS capable Java client, such as wlfullclient.jarC client applications that can access WebLogic JMS applications and resources.
Supports SSL.
JMS .NET Client
(Introduced in WebLogic Server 10.3)
T3.NETT3WebLogic.Messaging.dll dynamic libraryMicrosoft .NET client applications, written in C#, that can access WebLogic JMS applications and resources.
WebLogic AQ JMS Client
(Introduced in WebLogic Server 10.3.1)
JNDI/JavaIIOP/T3 +aqapi.jar, o6.jar, orai18n.jar and the wlclient.jar, wlfullclient.jar, weblogic.jar (Install client), or wlthint3client.jar
JMXRMIJavaIIOPwljmxclient.jar
Web ServicesSOAPJavaHTTP/Swseeclient.jar
C++ ClientCORBAC++IIOPTuxedo librariesInteroperability between WebLogic Server applications and Tuxedo clients/services.
Supports SSL.
Uses CORBA 2.3 ORB.
Tuxedo Server and Native CORBA clientCORBA or RMIC++Tuxedo-General-Inter-Orb-Protocol
(TGIOP)
Tuxedo librariesInteroperability between WebLogic Server applications and Tuxedo clients/services.
Supports SSL and transactions.
Uses CORBA 2.3 ORB.

In case of any ┬ęCopyright or missing credits issue please check CopyRights page for faster resolutions.

Leave a Reply