[teiid-issues] [JBoss JIRA] Updated: (TEIID-509) Add new logging level so that server startup information can be logged and be differentiated from critical/warning level entries

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Mon Apr 20 22:18:22 EDT 2009


     [ https://jira.jboss.org/jira/browse/TEIID-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-509:
---------------------------------

        Fix Version/s: 6.1.1
    Affects Version/s: 6.1.0
             Assignee:     (was: Steven Hawkins)
           Complexity: Low
             Priority: Minor  (was: Major)


> 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.1.1
>
>
> 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

        



More information about the teiid-issues mailing list