Cloud Pak for Integration

 View Only
Expand all | Collapse all

JNDI Configurations on CP4I for JSM nodes

  • 1.  JNDI Configurations on CP4I for JSM nodes

    Posted Mon February 26, 2024 12:32 PM

    2024-02-26 06:34:06.044 131 javax.naming.NameNotFoundException; remaining name '"/C:/JNDI-Directory"'
    2024-02-26 06:34:06.044 131 at com.sun.jndi.fscontext.FSContext.checkExists(FSContext.java:850)
    2024-02-26 06:34:06.044 131 at com.sun.jndi.fscontext.FSContext.checkIsDirectory(FSContext.java:883)
    2024-02-26 06:34:06.044 131 at com.sun.jndi.fscontext.FSContext.<init>(FSContext.java:108)
    2024-02-26 06:34:06.044 131 at com.sun.jndi.fscontext.FSContext.<init>(FSContext.java:81)
    2024-02-26 06:34:06.044 131 at com.sun.jndi.fscontext.RefFSContext.<init>(RefFSContext.java:97)
    2024-02-26 06:34:06.045 131 at com.sun.jndi.fscontext.RefFSContextFactory.createContext(RefFSContextFactory.java:42)
    2024-02-26 06:34:06.045 131 at com.sun.jndi.fscontext.RefFSContextFactory.createContextAux(RefFSContextFactory.java:47)
    2024-02-26 06:34:06.045 131 at com.sun.jndi.fscontext.FSContextFactory.getInitialContext(FSContextFactory.java:49)
    2024-02-26 06:34:06.045 131 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:705)
    2024-02-26 06:34:06.045 131 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:324)
    2024-02-26 06:34:06.045 131 at javax.naming.InitialContext.init(InitialContext.java:255)
    2024-02-26 06:34:06.045 131 at javax.naming.InitialContext.<init>(InitialContext.java:227)
    2024-02-26 06:34:06.045 131 at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:112)
    2024-02-26 06:34:06.045 131 at com.ibm.broker.jmsclienthelper.JMSClientHelper.setInitialContext(JMSClientHelper.java:845)
    2024-02-26 06:34:06.045 131 at com.ibm.broker.jmsclienthelper.JMSClientInputReplyHelper.getJMSInput(JMSClientInputReplyHelper.java:291)
    2024-02-26 06:34:06.045 131 at com.ibm.broker.jmsclientnodes.JMSClientInputNode.run(JMSClientInputNode.java:439)
    2024-02-26 06:34:08.296744: BIP4640E: ACE JMSClient. 'Broker 'integration_server'; Execution Group 'JMS-Integration-Server-1'; Message Flow 'test'; Node 'JMS Input::ComIbmJMSClientInputNode' ' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = 'com.sun.jndi.fscontext.RefFSContextFactory'. Location of the bindings = 'file:/C:/JNDI-Directory/'. ConnectionFactory Name = 'qcf1'. JMS destination = 'testJMSTopic1'. The exception text is : 'No Initial Context, Failure to obtain JNDI administered objects'.

    Kindly help in resolving the above error from the POD logs. 



    ------------------------------
    shreya soni
    ------------------------------


  • 2.  RE: JNDI Configurations on CP4I for JSM nodes

    Posted Tue February 27, 2024 05:53 AM

    I assume you mean App Connected Enterprise.

    Your error indicates it is looking for a file that does not exist (file:/C:/JNDI-Directory/).  Are you using MQ as your provider and trying to read the bindings file?  You will need to mount the file to the Pod and then reference the location.  If you have a hard coded reference, then you may want to override it.  More information in the knowledge center.

    Brian



    ------------------------------
    Brian S Paskin
    Sr. Technology Engineer
    IBM Cloud Engineering
    ------------------------------

    Original Message