user: NULL is not authenticated
gfreemankc Jun 17, 2004 2:52 PMWe're having an issue with our queue where we are unable to send messages to it after a period of inactivity. We're using JBoss 3.2.3 (on Windows)
The mq trace log has the following:
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] Connection Initializing
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] Getting the serverIL
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] serverIL=org.jboss.mq.il.jvm.JVMServerIL@b4faeb
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] Authenticating
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] Authenticating user null
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : authenticate
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.security.ServerSecurityInterceptor] Autenticating user null/null
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.security.SecurityManager] Username: null is authenticated
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.security.SecurityManager] Adding group : class org.jboss.security.NestableGroup Roles(members:guest)
The very next call (at a later time) has:
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] Connection Initializing
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] Getting the serverIL
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] serverIL=org.jboss.mq.il.jvm.JVMServerIL@b4faeb
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] Authenticating
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] Authenticating user null
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : authenticate
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.security.ServerSecurityInterceptor] Autenticating user null/null
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.sm.file.DynamicLoginModule] logout
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.security.SecurityManager] User: null is NOT authenticated
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.server.TracingInterceptor] EXCEPTION : authenticate:
javax.jms.JMSSecurityException: User: null is NOT authenticated
The thing I finde peculiar is the logout message.
The message sending code is:
QueueConnectionFactory queueFactory = (QueueConnectionFactory) context.lookup(factoryName); queueConnection = queueFactory.createQueueConnection();
and fails on the createQueueConnection() call (if it's not obvious).
The destination is configured as:
<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=myEvents"> <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends> <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends> <attribute name="SecurityConf"> <security> <role name="guest" read="true" write="true"/> <role name="publisher" read="true" write="true" create="false"/> </security> </attribute> </mbean>
We are also using the oracle persistence manager for our messages, and the conf/jbossmq-state.xml is unmodified:
<User> <Name>guest</Name> <Password>guest</Password> </User> *** Stuff removed *** <Role name="guest"> <UserName>guest</UserName> <UserName>john</UserName> </Role>
I hope I've provided the right amount of info, but please let me know if I left out a critical piece of info..
Best Regards