I have search through this site for HOWTOs that would be useful to me in my current situation. I have explored the JBossSX Architecture literature in an effort to understand how JBoss handles authentication. In both cases I have not found a clue to solving the issue I am facing. The issue is the application log files are filling up with the below information: | 09:12:32,764 INFO [JMSContainerInvoker] Trying to reconnect to JMS provider for MY1MDB | 09:12:32,764 DEBUG [JMSContainerInvoker] Initializing | 09:12:32,764 DEBUG [JMSContainerInvoker] Looking up provider adapter: java:/DefaultJMSProvider | 09:12:32,764 DEBUG [JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JNDIProviderAdapter@12a375b | 09:12:32,764 INFO [JMSContainerInvoker] Trying to reconnect to JMS provider for MY2MDB | 09:12:32,764 DEBUG [DLQHandler] Creating DLQHandler | 09:12:32,764 DEBUG [JMSContainerInvoker] Initializing | 09:12:32,764 DEBUG [JMSContainerInvoker] Looking up provider adapter: java:/DefaultJMSProvider | 09:12:32,764 DEBUG [DLQHandler] Using factory: org.jboss.mq.SpyXAConnectionFactory@19c2931 | 09:12:32,764 DEBUG [JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JNDIProviderAdapter@12a375b | 09:12:32,764 DEBUG [DLQHandler] Creating DLQHandler | 09:12:32,764 DEBUG [DLQHandler] Using factory: org.jboss.mq.SpyXAConnectionFactory@19c2931 | 09:12:32,764 DEBUG [DLQHandler] Initialization failed DLQHandler | javax.jms.JMSSecurityException: User: null is NOT authenticated | at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:230) | at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:66) | at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:613) | at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:172) | at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:165) | at org.jboss.mq.Connection.authenticate(Connection.java:1065) | at org.jboss.mq.Connection.<init>(Connection.java:252) | at org.jboss.mq.Connection.<init>(Connection.java:323) | at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:116) | at org.jboss.mq.SpyConnectionFactory.internalCreateConnection(SpyConnectionFactory.java:137) | at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:108) | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:187) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:510) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428) | at java.lang.Thread.run(Thread.java:595) | 09:12:32,764 DEBUG [DLQHandler] Initialization failed DLQHandler | javax.jms.JMSSecurityException: User: null is NOT authenticated | at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:230) | at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:66) | at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:613) | at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:172) | at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:165) | at org.jboss.mq.Connection.authenticate(Connection.java:1065) | at org.jboss.mq.Connection.<init>(Connection.java:252) | at org.jboss.mq.Connection.<init>(Connection.java:323) | at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:116) | at org.jboss.mq.SpyConnectionFactory.internalCreateConnection(SpyConnectionFactory.java:137) | at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:108) | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:187) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:510) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428) | at java.lang.Thread.run(Thread.java:595) | 09:12:32,764 ERROR [JMSContainerInvoker] Reconnect failed: JMS provider failure detected for MY1MDB | javax.jms.JMSSecurityException: User: null is NOT authenticated | at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:230) | at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:66) | at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:613) | at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:172) | at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:165) | at org.jboss.mq.Connection.authenticate(Connection.java:1065) | at org.jboss.mq.Connection.<init>(Connection.java:252) | at org.jboss.mq.Connection.<init>(Connection.java:323) | at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:116) | at org.jboss.mq.SpyConnectionFactory.internalCreateConnection(SpyConnectionFactory.java:137) | at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:108) | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:187) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:510) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428) | at java.lang.Thread.run(Thread.java:595) | 09:12:32,764 ERROR [JMSContainerInvoker] Reconnect failed: JMS provider failure detected for MY2MDB | javax.jms.JMSSecurityException: User: null is NOT authenticated | at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:230) | at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:66) | at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:613) | at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:172) | at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:165) | at org.jboss.mq.Connection.authenticate(Connection.java:1065) | at org.jboss.mq.Connection.<init>(Connection.java:252) | at org.jboss.mq.Connection.<init>(Connection.java:323) | at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:116) | at org.jboss.mq.SpyConnectionFactory.internalCreateConnection(SpyConnectionFactory.java:137) | at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:108) | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:187) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:510) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428) | at java.lang.Thread.run(Thread.java:595) | 09:12:32,764 DEBUG [JMSContainerInvoker] innerStop | 09:12:32,764 DEBUG [JMSContainerInvoker] innerStop | 09:12:32,764 DEBUG [DLQHandler] Destroying DLQHandler | 09:12:32,764 DEBUG [DLQHandler] Destroying DLQHandler | 09:12:32,764 DEBUG [DLQHandler] Destroyed DLQHandler | 09:12:32,764 DEBUG [DLQHandler] Destroyed DLQHandler | 09:12:32,764 INFO [JMSContainerInvoker] Waiting for reconnect internal 10000ms for MY1MDB | 09:12:32,764 INFO [JMSContainerInvoker] Waiting for reconnect internal 10000ms for MY2MDB | What I have done is moved my application over from 4.0.3SP1 to 4.0.5. Everything was working fine in 4.0.5 involving the MDBs. As I was working with some of the cofiguration files solving other issues, JBoss has has detected some changes in the configuration files and has refreshed its settings. This has turned on JAAS for the MBDs. I have never required authentication for my MDBs. I do not use the <run-as> tag, so having it failing now is perplexing. Because I am new to JBoss, I would like to empty any cached setting JBoss has and have the server refresh the setting to ensure all is set properly. Next, I would like to know how can I stop JBoss from being denied access to the MDBs. Thank you in advance for taking the time to read my post. Russ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995332#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...