[
https://jira.jboss.org/jira/browse/JBPORTAL-2323?page=com.atlassian.jira....
]
luke biddell commented on JBPORTAL-2323:
----------------------------------------
This issue cost me a fair bit of time, in the end it was obviously my fault but the
logging issue most certainly didn't help.
Don't think it's anything to do with JBossPortal though, this is part of the base
AS.
ClassNotFoundException for missing custom login module is logged at
TRACE level
-------------------------------------------------------------------------------
Key: JBPORTAL-2323
URL:
https://jira.jboss.org/jira/browse/JBPORTAL-2323
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Affects Versions: 2.7.1 Final
Environment: Java 1.6.0_10, Linux (CentOS)
Reporter: Stephen Houston
See -
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=150756 for
discussion of the issue.
In summary, replace the line
<login-module code="org.jboss.portal.identity.auth.IdentityLoginModule"
flag="required">
in jboss-portal-ha.sar/conf/login-config.xml
with
<login-module code="org.foo.MissingModule" flag="required">
start the portal and attempt to log in. You will see no error message to the effect that
there is a missing class, nor will the user see anything on the front end to indicate that
an error occurred. The actual ClassNotFoundException is logged at TRACE level. Given the
severity of the exception I would have expected this at ERROR level.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira