I suppose it is related to the security-setting of the messaging subsystem. Also you can add <security-enabled>false</security-enabled> to the hornetq-server element.
Also the security-realm of the remoting subsystem might come into play for the physical connection (you might remove it to unsecure).
You might have a look into the docs/schema/jboss-as-messaging*.xsd or you use the CLI interface to change the configuration, here you have tab-completition and help.
1 of 1 people found this helpful
The first thing to realize here is that you're dealing with 2 different types of security. The first is security on the JNDI call, the second is security on the messaging subsystem (i.e. HornetQ). As Wolf mentioned, you can disable security on the messaging subsystem by setting:
If you want to disable security for JNDI then (as Wolf mentioned) you can to remove the security-realm from the "remoting-connector".
Thank you! the problem has been resolved