Message log entry: Description

This section describes message log entries. The information is the same whether the messages are logged to a file or displayed on a console, whether the messages are the result of a tracing event or a severe error event. The messages are logged as plain text, and can be viewed with any text editor or browser utility.

There are several run-time properties that control message logging. See "Run-time properties for CORBA clients and servers" for a complete list of these properties. In particular, the com.ibm.CORBA.logger.fileDetail and com.ibm.CORBA.logger.consoleDetail properties control the amount of detail provided in message log entries (that is, brief or detailed). Detailed messages contain all of the information known about the message, some of which would be useful only to IBM support personnel. Brief messages contain only the timestamp and the message text.

Example of detailed message log entry

The following is an example of a detailed message log entry:

ComponentId:  393316
ProcessId:    981
ThreadId:     857
FunctionName: e:/l0203/src/eborb/lib/or/callstrm/callsiop.cpp
ProbeId:      4180
SourceId:     @(#) 1.22 src/eborb/lib/or/misc/wasderr.cpp,
              eborb, ebroker,
              l0203.02 1/22/02 09:32:01 [1/22/02 17:40:58]
Manufacturer: IBM Corporation
Product:      WebSphere Application Server
Version:      5.0
ProcessType:  daemon
ProcessAlias: WASDAEMON
HostName:     gaston
TimeStamp:    2002-01-25 12:54:26.61339573
Severity:     1
Message Text: A SystemException occurred: INITIALIZE, minor code 0x49420036 (SOMDERROR_SOMDDAlreadyRunning)
at e:/l0203/src/eborb/lib/or/callstrm/callsiop.cpp line 4180.
Cannot open the Location Service Daemon's listening port at address gaston:2809.
The Location Service Daemon may already be running.

Example of a brief message log entry

The following is an example of a brief message log entry:

TimeStamp:      2002-01-25 12:58:17.188243117
A SystemException occurred: INITIALIZE, minor code 0x49420036 (SOMDERROR_SOMDDAlreadyRunning)
at e:/l0203/src/eborb/lib/or/callstrm/callsiop.cpp line 4180.
Cannot open the Location Service Daemon's listening port at address gaston:2809.
The Location Service Daemon may already be running.

Location of the message log file

By default, messages are logged in the file $WASORBTOP/service/activity.txt, where WASORBTOP is an environment variable which specifies the top level installation directory of the ORB. Note that alternate names for both the directory and filename can be specified by setting the com.ibm.CORBA.logger.directoryName and com.ibm.CORBA.logger.logFileName ORB run-time properties. For more information on this, see "Run-time properties for CORBA clients and servers".

Note: Many different processes may be logging messages to the same message log file. Each message entry includes the process id and thread id associated with the program that logged the message.

Message log file rollover

It is possible that the message log file could grow to an undesirable size. This might be caused by a program logging a large number of messages or by many programs logging messages to the same file over a long period of time.

To help manage the size of this file, an automatic rollover capability is provided by the logger.

Note: This capability applies only to the message log file. It is not provided for trace log files.

Before a message is actually logged to the message log file, a check is made to determine if the current log file size is larger than the currently configured maximum size. The ORB run-time property com.ibm.CORBA.logger.maxLogFileSize is used to specify this maximum size, in kilobytes. The default value is 1024 KB, or 1 MB. If you set this property to 0 (zero), you effectively disable the automatic rollover capability.

If the message log file is larger than the maximum size, then:

Communications trace log entries

The com.ibm.CORBA.orbCommunicationsTraceLevel run-time property controls the tracing of GIOP messages sent or received by the ORB. The ORB supports four levels of tracing: none, basic, intermediate and advanced. The following sections provide examples of the basic, intermediate, and advanced trace levels.

Example of basic communications trace log entry

The following is an example of a brief trace log entry with the com.ibm.CORBA.orbCommunicationsTraceLevel property set to basic:

TimeStamp:    2002-01-28 15:06:31.398705663
File/function e:/l0203/src/eborb/lib/or/trans/transip.cpp:1466 
              has logged trace data:

0000  47 49 4F 50 01 02 01 00 - 7C 00 00 00 01 00 00 00  GIOP....|.......
0010  03 00 00 00 00 00 00 00 - 43 00 00 00 4A 4D 42 49  ........C...JMBI
0020  00 00 00 13 00 00 00 00 - 0A C3 63 C2 BD 40 1C 55  .........c.@.U
0030  E0 00 02 E2 09 35 5C A0 - 00 00 00 24 00 00 00 1F  ....5\ ...$....
0040  41 52 53 55 00 10 00 0F - 00 0C 00 04 65 42 6F 61  ARSU........eBoa
0050  00 04 01 54 FA 12 00 12 - 00 00 00 52 03 00 00 00  ...T.......R....
0060  0F 00 00 00 67 65 74 50 - 72 69 6E 74 65 72 4C 69  ....getPrinterLi
0070  73 74 00 00 01 00 00 00 - 1C 4D 42 49 08 00 00 00  st.......MBI....
0080  01 00 00 00 00 00 45 FF                            ......E.

The basic trace level provides a hexadecimal dump of the contents of the GIOP message.

Example of intermediate communications trace log entry

The following is an example of a brief trace log entry with the com.ibm.CORBA.orbCommunicationsTraceLevel property set to intermediate:

TimeStamp:    2002-01-28 15:05:00.960148555
File/function e:/l0203/src/eborb/lib/or/trans/transip.cpp:1466 
              has logged trace data:

0000  47 49 4F 50 01 02 01 00 - 7C 00 00 00 01 00 00 00  GIOP....|.......
0010  03 00 00 00 00 00 00 00 - 43 00 00 00 4A 4D 42 49  ........C...JMBI
0020  00 00 00 13 00 00 00 00 - 22 8F 8B B9 BC E5 1C 55  ...............U
0030  E0 00 02 FA 09 35 5C A0 - 00 00 00 24 00 00 00 1F  .....5\ ...$....
0040  41 52 53 55 00 10 00 0F - 00 0C 00 04 65 42 6F 61  ARSU........eBoa
0050  00 04 01 54 FA 12 00 30 - 00 00 00 18 01 00 00 00  ...T...0........
0060  0F 00 00 00 67 65 74 50 - 72 69 6E 74 65 72 4C 69  ....getPrinterLi
0070  73 74 00 00 01 00 00 00 - 1C 4D 42 49 08 00 00 00  st.......MBI....
0080  01 00 00 00 00 00 45 FF                            ......E.

***** GIOP Message *****
GIOP Version:      1.2
Byte Order:        LittleEndian (Intel)
More Fragments:    No
Message Length:    124 (0x0000007C)
Message Type:      REQUEST
Request ID:        1 (0x00000001)
Response flags:    0x00000003 (reply msg required=Yes, twoway request=Yes)
Method name:       getPrinterList

The intermediate trace level adds formatting of the various headers within the GIOP message for easier readability.

Example of advanced communications trace log entry

The following is an example of a detailed trace log entry with the com.ibm.CORBA.orbCommunicationsTraceLevel property set to advanced:


ComponentId:  393316
ProcessId:    364
ThreadId:     748
FunctionName: e:/l0203/src/eborb/lib/or/trans/transip.cpp
ProbeId:      1466
SourceId:     @(#) 1.12 src/eborb/lib/or/trans/transip.cpp, eborb, 
              ebroker, k0149.03 10/23/01 11:02:49 [1/4/02 09:13:55]
Manufacturer: IBM Corporation
Product:      WebSphere Application Server
Version:      5.0
ProcessType:  client
ProcessAlias: DefaultClient
HostName:     gaston
TimeStamp:    2002-01-28 15:09:43.357868559
Severity:     3
Message Text:
File/function e:/l0203/src/eborb/lib/or/trans/transip.cpp:1466 
              has logged trace data:

0000  47 49 4F 50 01 02 01 00 - 7C 00 00 00 01 00 00 00  GIOP....|.......
0010  03 00 00 00 00 00 00 00 - 43 00 00 00 4A 4D 42 49  ........C...JMBI
0020  00 00 00 13 00 00 00 00 - 0C 4B E9 C5 BE 00 1C 55  .........K.....U
0030  E0 00 02 FF 09 35 5C A0 - 00 00 00 24 00 00 00 1F  .....5\ ...$....
0040  41 52 53 55 00 10 00 0F - 00 0C 00 04 65 42 6F 61  ARSU........eBoa
0050  00 04 01 54 FA 12 00 1E - 00 00 00 12 03 00 00 00  ...T............
0060  0F 00 00 00 67 65 74 50 - 72 69 6E 74 65 72 4C 69  ....getPrinterLi
0070  73 74 00 00 01 00 00 00 - 1C 4D 42 49 08 00 00 00  st.......MBI....
0080  01 00 00 00 00 00 45 FF                            ......E.

***** GIOP Message *****
GIOP Version:      1.2
Byte Order:        LittleEndian (Intel)
More Fragments:    No
Message Length:    124 (0x0000007C)
Message Type:      REQUEST
Request ID:        1 (0x00000001)
Response flags:    0x00000003 (reply msg required=Yes, twoway request=Yes)
Method name:       getPrinterList

Target Address begins at offset: 20 (0x00000014)

Service context list:
   [0]  id = 0x49424D1C [IOP::CPPOrbLevelContext], 
        length = 8 (0x00000008), data offset = 127 (0x0000007F)
        Base ORB Major Version: 0x0000FF45
        Base ORB Minor Version: 0x00000000
        Extended ORB Version:   0x00000000

Parameters begin at offset: 136 (0x00000088)

The advanced trace level adds more detailed formatting of the contents of the GIOP message, such as formatting of object references, service contexts, tagged profiles and tagged components.

Location of trace log files

By default, trace messages are written to a file whose name is of the form $WASORBTOP/service/process_alias/trace_file_name, where:


Related tasks
Reading a message log
Related reference
Run-time properties for CORBA clients and servers



Searchable topic ID:   rcor_actlog
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/corba/ref/rcor_actlog.html

Library | Support | Terms of Use | Feedback