Mar 2nd, 2006, 03:42 PM
Can Spring JMS not cache JNDI or redo JNDI lookup?
We have one app A subscribing messages from a queue in another server B. Whenever B is restarted (together with the associated JMS server), A also needs to restart because the JDNI lookup cached in A no longer work.
Does Spring JMS have any setting which will detect if a new JNDI lookup is required so that the app A doesn't need to restart if server B is restarted?
Mar 2nd, 2006, 04:09 PM
Set the cache property on your JndiObjectFactoryBean to false.