MDB starts to consume messages before fully initialization of JNDI names

AS: Websphere 8.5.5

MQ impl: SIB

During application startup MDB starts to invoke onMessage method, which in turn invokes initialContext.lookup in order to find specific bean. Sometimes (during variety of startup iterations) it returns null instead of reference to bean object.

This behavior is nondeterministic: in some startup iterations bean's context has time for all JNDI names initialization due to more longer MDB initialization and respectively a pause in message consumption.

Is there any workaround or magic IBM key to resolve issue ?

So, as everyone "love's" Websphere, it was without a doubt an IBM bug. Sorry, i lied.... it was TWO bugs at the same time.

• First : http://www-01.ibm.com/support/docview.wss?uid=swg1PI28099. Yep, you need to fix this bug yourself !!! Just add this jvm custom property to your server: com.ibm.ejs.j2c.J2CServerListener.activateEndpointsOnCRAStarted = true
• Second: http://www-01.ibm.com/support/docview.wss?uid=swg1PM62774 Yep, this one you need to fix ... drumroll ... by yourself too !!! Just add the second custom property to your server: com.ibm.ws.cdi.immediate.ejb.start = true