How to Avoid Anonymous Lookups on JMS Queues
Last updated on DECEMBER 19, 2016
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
When no credentials are provided in the initial context, by default a JMS client can lookup the JMS resources. It may be desired to remove this lookup.
Hashtable properties = new Hashtable();
// NOTE: The port number of the server is provided in the next line,
// followed by the userid and password on the next two lines.
Even without SECURITY_PRINCIPAL or SECURITY_CREDENTIALS, the JMS client program can connect to the server, lookup queues and read/write JMS messages.
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