The correct way to set up security for JMS is to go to the console, SELECT ACLS in the tree view, then create some access control lists.

• Set the ACL name which should be weblogic.jms.queue.QUEUENAME or weblogic.jms.TOPIC.TOPICNAME.
• elect Create.
• Enter the New Permission of send or receive.
• Select Create.
• Enter a comma separated list of users or groups.
• Select Grant Permission.
• Select "saved to the REALM IMPLEMENTATION" to save your changes.
• Select Yes.

This will update the fileRealm.properties file with lines that look like the following:

acl.send.weblogic.jms.queue.TestQueue1=user1
acl.receive.weblogic.jms.queue.TestQueue1=user1

If you don't have an ACL for a queue or topic, security is wide open.There are also ACL's for accessing the JNDI context; the JNDI context is a requirement for initially accessing JMS. 

The correct way to set up security for JMS is to go to the console, select ACLs in the tree view, then create some access control lists.

This will update the fileRealm.properties file with lines that look like the following:

acl.send.weblogic.jms.queue.TestQueue1=user1
acl.receive.weblogic.jms.queue.TestQueue1=user1

If you don't have an ACL for a queue or topic, security is wide open.There are also ACL's for accessing the JNDI context; the JNDI context is a requirement for initially accessing JMS.