Feb 22nd, 2010, 11:11 AM
Does Spring handle stale JNDI destinations?
Reading the WebLogic documentation http://download.oracle.com/docs/cd/E...html#wp1311973 it states:
..some JMS providers, like WebLogic JMS, may invalidate a Destination object after a server failure. So, if the EJB runs on Server A, and JMS runs on Server B, then the EJB on Server A will have to perform the JNDI lookup of the objects from Server B again after that server has recovered.
So if I am using Spring to load all my JNDI objects at context startup, will it handle doing to re-lookups automatically if my JMS Provider does invalidate the Destination object?
Thanks for any help,