Tracker issue for JGroups portion of EAP62_2010 Logging Unification. ANDIAMO-7 compliance.
https://github.com/belaban/JGroups/pull/101 This PR updates the message formats used in JGroups to match those used in EAP. Will require JGroups 3.2.11.Final release. N.B. EAP already configures JGroups with a custom Log implemented by JBoss Logging, so the resulting log messages will have a consistent format.
PR for component upgrade: https://github.com/jbossas/jboss-eap/pull/346
Created attachment 799394 [details] JGroups serious logs without id - JGroups-3.2.12.Final
Per ANDIAMO-7 every serious log message (warn, error, fatal) should have a unique code that can be used to identify it. But I found 525 serious log messages without id: see attachment 799394 [details]
Many of these log messages are used in tests or demos. Many are also assertions - and are not triggered at runtime.
JGroups JIRA: https://issues.jboss.org/browse/JGRP-1709
Most of the ERROR and WARN messages in the attached log are from - classes that are not officially supported (STOMP, PRIO) - classes that are not used anymore (e.g. NAKACK, NakReceiverWindow, Retransmitter, DefaultRetransmitter, RangeBasedRetransmitter etc) - test code (StateTransferTest) - demos (Whiteboard, GraphPanel, Draw, QuoteServer) What would be much more useful is to have a list of ERROR and WARN messages that are actually logged running the testsuite and from support cases in production. These could then successively be converted to use unique message IDs.
Unfortunately we don't have such a list and getting this would take great effort. All we can do is to update our tests to ignore test classes, demos and all classes you mentioned.
The remaining log messages will have to be addressed in a future release.
Rescheduling this for EAP7. According to Bela, this won't be fully addressed until JGroups 3.5 or so.