Kbase P96551: What are the possible values for the -logentrytypes startup parameter in OpenEdge 10
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/12/2011 |
|
Status: Verified
GOAL:
What is the LOG-ENTRY-TYPES attribute?
GOAL:
What are the possible values for the LOG-ENTRY-TYPES attribute?
GOAL:
What are the possible values for the -logentrytypes parameter?
GOAL:
What information is going to be written in the client log file?
GOAL:
What logging levels apply to each log entry type?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
FIX:
The LOG-ENTRY-TYPES attribute applies to the LOG-MANAGER system handle, it is a comma-separated list of one or more types of log entries to write to the log file.
Use the LOG-ENTRY-TYPES attribute to specify one or more types of log entries to write to the log file specified by the LOGFILE-NAME attribute or the Client Logging (-clientlog) startup parameter.
The LOG-ENTRY-TYPES attribute corresponds to the Log Entry Types (-logentrytypes) startup parameter.
The following are some of the values for the LOG-ENTRY-TYPES attributes. For a complete listing, reference the OpenEdge Development: Debugging and Troubleshooting - Section dealing with Log Entry Types.
4GLMessages:
Progress writes all 4GL VIEW-AS ALERT-BOX messages to the log file, together with the 4GL stack, when you turn on Debug Alert using either the Debug Alert (-debugalert) startup parameter or the DEBUG-ALERT attribute on the SESSION system handle.
Logging level: Level 2 (Basic) and higher
4GLTrace:
Turns on logging of the execution of the following 4GL statements: RUN, PUBLISH, FUNCTIONS, and SUBSCRIBE, and then user-defined functions.
Logging level: Entry messages are logged at level 2 (Basic) and higher. Return messages are logged at level 3 (Verbose) and higher. Information specific to DataServers is logged at Level 4 (Extended).
4GLTrans:
Turns on logging for the processing of transactions and subtransactions in ABL procedures.
Logging Level: Level 2 (Basic) logs messages when a transaction begins or ends, or when a transaction is undone. Level 3 (Verbose) logs messages when a transaction or subtransaction begins or ends, or when a transaction or subtransaction is undone.
AiaMgmt:
Logs messages about regular AIA operations, such as AIA version information, instantiation, some other informational messages, and information on the AIA connection pool.
Logging level: Level 2 (Basic) logs instantiation and informational messages. Levels 3 (Verbose) and 4 (Extended) log connection pool information.
AiaProp:
Logs the properties set for the specific AIA instance in the ubroker.properties file.
Logging level: Level 2 (Basic) and higher.
AiaRqst:
Logs information on the GET and POST commands sent by the client and the response back to the client.
Logging level: Level 2 (Basic) and higher.
AiaUbroker:
Logs information on the communication between the AIA and the Unified Broker.
Logging level: Level 2 (Basic) logs most information. Level 3 (Verbose) also logs a binary dump of messages exchanged between the client and the broker/server process.
AiaDefault:
Combines AiaMgmt and AiaProp.
Logging level: Level 2 (Basic) logs most information. Levels 3 (Verbose) and 4 (Extended) log connection pool information.
DB.Connects:
Turns on logging of database connections and disconnections. The log messages include database name and user ID number.
Logging level: Level 2 (Basic) and higher.
DS.QryInfo
DS.Cursor
Turns on logging for the DataServer client context.
Logging level: Level 2 (Basic) or higher.
DynObjects.DB
DynObjects.XML
DynObj.ects.Other
DynObjects.UI:
Turns on logging for the creation and deletion of dynamic objects. For a list of dynamic objects within each category and a description of the log entries, see OpenEdge Development: Debugging and Troubleshooting.
Logging level: Level 2 (Basic) logs most information. Level 3 (Verbose) also logs pool information.
FileID:
Turns on logging for file opening, file closing, and error messages that do not contain the file number.
Logging level: Level 2 (Basic) and higher.
IgnoredOps:
Turns on logging of the names and code locations of all window attributes or methods that the AVM ignores on embedded ABL windows.
Logging level: 2 (Basic).
MsgrTrace:
Turns on logging for WebSpeed Messengers.
Logging level: Level 2 (Basic) and higher. For the specific information logged at each level for CGIIP and other Messengers, see OpenEdge Development: Debugging and Troubleshooting.
NSPlumbing:
Turns on logging for the NameServer component.
Logging level: Level 2 (Basic) logs NameServer starts and stops, load balancing status and messages on registering and unregistering brokers. Level 3 (Verbose) also logs request from clients and status information on the communication between client and NameServer and between NameServer and brokers. Level 4 (Extended) also logs debugging messages on broker unregistering.
ProEvents.UI.Char
ProEvents.UI.Command
ProEvents.Other:
Turns on logging for different categories of events. For a list of events within each category and a description of the log entries, see OpenEdge Development: Debugging and Troubleshooting .
Logging level: Level 2 (Basic) logs most information, including a subset of WM GUI events. Level 3 (Verbose) also logs the remaining WM GUI events.
QryInfo:
Turns on logging for query resolution statistics.
Logging level: Level 2 (Basic) logs information about individual queries. Level 3 (Verbose) logs information about all queries.
SAX:
Turns on logging for the SAX parser.
Logging level: Level 2 (Basic)
UBroker.Basic
UBroker.ThreadPool
UBroker.AutoTrim:
Turns on logging for the Unified Broker. For other UBroker.* log entry types that might be requested by Progress Customer Support, see OpenEdge Development: Debugging and Troubleshooting.
Logging level: Level 2 (Basic) logs most information. For UBroker.Basic, Level 3 (Verbose) logs all remaining property values in ubroker.properties for a given broker, and more information on the connection from clients.
.WSADefault:
Provides server related messages for a single Web Service Adapter.
Logging level: Level 2 (Basic) logs processing requests and very severe errors, and is best for a production environment. Level 3 (Verbose) logs general access problems, startup property values, user authorization errors, request IDs, HTTP error responses, and WSDL retrieval errors, and is best for a development environment. Level 4 (Extended) logs HTTP and SOAP requests and responses, and is best for debugging..