glassfish
  1. glassfish
  2. GLASSFISH-13728

Can not find resource bundle for this logger.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1_dev
    • Component/s: security
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Macintosh

      Description

      The following information shows up in the server log after an upgrade of a
      v2.1.1 developer domain with an app deployed:

      [#|2010-09-30T15:15:53.484-0400|WARNING|glassfish3.1|javax.enterprise.system.core.security|_ThreadID=24;_ThreadName=Thread-1;|Can
      not find resource bundle for this logger. class name that failed:
      com.sun.enterprise.security.ssl.impl.SecuritySupportImpl|#]

      [#|2010-09-30T15:15:53.474-0400|SEVERE|glassfish3.1|javax.enterprise.system.core.security.com.sun.enterprise.security.ssl.impl|_ThreadID=24;_ThreadName=Thread-1;|java_security.expired_certificate|#]

      [#|2010-09-30T15:15:53.496-0400|WARNING|glassfish3.1|javax.enterprise.system.core.security|_ThreadID=24;_ThreadName=Thread-1;|Can
      not find resource bundle for this logger. class name that failed:
      com.sun.enterprise.security.ssl.impl.SecuritySupportImpl|#]

        Activity

        Hide
        kumarjayanti added a comment -

        setting target

        Show
        kumarjayanti added a comment - setting target
        Hide
        adf59 added a comment -

        Add 3.1-upgrade keyword. It was missing on this bug I submitted.

        Show
        adf59 added a comment - Add 3.1-upgrade keyword. It was missing on this bug I submitted.
        Hide
        Bobby Bissett added a comment -

        I didn't add the keyword before because I thought I saw these warnings in 3.1
        without an upgrade, but now I'm not seeing it. Good catch. In any event, I think
        this message key was copied over from a different module or package (it was used
        in two different places when I looked a couple weeks back). Adding a resource
        bundle for this should be simple, but I agree it's low priority.

        Show
        Bobby Bissett added a comment - I didn't add the keyword before because I thought I saw these warnings in 3.1 without an upgrade, but now I'm not seeing it. Good catch. In any event, I think this message key was copied over from a different module or package (it was used in two different places when I looked a couple weeks back). Adding a resource bundle for this should be simple, but I agree it's low priority.
        Hide
        Nithya Ramakrishnan added a comment -

        The resource bundle error has been fixed.
        The exception message (and not the key) appears in the logs, after this fix.

        Show
        Nithya Ramakrishnan added a comment - The resource bundle error has been fixed. The exception message (and not the key) appears in the logs, after this fix.

          People

          • Assignee:
            kumarjayanti
            Reporter:
            adf59
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: