On 10.01.2012 16:28, Rainer Jung wrote:
The below observation seems to be fixed now, after Mark's enhancements
to Realms and the unit tests.
Regards,
Rainer
One observation, unrelated to the failure we were discussion above: if I
dump all MBeans out of curiousity in the middle of TestRegistration,
then I get a reproducible failure at the end:
[junit] 10-Jan-2012 15:44:24.286 INFO [main]
org.apache.catalina.mbeans.TestRegistration.testMBeanDeregistration
[junit] 10-Jan-2012 15:44:24.290 INFO [main]
org.apache.catalina.mbeans.TestRegistration.testMBeanDeregistration
Name: Tomcat:type=Realm,realmPath=/realm0
[junit] modelerType: org.apache.tomcat.util.modeler.BaseModelMBean
[junit] appName: Tomcat
[junit] realmPath: /realm0
[junit] stateName: STOPPED
[junit] allRolesMode: strict
[junit] className: org.apache.catalina.realm.JAASRealm
[junit] useContextClassLoader: true
[junit] validate: true
It seems the MBean for that Realm is created somehow when I query the
other MBeans and retrieve their arguments, although the JAASRealm itself
logs
JAASRealm.setContainer Set JAAS app name Tomcat
much earlier.
If I dump all MBeans twice, then in the second dump the Realm MBean is
contained (not in the first dump):
Name: Tomcat:type=Realm,realmPath=/realm0
modelerType: org.apache.tomcat.util.modeler.BaseModelMBean
appName: Tomcat
realmPath: /realm0
stateName: STARTED
allRolesMode: strict
className: org.apache.catalina.realm.JAASRealm
useContextClassLoader: true
validate: true
But it seems it is never deresitered/destroyed during the test.
Thought you might be interested because of the "Re: problem using
default Realm in new unit tests" discussion going on in parallel.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
