Description of problem: When portal is configured to use JTA transactions (https://docs.jboss.org/author/display/GTNPORTAL38/JTA+integration) there is exception in logs (with INFO severity). It seems portal works fine, only stacktrace is shown. It is shown when user is logged in for the first time into the portal (or if the session is started again). The user is added into portal by our tool (it adds users directly by editting ${gatein.home}/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/organization-configuration.xml). With user added using UI the exceprion isn't present. But e.g. if you try to sign in with blank username and password exception occurs. Steps to Reproduce: 1. set portal using JTA and start it 2. click Sign In 3. leave blank input fields and click Sign In button or use config-tool to add demo users and try to log in as john (mary, demo). There is link to job where the config tool is used to add demo users: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/EPP/view/6.2/view/UI%20Database%20Support/job/epp6_ui_selenium_tests_db_mysql55/116/ in the log of the build you can see the exceptions.
Doesn't require release notes as issue is in FilterDisabledLoginModule, which is new stuff in JPP 6.2 .
https://github.com/gatein/gatein-portal/pull/892 was merged in upstream.
Verified in ER05.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.