Error "org.omg.CORBA.portable.UnknownException: vmcid: 0x0 minor code: 0 completed: Maybe]"

I was bugged by this error yesterday. I didn't have any clue. I tried to do clean build on WID (WebSphere Integeration Developer). Its doesn't help. Restarted the server couple of times, removed from the server and published again no way & no improvements not even a single step forward.

Exception stack trace: javax.naming.NamingException: Error during resolve [Root exception is org.omg.CORBA.portable.UnknownException: vmcid: 0x0 minor code: 0 completed: Maybe]
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1939)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1862)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1552)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1354)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:172)
at javax.naming.InitialContext.lookup(InitialContext.java:363)
at com.ibm.ws.sca.internal.ejb.util.EJBLocator$JndiLocator.locate(EJBLocator.java:464)
at com.ibm.ws.sca.internal.ejb.util.EJBLocator.locate(EJBLocator.java:442)
at com.ibm.ws.sca.internal.ejb.util.EJBObjectFactory.createStub(EJBObjectFactory.java:72)
at com.ibm.ws.sca.internal.ejb.util.EJBStubAdapter.getStub(EJBStubAdapter.java:87)
at com.ibm.ws.sca.internal.ejb.util.EJBStubHelper.lookup(EJBStubHelper.java:89)
at com.ibm.ws.sca.internal.ejb.util.EJBStubHelper.lookup(EJBStubHelper.java:82)
at com.ibm.ws.sca.internal.binding.handler.SCAImportBindingHandler.getExportEJBStub(SCAImportBindingHandler.java:146)
at com.ibm.ws.sca.internal.binding.handler.SCAImportBindingHandler.processMessage(SCAImportBindingHandler.java:221)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:725)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1166)
at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:843)
at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.processUOWMessage(ModuleSessionBean.java:338)
at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.transactionNotSupportedActivitySessionNotSupported(ModuleSessionBean.java:287)
at com.ibm.wsspi.sca.ejb.module.EJSLocalStatelessModule_43132892.transactionNotSupportedActivitySessionNotSupported(EJSLocalStatelessModule_43132892.java:131)
at com.ibm.ws.sca.internal.uow.handler.UOWStrategyImpl.transactionLocalActivitySessionFalse(UOWStrategyImpl.java:386)
at com.ibm.ws.sca.internal.uow.handler.JoinUOWHandler.processMessage(JoinUOWHandler.java:131)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:725)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1166)
at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:834)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.SCAInvocationAction.invokeSync(SCAInvocationAction.java:531)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.RetryControl.invokeByStyle(RetryControl.java:327)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.RetryControl.invokeWithRetry(RetryControl.java:221)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.ServiceInvocation.complete(ServiceInvocation.java:124)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.FlowActionFactoryImpl.create(FlowActionFactoryImpl.java:667)
at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.invokeFlowAction(ServiceInvokeMediation.java:469)
at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.mediate(ServiceInvokeMediation.java:390)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:323)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.SIBXJavaMediationPrimitive.invoke(SIBXJavaMediationPrimitive.java:93)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:419)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:345)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:419)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:345)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:419)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:345)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.SIBXJavaMediationPrimitive.invoke(SIBXJavaMediationPrimitive.java:93)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:419)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:345)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.Input.invoke(Input.java:137)
at com.ibm.ws.sibx.scax.mediation.engine.RequestFlow.invokeFlow(RequestFlow.java:132)
at com.ibm.ws.sibx.scax.mediation.engine.MediationFlow.invokeRequestFlow(MediationFlow.java:135)
at com.ibm.wsspi.sibx.mediation.flow.ejb.MediationFlowBean.invokeRequestFlow(MediationFlowBean.java:230)
at com.ibm.wsspi.sibx.mediation.flow.ejb.EJSLocalStatelessMediationFlow_f5ad87fe.invokeRequestFlow(EJSLocalStatelessMediationFlow_f5ad87fe.java:127)

I got tensed thinking of the whole day, will go in vain in debugging this issue. Search didn't give us much information. Then got some clue from devworks forum. Oops there were lot of unanswered questions, few of them got some suggestions same as clean+build and deploy.

I tried a different combination, removed the project from server. (checked in the admin console). Delete all the projects which are generated by WID (App,EJB and WEB Projects). Then do a clean build and deploy application. Mostly this works b'coz it worked for me.

Note : Even after the below steps your facing the problem check in devworks or open a PMR with IBM.

BO Map Failure at runtime with null pointer Exception

The issue is the BO Map was failing at runtime giving null ponter exception at a custom map, i got really confused looked every thing in the custom map. All the value was checked to null or it is intialized to default. After doing all this again the same error kept on throwing.

Wait i remember something, i checked the right hand side BO (to BO) to which value needs to be assigned. That particular BO was null. Why this ? :-(

There is a file named map.config.properties which is located in runtimes/properties/ folder of your WID/WPS installation location. That file has an important property set which is

createChildBOsbyDefault=false




if this is set to false if there is custom mapping where the value needs to set to a particular field of the BO, at first we need to create the BO otherwise there should be move option to that particular. unless the above two occurs the BO will be always null. If you try to assign a value to field in the BO. It will throw null pointer exception (check the above screenshot)

In order to overcome the issue, before doing a custom assign to variable to the BO, first create that BO or make a move. The move should be always before the custom assign (exceution order) check the below screen shot

TKDL Traditional Knowledge Digital Library

TKDL, Traditional Knowledge Digital Library is a mammoth effort by indian goverment to save the bio-piracy battle. India home of ayurvedic, unani and siddha medicines and has history that traces back to more than 5,000 years ago.

These This knowledge has generally been passed down by word of mouth from generation to generation. A part of this knowledge has been described in ancient classical and other literature, often inaccessible to the common man and even when accessible rarely understood. Documentation of this existing knowledge, available in public domain, on various traditional systems of medicine has become imperative to safeguard the sovereignty of this traditional knowledge and to protect it from being misappropriated in the form of patents on non-original innovations, and which has been a matter of national concern.

India fought successfully for the revocation of turmeric and basmati patents granted by United States Patent and Trademark Office (USPTO) and neem patent granted by European Patent Office (EPO). As a sequel to this, in 1999, the Department of Ayurveda, Yoga & Naturopathy, Unani, Siddha and Homoeopathy-(AYUSH),erstwhile Department of Indian System of Medicine and Homoeopathy(ISM&H) constituted an inter-disciplinary Task Force, for creating an approach paper on establishing a Traditional Knowledge Digital Library (TKDL).

The project TKDL involves documentation of the knowledge available in public domain on traditional knowledge from the existing literature related to Ayurveda, Unani,Siddha and Yoga, in digitized format in five international languages which are English, German, French, Japanese and Spanish.

Under normal circumstances, a patent application should always be rejected if there is prior existing knowledge about the product.But in most of the developed nations like United States, "prior existing knowledge" is only recognized if it is published in a journal or is available on a database - not if it has been passed down through generations of oral and folk traditions.

But now we have TKDL

Review Naan Kadavul

Naan Kadavul is from bala, as his previous movies this has also become a master piece. Almost all the departments of the movie are superb.Ilaiyaraaja has once again given a wonderful music and background score (he is the only man who can do this). Arya was unimaginable with his previous chocolate boy characters this movie brings the acting part, pooja was also equally good. But in my point arya did a amazing job.

These kind of movies bring lots of fresh blood in to the tamil movie industry.Bala has sculpterd this movie with arya and has taken almost three years to complete it.I think the time he took is worth.Arthur Wilson did his own way of magic and brought lot of richness to the film.

The movie plays around arya and has captured the life of Aghori, who are a sect of sadhus. Wonder full piece of movie from bala. must watch.

In my point of view its superb movie.

using promoted properties websphere enterprise service bus aka ESB

The concept of the promoted property is dynamic change without restarting or reinstalling the application again. ESB is used mostly in integeration space. Each and every down time of app change counts. This is very good feature. The implemenatation example goes like this.

For example there is two type of implementations which will be used in the mediation flow, only one of the implementation will be used which one to use will can be configured using the promoted property.


Use "MessageFilter" primitive. In the details select the distribution as "First" . And in the filters tab using xpath create two terminals "match1" and "match2".Click on the promoted properties you can see the filter property is promoted field. select the two field and give alias name different.

Wire the "match1" terminal to one application and "match2" to other application.


Deploy the application. Log in to the admin console. Go the sca modules. This will display all the applications deployed in the server.Select the application and then select mdoule properties there you can see your two properties



Give the value such that it passes one condition (it will use one application at a time). If you gave both the conditions as true. since you have given distribution as first. The first condtion matched terminal will be fired.

If you want all the terminals to be fired then set the distribution property as "All". It will the check all the conditions and fires which ever matching