What does it mean "org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: maybe it means?

Question

I get a very cryptic error when calling an EJB bean deployed on a weblogic 10.3.5 server.

Error:

javax.ejb.EJBException: CORBA MARSHAL 0 Maybe; nested exception is: org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe; nested exception is: org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.unwrapRemoteException(RemoteBusinessIntfProxy.java:121) at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:103) at $Proxy0.getOrder(Unknown Source) at test.EjbTest.main(EjbTest.java:37) Caused by: org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemException(MessageBase.java:897) at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:99) at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(CorbaMessageMediatorImpl.java:572) at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:430) at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:326) at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:129) at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457) at service._OrderSession_fb3odc_OrderSessionRIntf_Stub.getOrder(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85) ... 2 more 

An ejb binding is created using wlclient.jar :

 public static <T> T getRemoteEJB(String jndi, Class<T> clazz){ try { Properties props = new Properties(); props.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"); props.put(Context.PROVIDER_URL, "t3://localhost:7001"); InitialContext ctx = new InitialContext(props); T ejb = (T) ctx.lookup(jndi); PortableRemoteObject.narrow(ejb, clazz); return ejb; } catch (Exception e) { logger.error("Unable to lookup object of class {} through jndi name {}", clazz, jndi); } return null; } 

I can not find what this mysterious vmcid: 0x0 minor code: 0 completed: Maybe means, so please at least in order to understand what this means. The request ends on the server side, because there are no errors there.

Answer 1

A quick search for an error points to a link. One recommendation is not to use wlclient.jar , but weblogic.jar . Quoting the link,

Try using weblogic.jar on the client side or even better the ability to create "wlfullclient.jar" using the jarBuilder utility provided as part of WebLogic

The problem is Marshalling objects when using the WebLogic t3 protocol. Check out this link.

Answer 2

Another thing you could try on the client side is to use wlthint3client.jar. It comes with WebLogic 10.3.5 (in wlserver_10.3.5 \ server \ lib). It is larger than wlclient.jar, but much smaller than wlfullclient.jar. Warning if you use this: if the Swing client switches from iiop to t3, they will need to include smclientclasses.jar in their web start package, otherwise they will get errors. If the client does not use Swing, this should not be a problem.