Hide Forgot
In previous versions of JBoss EAP 6, when the definition of a POJO was removed from the server's configuration file, references to the POJO were not removed from the `logging.properties` file. If a POJO of the same name was later created again, JBoss EAP would state that there was a duplicate entry in `logging.properties`. This issue has now been resolved and references to POJO objects which no longer remain are removed from the `logging.properties` file.
If I remove a custom Log4J appender from my standalone.xml and restart JBoss, I can still see the POJO definition for the removed appender in my logging.properties file. Reproduce: 1. Start JBoss in standalone mode 2. Log in to web console 3. Profile > core > logging > handlers > custom > add 4. name it whatever 5. class: {{org.apache.log4j.FileAppender}} 6. module: {{org.apache.log4j}} 7. Add a property: {{file -> /path/to/some/log4j.log}} 8. Add the appender to the root logger 9. Restart JBoss 10. Verify the log is populated and {{logging.properties}} has the appender 11. Stop JBoss 12. Edit {{standalone.xml}} and comment out the custom appender and the root logger reference 13. Start JBoss and stop it again after it completed startup 14. Uncomment the appender in {{standalone.xml}} 15. Start JBoss. 16. You should see an error about a duplicate entry in {{logging.properties}}
Could I get a QA review and a qa_ack+ or qa_ack-?
James, you can go on with this.
Verified with EAP 6.3.0.ER8