NameNotFoundException When JMS Manually Migrating Back A Migratable WLS Server
Last updated on DECEMBER 11, 2017
Applies to:Oracle Weblogic Server - Version 10.3.2 and later
Information in this document applies to any platform.
Exception "javax.naming.NameNotFoundException" when manually migrating back a migratable Weblogic server that contains JMS resources like a JMS distributed queue. On this cluster a Message-Driven Bean (MDB) is also deployed to consume messages from a local JMS distributed queue.
Complete exception received by the MDB :
<BEA-010061> <The Message-Driven EJB: jmsMessageformat is unable to connect to the JMS destination: test_jms.QueueSend. The Error was: javax.naming.NameNotFoundException: While trying to lookup 'test_jms.QueueSend' didn't find subcontext 'test_jms'. Resolved ''; remaining name 'test_jms/QueueSend'
Current configuration :
Weblogic 10.3.2 domain with a cluster distributed over several machines.
MDB deployed on the cluster to consume JMS messages.
The JMS service is configured to be automatically migrated :
- JMS servers (one per managed server) are targeted on migratable resources of cluster
- JMS resources (queues and factories) are targeted on the cluster (NOT on Migratable servers).
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