[GLASSFISH-20528] duplicate log message ids in deployment/dol and deployment/javaee-full Created: 14/May/13  Updated: 20/Dec/16  Resolved: 14/May/13

Status: Resolved
Project: glassfish
Component/s: deployment
Affects Version/s: 4.0_dev
Fix Version/s: 4.1

Type: Bug Priority: Major
Reporter: Tom Mueller Assignee: Hong Zhang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 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



 Comments   
Comment by Hong Zhang [ 14/May/13 ]

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.

Generated at Sat Jan 21 14:19:38 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.