Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 4.0
    • Fix Version/s: future release
    • Component/s: security
    • Labels:
      None
    • Environment:

      WinXP, GF 3.2 latest workspace

      Description

      Below java file contains hard-coded log messages:

      http://wikis.sun.com/display/glassfish/GlassFishV3LoggingMessageFormat

      security\webintegration\src\main\java\com\sun\web\security\RealmAdapter.java

      There are multiple messages hard-coded instead of using LogStrings.properties file for localization.

      One particularly that stands out is the following, as it is logged during QL.

      [#|2011-06-15T11:19:32.217+1000|WARNING|glassfish3.2|javax.enterprise.system.container.web.com.sun.web.security|_ThreadID=30;_ThreadName=Thread-1;|Exception
      com.sun.enterprise.security.auth.login.common.LoginException: Login failed: Failed file login for j2ee.
      at com.sun.enterprise.security.auth.login.LoginContextDriver.doPasswordLogin(LoginContextDriver.java:394)

      As a proper message is logged just before it, the stacktrace can simply be logged without a message:

      _logger.log(Level.WARNING,"web.login.failed", le.toString());
      _logger.log(Level.WARNING, null , le);

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            JeffTancill
            Reporter:
            Dies Koper
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: