These properties configure the output from a logging profile that uses the JDK java.util.logging package as its logging system. All properties in the logging profile are applied to the Log4j configuration. Only those properties used in the preconfigured JDK log profiles are documented here. For information on other properties, see the Java Logging package documentation
Log profile properties, com.sybase.jaguar.logprofile.subsystem
Specifies the log level for the root logger.
Same as for <logger>.level.
Defines the logging level for logger named <logger>.
The logger names used internally in EAServer are the same as for
Log4j, specified in Table B-8.
One of the levels listed in Table B-14, as defined in java.util.logging.Level. Levels are listed in order of ascending severity. Only messages with severity greater than the specified level are logged.
Level |
To indicate |
|---|---|
ALL |
All messages are logged. |
FINE |
Debug messages are logged. |
FINER |
Same effect as FINE. |
FINEST |
Same effect as FINE. |
CONFIG |
A configuration error has been detected. You should correct the problem. |
INFO |
Warning and informational messages are logged. Informational messages include status information, such as the name server has finished binding components. An example warning would be that the server is in a cluster and other members are not found. |
WARNING |
An error has occurred that prevents completion of a requested action. For example, a component has thrown an uncaught exception and its transaction is being rolled back. |
SEVERE |
An error has occurred that indicates the server should terminate. |
OFF |
No messages are logged. |
Loggers allow you to associate logical names with categories
of messages. For example, com.sybase.jaguar.servlet is
the logger name for messages from the EAServer servlet engine. Table B-8 lists
the logger names used internally by EAServer. Loggers use a name-based
hierarchy, similar to the Java package naming convention, and inherit
settings from their parent. For example, a logger named com.sybase.jaguar.servlet inherits the
settings for com.sybase, unless
you explicitly configure com.sybase.jaguar.
If a logger is not configured explicitly, it inherits the root logger
setting configured by the .level property.
The same names are used for Log4j logger names, EAS log subsystem categories, and java.util.logging logger names.
.level, java.util.logging.ConsoleHandler.level, java.util.logging.FileHandler.level
Specifies handlers for the log output.
A comma-separated list of classes that implement java.util.logging.Handler. For example:
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.formatter, java.util.logging.ConsoleHandler.level, java.util.logging.FileHandler.formatter, java.util.logging.FileHandler.level, java.util.logging.FileHandler.pattern
If using handler java.util.logging.ConsoleHandler, the formatter class to be used.
The handler class name. The class must implement java.util.logging.Formatter.
If using handler java.util.logging.ConsoleHandler, the log level for file output to be logged.
Same as <logger>.level. The most restrictive of the <logger>.level and the console handler setting is used.
If using handler java.util.logging.FileHandler, the formatter class to be used.
The handler class name. The class must implement java.util.logging.Formatter.
If using handler java.util.logging.FileHandler, the log level for file output to be logged.
Same as <logger>.level. The most restrictive of the <logger>.level and the file handler setting is used. For example, if the logger level is INFO, and the file handler setting is WARNING, only WARNING messages are logged by the file handler. If the logger level is INFO, and the file handler setting is ALL, the effective level is WARNING.
The pattern (template) for the output file name.
See the FileHandler API documentation.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
