Uploaded image for project: 'Karaf'
  1. Karaf
  2. KARAF-2095

Camel Route (JMS Polling) not working when installing feature "jndi"

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.2.9
    • 2.4.0, 3.0.2, 2.3.6, 4.0.0.M3
    • karaf
    • None
    • Windows/Linux

    Description

      We have a route which polls on a weblogic jms queue.If we do not have "feature jndi" installed, the route work fine.On installing jndi feature,it work fine if we do not restart the container. On restarting the container it throws following exception.
      ---------------------------------------------------------------------------
      013-01-02 16:06:22,723 | WARN | JmsConsumer[IN] | faultJmsMessageListenerContainer | 101 - org.springframework.jms - 3.0.7.RELEASE | Could not refresh JMS Connection for destination 'IN' - retrying in 5000 ms. Cause: JndiObjectTargetSource failed to obtain new target object; nested exception is javax.naming.ConfigurationException: rmiURLContextFactory.getObjectInstance: argument must be an RMI URL String or an array of them
      org.springframework.jndi.JndiLookupFailureException: JndiObjectTargetSource failed to obtain new target object; nested exception is javax.naming.ConfigurationException: rmiURLContextFactory.getObjectInstance: argument must be an RMI URL String or an array of them
      ----------------------------------------------------------------------------
      I enclosed the following files:
      1)log file for my test(karaf.log)
      2)Test project as attachment(wls_jmspolling.zip)

      Attachments

        1. jndibugtest.zip
          19 kB
          Antoni Mylka
        2. karaf.log
          1.00 MB
          Shrish Srivastava
        3. wls_jmspolling.zip
          2.64 MB
          Shrish Srivastava

        Activity

          People

            jbonofre Jean-Baptiste Onofré
            shrishs Shrish Srivastava
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: