Why do the queue names appear to include jms-module name (+!) ?

Question

We upgraded our domain from weblogic 8.1 to 10.3.2.
To get the clustered environment to work, I had to delete the jms-module and recreate (including the FileStore, the Jms-server...).
After doing all this, When examining the Jms-server Active Destinations,
(In Settings - Monitoring - Active Destination)
I see the queue names such as:
jms-moduleName!queueName
I can't help but think this is related to this error message in the logs;
No servers found having jms destination queueName.
In our single server environment. I did not have to delete and recreate the autogenerated Jms-module and in Active Destinations, the Name shows up as I would expect. In this environment, I do not have the same error as above.
Is there anyway to stop the prefix, 'jms-moduleName!" from being added to the queue name in Active Destinations?
How and why is this being added?
Any comments would be greatly appreciated. THANKS.

Answer 1

Hi,
Almost all applications use a destination's JNDI name to look it up (see the JNDI name field for each destination). The "jms-moduleName!queueName" syntax your referenced is generated based on the configured name of the destination, not the JNDI name.
Some side advice since your setting up a new configuration:
* If your using distributed destination, I advise taking the opportunity to change your configuration to use the simpler"uniform distributed destination" option. 8.1 and older supported only the older "weighted distributed destination" behavior which requires that each member destination be configured individually -- this is unwieldy, and will (hopefully) be deprecated soon.
* See [ JMS Configuration Best Practices | http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG ] and [ JMS Performance and Tuning Check List | http://download.oracle.com/docs/cd/E14571_01/web.1111/e13814/jmstuning.htm#PERFM294 ].
* Always configure quotas and paging, and ensure they are tuned to prevent JVM out-of-memory (as per the JMS Perf and Tuning check list referenced above).
Hope this helps,
Tom
Edited by: TomB on Jun 20, 2010 7:00 PM