One thing I have figured out was that the behaviour changed from version 3.0.6 to 3.0.7.
It worked the way I wanted in 3.0.6, in 3.0.7 something changed and I can't determine what that is yet. Only thing I can see in the release notes that may be involved is "Allow dispatch to j_security_check"
The broken behaviour is also around in 3.2.1
Thanks for any help,
If you figure it out, I'd like to know too ;-)
Any update on this ?
It is a bit of a stopper on releasing anything for Jboss since it exists in both 3.0.7 and 3.2.1 (whereas, as the original poster mentioned was fine in all up to 3.0.6). It appears that JBoss is 'losing' the Default Context somewhere in the JAAS authenticate process with a failure.
I'll answer my question ... upon searching down the bugs on Sourceforge, it appears it is (was) a bug in Jetty (was fixed by Greg Wilkins) and will be merged back into JBoss soon. I'll maybe give the JBoss-Tomcat bundle a go since is supposedly fine there.
I've been having this same issue. Any news on when it will be fixed? I'm using JBoss 3.0.6.
Fixed in JBoss 3.0.8.
Will this be fixed in JBoss 3.2.1? I don't want to fall back to 3.0.8