javax.naming.NamingException: ConnectionFactoryImpl reference is null

ibm.com | 7 months ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    WASdev | Using WebSphere MQ with the Liberty profile - WASdev

    ibm.com | 7 months ago
    javax.naming.NamingException: ConnectionFactoryImpl reference is null

    Root Cause Analysis

    1. javax.naming.NamingException

      ConnectionFactoryImpl reference is null

      at com.ibm.mq.connector.outbound.ConnectionFactoryImpl.getReference()
    2. com.ibm.mq
      ConnectionFactoryImpl.getReference
      1. com.ibm.mq.connector.outbound.ConnectionFactoryImpl.getReference(ConnectionFactoryImpl.java:305)
      1 frame
    3. org.apache.aries
      OSGiObjectFactoryBuilder.getObjectInstance
      1. org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstance(ObjectFactoryHelper.java:64)
      2. org.apache.aries.jndi.OSGiObjectFactoryBuilder.getObjectInstance(OSGiObjectFactoryBuilder.java:57)
      2 frames
    4. Java RT
      NamingManager.getObjectInstance
      1. javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283)
      1 frame
    5. com.ibm.ws
      WSContext.lookup
      1. com.ibm.ws.jndi.internal.WSContext.resolveObject(WSContext.java:128)
      2. com.ibm.ws.jndi.internal.WSContext.lookup(WSContext.java:296)
      3. com.ibm.ws.jndi.internal.WSContext.lookup(WSContext.java:291)
      3 frames
    6. org.apache.aries
      DelegateContext.lookup
      1. org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)
      1 frame
    7. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:392)
      1 frame
    8. Spring Context
      JndiTemplate$1.doInContext
      1. org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154)
      1 frame