glassfish
  1. glassfish
  2. GLASSFISH-20528

duplicate log message ids in deployment/dol and deployment/javaee-full

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0_b88_RC4
    • Fix Version/s: 4.1
    • Component/s: deployment
    • Labels:
      None

      Description

      The AS-DEPLOYMENT prefix is used in both the dol and javaee-full modules. It looks like it should not be used in javaee-full:

      The log annotation processor produces the following output:

      [INFO] Processing jar file:D:\tools\glassfish4\glassfish\modules\dol.jar
      [WARNING] Duplicate message id AS-DEPLOYMENT-00016, this message ID has been used found in another module:\tools\glassfish4\glassfish\modules\deployment-javaee-full.jar
      [WARNING] Duplicate message id AS-DEPLOYMENT-00015, this message ID has been used found in another module:\tools\glassfish4\glassfish\modules\deployment-javaee-full.jar

        Activity

        Hide
        Hong Zhang added a comment -

        I just fixed it earlier today! When I was fixing another issue related to nucleus logger, I noticed duplicated message ids were used in different deployment modules. I have talked with Raj and the recommendation is that we should use same prefix for all appserver deployment modules (AS-DEPLOYMENT), but we should allocate different ranges for different modules to avoid conflict. I have done necessary clean ups accordingly.

        Show
        Hong Zhang added a comment - I just fixed it earlier today! When I was fixing another issue related to nucleus logger, I noticed duplicated message ids were used in different deployment modules. I have talked with Raj and the recommendation is that we should use same prefix for all appserver deployment modules (AS-DEPLOYMENT), but we should allocate different ranges for different modules to avoid conflict. I have done necessary clean ups accordingly.

          People

          • Assignee:
            Hong Zhang
            Reporter:
            Tom Mueller
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: