javax.jms.JMSSecurity Exception: User: xxx is NOT authentica

[rf360m]

Has the manner in which you set up users and passwords for use with JMS topics and queues changed since jboss 3.2? I had no problem with version 3.2 in setting up a topic that required authentication of a user and password before joining. However, in version 4.0.5 I am unable to do this. I always get a javax.jms.JMSSecurity Exception: User: xxx is NOT authenticated.

I have set up the xml files in the same way as I did for version 3.2. I have also searched the web for an answer but have not found one.

Any advice on how to set this up would be most appreciated.

Thanks!

[mkobold]

Check the $JBOSS_HOME/server/default/deploy/jms/*-jdbc-state-service.xml

Verify the data-source JNDI name it is configured to use, also make sure that the role and identities are present in the target database table (jms_roles). At the very least the table can be dropped and JBossMQ will re-create the table and auto-populate the table.