glassfish
  1. glassfish
  2. GLASSFISH-4202

"WARNING: Visiting non-standard Signature object"

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 9.1peur1
    • Fix Version/s: None
    • Component/s: verifier
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      4,202
    • Status Whiteboard:
      Hide

      v3_exclude,V2.1.1exclude

      Show
      v3_exclude,V2.1.1exclude

      Description

      It happens quite often that I see the following WARNING in GlassFish's log after
      doing some deploy-undeploy cycles. To be it looks like the admin gui is
      procuding that warnings. It is a bit scary that GlassFish stumbles over it's own
      behaviour. Users will think they did something wrong, while actually they did
      nothing wrong.

        Activity

        Hide
        Anissa Lam added a comment -

        Please attach server.log or copy & paste the warning here. There is no way for
        us to work on this issue without even knowing what warning you are getting.

        Show
        Anissa Lam added a comment - Please attach server.log or copy & paste the warning here. There is no way for us to work on this issue without even knowing what warning you are getting.
        Hide
        mkarg added a comment -

        Created an attachment (id=1338)
        GlassFish server.log containing several "Visiting non-standard Signature object" WARNINGs

        Show
        mkarg added a comment - Created an attachment (id=1338) GlassFish server.log containing several "Visiting non-standard Signature object" WARNINGs
        Hide
        Anissa Lam added a comment -

        Thanks for providing the warning message.
        I believe this is warning from the verifier. Reassign the bug to 'verifier' for
        further investigation.

        Show
        Anissa Lam added a comment - Thanks for providing the warning message. I believe this is warning from the verifier. Reassign the bug to 'verifier' for further investigation.
        Hide
        harpreet added a comment -

        Not critical to v2.1 - marking issue for next release

        Show
        harpreet added a comment - Not critical to v2.1 - marking issue for next release
        Hide
        sanandal added a comment -

        "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
        release whose primary release driver is SailFin.
        This issue will be scrubbed after this release and will be given the right
        priority for the next release."

        Show
        sanandal added a comment - "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
        Hide
        mkarg added a comment -

        Increased priority to P3 according to
        https://glassfish.dev.java.net/public/IssueTrackerPriority.html as this bug is
        neither invisible nor internal. The administrator will see a bug and try to fix
        it, what results in costs for the customer. This is not acceptable from an
        economic view.

        Show
        mkarg added a comment - Increased priority to P3 according to https://glassfish.dev.java.net/public/IssueTrackerPriority.html as this bug is neither invisible nor internal. The administrator will see a bug and try to fix it, what results in costs for the customer. This is not acceptable from an economic view.
        Hide
        Sanjeeb Sahoo added a comment -

        v3_exclude

        Show
        Sanjeeb Sahoo added a comment - v3_exclude
        Hide
        Sanjeeb Sahoo added a comment -

        The actual warning comes from BCEL which verifier uses. Since BCEL is bundled
        with JDK, we have to wait for JDK to bundle newer version of BCEL. Until then,
        we have to live with this message. Hence, v3_exclude.

        Show
        Sanjeeb Sahoo added a comment - The actual warning comes from BCEL which verifier uses. Since BCEL is bundled with JDK, we have to wait for JDK to bundle newer version of BCEL. Until then, we have to live with this message. Hence, v3_exclude.
        Hide
        jagadesh added a comment -

        Will not be fixed for V2.1.1

        Show
        jagadesh added a comment - Will not be fixed for V2.1.1
        Hide
        edrandall added a comment -

        Just upgraded to 3.1.2 and this issue is still present.

        The verifier outputs the message 107,130 times during the verification of our .ear file, with no clue as to what object is actually non-standard.

        Will it ever be fixed?

        Show
        edrandall added a comment - Just upgraded to 3.1.2 and this issue is still present. The verifier outputs the message 107,130 times during the verification of our .ear file, with no clue as to what object is actually non-standard. Will it ever be fixed?

          People

          • Assignee:
            Sanjeeb Sahoo
            Reporter:
            mkarg
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: