WebLogic Server 10.3.4 - JMS Topic Disappears When App Is Deployed In Cluster After App Restart resulting in BEA-010061: MessageDrivenEJB is unable to connect to the JMS destination
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.4 to 126.96.36.199
Information in this document applies to any platform.
***Checked for relevance on 22-Jan-2015***
Application is packaged with a JMS module. When the application is deployed its JMS module is deployed as well and the JMS resources are available in the JNDI tree. The application's state is 'active' and is accessible. But whenever the application is stopped using the console option the app's JMS module is moved to PREPARED State and its resources (such as UDQ or UDT etc) are unbound from the JNDI tree. On application start the JMS module becomes ACTIVE but the module resources fail to bind. Hence the JNDI is missing the entries and the find call is failing.
Steps to Reproduce:
- Create a Weblogic 10.3.4 domain with 2 Managed Servers in a Cluster.
- Create 2 JMS Servers and target them to each managed server.
- Deploy the "enterprise" application which would create a"JobSchedulerTopic" (Uniform Distributed Topic) and a "JMSSubdeployment"targeted to both JMS Servers.
- Stop the application and start it again.
- Application goes to Warning state and in the View JNDI Tree the "JobSchedulerTopic" disappears.
- The managed servers have to be restarted to bring back the application to ACTIVE state.
The following error can be seen in the logs:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms