Easy to find on jmx-console: log in to http://localhost:8080/jmx-console/
click on link to service=JNDIView click on button 'Invoke' to MBean operation String list() look in the java: Namespace section, under the jaas branch, on my server the section looks like this: | +- XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory) | +- DefaultDS (class: javax.sql.DataSource) | +- SecurityProxyFactory (class: org.jboss.security.SubjectSecurityProxyFactory) | +- DefaultJMSProvider (class: org.jboss.jms.jndi.JNDIProviderAdapter) | +- comp (class: javax.naming.Context) | +- ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory) | +- jdbc (class: org.jnp.interfaces.NamingContext) | | +- SurveyDS (class: javax.sql.DataSource) | | +- RealmDS (class: javax.sql.DataSource) | | +- LinklibDS (class: javax.sql.DataSource) | | +- UserDS (class: javax.sql.DataSource) | +- JmsXA (class: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl) | +- jaas (class: javax.naming.Context) | | +- JmsXARealm (class: org.jboss.security.plugins.SecurityDomainContext) | | +- jbossmq (class: org.jboss.security.plugins.SecurityDomainContext) | | +- HsqlDbRealm (class: org.jboss.security.plugins.SecurityDomainContext) | +- timedCacheFactory (class: javax.naming.Context) | Failed to lookup: timedCacheFactory, errmsg=org.jboss.util.TimedCachePolicy | +- TransactionPropagationContextExporter | +- StdJMSPool (class: org.jboss.jms.asf.StdServerSessionPoolFactory) | +- Mail (class: javax.mail.Session) | +- TransactionPropagationContextImporter | +- TransactionManager (class: org.jboss.tm.TxManager) | I looked at that code as well, it's obviously within that, the line of logging output points in that direction too: | TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Begin loadConfig, loginConfigURL=file:/home | /java/jboss-4.0.2/server/default/conf/login-config.xml | but I also did a few experiments trying to get setup other application-policies, using JBoss examples and I couldn't get them to work in the 'default' server. The only application-policies that JBoss will read for me are from the example app which sets up a complete new directory in the server dir. Confusing. Basically though my guess is that a big nasty exception is getting swallowed up without any log output, and that's where the answer will be. I'm pretty snowed under this weekend but I'll try to get onto it ASAP. Obviously if you do first, make sure you report back! Good luck (and for me!) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888737#3888737 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3888737 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
