karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shrish Srivastava (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-2095) Camel Route (JMS Polling) not working when installing feature "jndi"
Date Wed, 02 Jan 2013 15:38:12 GMT
Shrish Srivastava created KARAF-2095:
----------------------------------------

             Summary: Camel Route (JMS Polling) not working when installing feature "jndi"
                 Key: KARAF-2095
                 URL: https://issues.apache.org/jira/browse/KARAF-2095
             Project: Karaf
          Issue Type: Bug
          Components: karaf-core
    Affects Versions: 2.2.9
         Environment: Windows/Linux
            Reporter: Shrish Srivastava


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)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message