Susitha, I see what your problem is, but it is unclear how to fix it...
The log shows what is configured for the 'portal' security-domain. It uses the DatabaseServerLoginModule. However, the log does not show that a datasource is set for this login module. So what I think is happing is that the login module defaults to 'DefaultDS'. This is why the error says 'DefaultDS' is not bound. Also, I can not see what Datasources have been deployed in the log. So you need to look into two things. First, verify that your datasources are deployed in JBoss server. You can look this up thru jmx-console. Also, verifiy the jndi names they are bound under. Then use jmx-console to verify the configuration of 'portal' security-domain. What is important is that a datasource jndi name be set for the login module and that the name matches the jndi name of deployed datasource. Just as a recommendation, you may want to remove all the duplicat application-policy/application entries in all these login-config files and login-config.xml files you have. In the end, the login-config.xml in portal.sar should be the one that matters. All the rest just make things confusing, and my cause problems. Hope this helps. There is a lot to learn, which is not good if you only have a couple of weeks. cgriffith View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932407#3932407 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932407 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
