IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
  • 1.  jndi.properties cache issue

    Posted 05/19/14 10:36 PM

    Originally posted by: DSTX_HOME


    Hi everyone,

    I am having a very strange issue.  I have been using JMS adapter to connect to AMQ. As part of it, I was having supporting jar files and jndi.ini files under lib.

    The absolute path for this lib is defined in dtx.ini file.  Recently I had to add another queue name in jndi.properties file.  After modification, I noticed, whenever I do bounce launcher, engine does not read jndi.properties settings and throw error in .mal file.   Description from .mal file given below..

    Has anyone experienced similar issue ?  Before modifying jndi.properties file with new queue, it was working for almost 9 months without any issue. Other than queue variable, nothing else changed as far as infrastructure and server settings are concerned.  I never had CLASSPATH OR LIBPATH defined in launcher properties file but jar location was defined in dtx.ini.    Let me know if you have something to add here..    Thanks.

     

    Another point : I noticed, if I touch jndi.properties files after stopping launcher and then bring up. It does not create this error. But if I just stop and start launcher, start throwing below error.

     

    <54263944-41381-Fri May 16 03:06:24 2014>: The file was created by JMS adapter from IBM Corporation
    <54263944-41381-Fri May 16 03:06:24 2014>: The file was created or updated on or around Fri May 16 03:06:24 EDT 2014
    <54263944-41381-Fri May 16 03:06:24 2014>:         @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue]
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue]
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue]
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue]
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue]
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue]
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropFromCmdValue] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.setAdapterPropsFromCmdline] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.doCmdlineFinalSanityCheck]
    <54263944-41381-Fri May 16 03:06:24 2014>: | >>>>By a cursory check, command combinations or syntax appears to be correct
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.doCmdlineFinalSanityCheck] (rc = 0) OK
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.validateProperties] (rc = 0) OK
    <54263944-43438-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.compareConnection]
    <54263944-43438-Fri May 16 03:06:24 2014>: | >>>Cannot reuse connection, we have a mismatch of one or more of jm, ictxf, ictxfurl
    <54263944-43438-Fri May 16 03:06:24 2014>: | In fact, everything starting from initCTX must be recreated
    <54263944-43438-Fri May 16 03:06:24 2014>: | Connection will not be reused
    <54263944-43438-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.compareConnection] (rc = 0) OK
    <54263944-42924-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.compareConnection]
    <54263944-42924-Fri May 16 03:06:24 2014>: | >>>Cannot reuse connection, we have a mismatch of one or more of jm, ictxf, ictxfurl
    <54263944-42924-Fri May 16 03:06:24 2014>: | In fact, everything starting from initCTX must be recreated
    <54263944-42924-Fri May 16 03:06:24 2014>: | Connection will not be reused
    <54263944-42924-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.compareConnection] (rc = 0) OK
    <54263944-44209-Fri May 16 03:06:24 2014>: [m4jms:MConnectionImpl.connect]
    <54263944-44209-Fri May 16 03:06:24 2014>: | [m4jms:M4jmsutility.getInitCtx]
    <54263944-44209-Fri May 16 03:06:24 2014>: | [m4jms:M4jmsutility.getInitCtx] (rc = 0) OK
    <54263944-44209-Fri May 16 03:06:24 2014>: | Connecting...
    <54263944-44209-Fri May 16 03:06:24 2014>: | [m4jms:M4jmsutility.getQueueCF]
    <54263944-44209-Fri May 16 03:06:24 2014>: | | ****Error during connFac lookup:javax.naming.NameNotFoundException: connectionFactory
    <54263944-44209-Fri May 16 03:06:24 2014>: | [m4jms:M4jmsutility.getQueueCF] (rc = 0) OK
    <54263944-44209-Fri May 16 03:06:24 2014>: | [m4jms:M4jmsutility.getInitCtx]
    <54263944-44209-Fri May 16 03:06:24 2014>: | | Replacing connection context associated with env_org.apache.activemq.jndi.ActiveMQInitialContextFactory_failover:(ssl://for security reason, I have removed failover server details from here...)
    <54263944-44209-Fri May 16 03:06:24 2014>: | [m4jms:M4jmsutility.getInitCtx] (rc = 0) OK
    <54263944-44209-Fri May 16 03:06:24 2014>: | [m4jms:M4jmsutility.getQueueCF]
    <54263944-44209-Fri May 16 03:06:24 2014>: | | ****Error during connFac lookup:javax.naming.NameNotFoundException: connectionFactory
    <54263944-44209-Fri May 16 03:06:24 2014>: | [m4jms:M4jmsutility.getQueueCF] (rc = 0) OK
    <54263944-44209-Fri May 16 03:06:24 2014>: | Error during connection creation (sc=11).
    <54263944-44209-Fri May 16 03:06:24 2014>: [m4jms.MConnectionImpl.connect (sc=11)] (rc = -2) *** ERROR ***
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.onNotify]
    <54263944-41381-Fri May 16 03:06:24 2014>: | PREPARE_DESTROY
    <54263944-41381-Fri May 16 03:06:24 2014>: [m4jms:MAdapterImpl.onNotify] (rc = 0) OK
     


    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 2.  Re: jndi.properties cache issue

    Posted 05/22/14 05:26 AM

    Originally posted by: paul.brett


    If the the only change you made was 'add another queue name in jndi.properties file', then it is possible you have reached some sort of limit for the file content, or placed an unknown character in there.

    I think you need to raise this as a PMR to get it replicated in the lab, and possibly rectified.

    Thank-you.

    Paul

    Follow me on Twitter


    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange