Why are class names in log entries one character long? - Progress Community

Loading

Skip to Main Content

Why are class names in log entries one character long?

Why are the class names in PAS for OpenEdge logging entries one character long. Can logging in PAS for OpenEdge be configured so that the class names are displayed in full?

Nov 9, 2016
Knowledge

Title

Why are class names in log entries one character long?

URL Name

why-are-class-names-in-log-entries-one-character-long

Article Number

000175834

Environment

Product: OpenEdge Version: 11.6.x OS: Windows Other: PAS for OpenEndge

Question/Problem Description

The log entries in a PAS for OpenEdge log look something like the following:

16:32:20.995/137651 [catalina-exec-6] DEBUG c.p.c.c.j.i.baseClass1 - Found operation: LogClass..GetVerb
16:32:21.774/138430 [catalina-exec-6] DEBUG c.p.appserv.endpoints.oe.Endpoint - AppServer Endpoint connected: null
16:32:21.774/138430 [catalina-exec-6] DEBUG c.p.appserv.endpoints.oe.Endpoint - Creating singleton class LogClass
16:32:21.778/138434 [catalina-exec-6] DEBUG c.p.appserv.endpoints.oe.Endpoint - Running internal procedure: LogClass.GetVerb

The single letter package and class names make it difficult to track back to a particular method.

Steps to Reproduce

Clarifying Information

The default pattern entity looks something like the following:
<pattern>%d{HH:mm:ss.SSS}/%r [%thread] %-5level %logger{36} - %msg%n</pattern>

Error Message

Defect Number

Enhancement Number

Cause

This is expected behavior.

The default %logger attribute of the pattern entity in logging.xml is set relatively small. When set to a small integer, the class names and package name are abbreviated to save space in the log file.

Resolution

Edit <Project>\PASOEContent\WEB-INF\logging.xml and change the %logger attribute of the pattern entity to a size more suitable to the needs of the application.

Notice that the %logger size is set to 36. Modify the 36 to something larger. For example, increase the size to 100 as follows:
<pattern>%d{HH:mm:ss.SSS}/%r [%thread] %-5level %logger{100} - %msg%n</pattern>

The actual size to which %logger should be set is up to the needs of the individual application. It may take some experimentation to find a size that is adequate for an individual application.

The {###} value of the %logger attribute can also be left out completely. This causes the entire class list to be included in the logging entry, completely unrestricted. If the completeness of the class list is of greater importance than the length of the logging entry, then this might be a better option. The entry in logging.xml might look like the following:

<pattern>%d{HH:mm:ss.SSS}/%r [%thread] %-5level %logger - %msg%n</pattern>

Notice that %logger is included but the {###} is excluded.

Workaround

Notes

References to other Documentation:

http://logback.qos.ch/manual/layouts.html#conversionWord

Keyword Phrase

Last Modified Date

11/9/2016 1:14 PM

OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Why are class names in log entries one character long? - Progress Community