Since this is really a security problem, you'll want to enable TRACE logging for org.jboss.security to find out what the real error message is.
"javax.jms.JMSSecurityException: User: guest is NOT authenticated" is just a generic error message. We don't want to help attackers know they've guessed a real user id by giving them too much detail in the error message. :-) GUESS: (you'd be better off asking in the security form once you know the real problem): JBossMQ authenticates users against a database table by default. Does changing the "runDate" also cause the connections to the database to become broken? e.g. because some 'timeout" processing is based on that date? If so, have you configured your datasource to check for invalid/broken connections? Or try flushing the pool of the datasource when you change the date. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225409#4225409 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225409 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
