at java.security.AccessController.doPrivileged(Native Method) | at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) | at javax.security.auth.login.LoginContext.login(LoginContext.java:579) | at org.jboss.security.plugins.auth.JaasSecurityManagerBase.defaultLogin(JaasSecurityManagerBase.java:552) | at org.jboss.security.plugins.auth.JaasSecurityManagerBase.authenticate(JaasSecurityManagerBase.java:486) | at org.jboss.security.plugins.auth.JaasSecurityManagerBase.isValid(JaasSecurityManagerBase.java:365) | at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:160) | at org.jboss.security.integration.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:90) | at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubject(BaseConnectionManager2.java:687) | at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:495) | at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941) | at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89) | at ifs.fnd.sf.j2ee.FndJ2eeConnectionManager.getConnection(FndJ2eeConnectionManager.java:77) Sorry, i did not pay much attention to the log and the ds.xml file earlier. Looks like the issue is in the -ds.xml configuration. Remove this from the -ds.xml: <application-managed-security>true</application-managed-security> | datasource.getConnection(user,password) Remove that and see how it goes. P.S: Off topic - I am still not sure why this leads to a JAAS call. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228648#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...