I experienced the exact same problem in 5.0. Everything worked fine for 4.1. In 5.0, when vm transport is initializing, it goes through authorization and fails since there is no correct username/password.
-- View this message in context: http://www.nabble.com/Trouble-with-JAAS---5.0.0-tp14250971s2354p14308173.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
