Can you put the source code of your getting the connection here? The code may help us find out what's the problem. Thanks.
I am changed the dsJndiName default value as my local datasource jndi-name in conf/login-config.xml file.
Now it is working fine.
We are currently using JBoss v4.2.3.ga and have upgraded JBoss messaging to v 1.4.4 and JBoss remoting to v2.2.3.
JMS messages are sent & received without any exceptions for initial 3-4 days. After that we are observing exception messagesjavax.jms.JMSSecurityException: User null is NOT authenticated, whenever we are trying to create the connection.
We have seen that there is no deadlock on JBoss AS and other DB operations are working normally.
We are using the following security domain for JMS
<login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"
flag = "required">
<module-option name = "unauthenticatedIdentity">guest</module-option>
<module-option name = "dsJndiName">java:/DefaultDS</module-option>
<module-option name = "principalsQuery">SELECT PASSWD FROM JBM_USER WHERE USER_ID=?</module-option>
<module-option name = "rolesQuery">SELECT ROLE_ID, 'Roles' FROM JBM_ROLE WHERE USER_ID=?</module-option>