On some occasions it may be necessary to debug the problems of your annotator by retrieving UIMA log messages of a finer level.
在某些情况下，有必要从更细的级别获取UIMA日志消息来调试注释器的问题。
PMRs require a description of the problem, the level of severity of the problem, and often also the relevant log files to help IBM Support understand your environment and debug the problem.
pMR要求提供问题的描述、问题的严重性级别，通常还要提供相关的日志文件来帮助IBMSupport了解您的环境和对问题进行调试。
The debug log level generates extensive information, whicl the fatal level records only fatal exceptions.
debug日志记录级别生成最丰富的信息，而fatal 级别只记录严重的异常。
You can turn on package org.hibernate.SQL's log level to DEBUG in log4j to see all the SQL generated.
你可以在log4j中将or g . hibernate . SQL包的日志级别设为DEBUG，这样便能看到生成的所有SQL。
You can call methods on the log object that correspond to the desired log level: debug, info, error, and so on. (See Resources for more information on logging.)
可以调用log对象上与想要的日志级别相对应的方法，这些日志级别包括：debug、info和error等(参见参考资料了解关于日志记录的更多信息)。
You can call methods on the log object that correspond to the desired log level: debug, info, error, and so on. (See Resources for more information on logging.)
可以调用log对象上与想要的日志级别相对应的方法，这些日志级别包括：debug、info和error等(参见参考资料了解关于日志记录的更多信息)。
应用推荐