Production Redeployment Not Possible As It Results In A Loss Of The JNDI Tree
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When trying a production redeployment the JNDI tree is lost.
The error only occurs if the old version of the application contains message driven beans that are pointing to a "foreign jms server". If the JMS queues are running in the same cluster as the application, the JNDI won't get lost during production redeployment. The JNDI tree is lost in the moment when the old version is shut down (and gets into the "outdated" state).
During the time where both versions run in parallel, the JNDI tree is still valid.
Despite of the JNDI tree loss, the rest of the application seems to be running. In particular, the message driven beans are still occuring as consumers on the queues.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms