[
https://jira.jboss.org/jira/browse/TEIID-509?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-509:
--------------------------------------
We should use the CONFIG level for this purpose (same as jdk and log4j logging). CONFIG
is actually treated as less than info, so it will still be up to the log configuration to
determine if the logs should be made. It would also be good to reintroduce the process
info log into the server at the config level.
Add new logging level so that server startup information can be
logged and be differentiated from critical/warning level entries
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-509
URL:
https://jira.jboss.org/jira/browse/TEIID-509
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 6.1.0
Reporter: Van Halbert
Priority: Minor
Fix For: 6.2.0
Currently, at server startup, nothing is being written to the hostcontroller or vmprocess
logs. The previous server started information is no longer being written because of the
log level wasn't being differentiated from actual critical/warning messages.
Therefore, a new level should be created so that the minimal server startup information
can continue to be written to the logs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira