We'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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839136#3839136 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839136 ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
