Details
-
Bug
-
Resolution: Duplicate
-
Major
-
7.0.0.ER4
-
None
Description
Description of problem:
EAP7 use different log ids. There is a mapping file available here that developers created to help users with the transition long ago:
- jboss-eap-6.4.0-src.zip/log-ids.txt
Customers could download this file in EAP6 sources.
If customers have some automatization for recognizing this log IDs, they should change this automatization.
"log-ids.txt" file contains also some old unused IDs, like IDs for "WildFly Messaging Subsystem".
Related functional jira: JBEAP-150
Example of difference
1. ./standalone.sh
EAP7:
...
10:10:11,061 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.0.6.Final-redhat-1) starting
...
EAP6:
...
10:08:04,187 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.4.6.GA (AS 7.5.6.Final-redhat-2) starting
...
Attachments
Issue Links
- duplicates
-
JBEAP-2483 Prefixes for all log messages have changed
- Closed
- relates to
-
LOGTOOL-74 Add ability to generate formatted files of logging id's for documentation purposes
- Resolved
-
JBEAP-2483 Prefixes for all log messages have changed
- Closed