9.2.4 Activity logsAdded by Whei-Jen Chen on January 3, 2013 | Version 1 (Original)
Activity logs are located under logs directory typically with the name ntsactivity_TIMESTAMP.log
. Activity logs contains all messages and traces that are logged by Lotus Traveler. If the logging level is set to FINEST, then this file can wrap quickly depending on how many users are using the system and the wrapping settings that are being used.
Activity log overview
The following is a sample log entry from the activity file:
[04/20 08:58:38.359] FINE DS-0[DxKhlwAA] CN=testuser1/O=ibm AuthWrapper.validateLogin#221 Attempting to validate userId(CN=testuser1/O=ibm) on device(35638400-5700-9401-1800-0050BF3F5173) userAgent(IBM SyncML Client 184.108.40.206) active sessions(0)
In the the activity file, this entry is a single line. Each log entry made in the server results in at least a single line of text added to the activity file. Each log entry contains fields shown in the following table, separated by at least one space. The example is taken from the entry from above.
|Timestamp:||The local date and time to millisecond precision ||[04/20 08:58:38.359]|
|Level ||SEVERE, WARNING, INFO, FINE, FINER, FINEST||FINE|
|Thread Identifier||The thread name with an optional correlator in brackets [ ]|| DS-0[DxKhlwAA]|
|User Name||The user's ID in canonical name format ||CN=testuser1/O=ibm|
|Source Code ID||The class, method, and line number that originated the message log. |
|Message||The message can be any text.|
Lotus Notes Traveler uses the following thread identifiers. These thread IDs correlate to the thread pool that spawned them and are related to the function that they are performing. Since they are not random, you can tell a lot about what is going on simply by looking at the thread ID.
- main: Main starting point.
- DCAM: Domino Content Adapter Main.
Device Sync, the "n" is the thread id, session is the session id, and msgID is the SyncML message identified (a number). Often there will be an optional correlator specified which is the synchronization session ID.
For example DS-0[DxKhlwAA], means this is device sync thread #0, which is handling synchronization session DxKhlwAA.
Prime Sync, the "n" is the thread id. Similar to device syncs, but this thread is handling the primesync function, there is no device involved here.
Servlet Listener - Interface between the servlet and nts.exe. Takes all incoming requests and passes it to a CLW thread for actual processing.
Servlet Worker - These threads handle the serialized data to/from the servlet.
- Alarm-n: Alarm Callback, the "n' is the is the thread ID.
- TC-n: Tell Commands, the 'n' is the thread id. These threads handle the administration requests of a console user.
- Worker-n: Worker that handles all the request for work by either passing it to some other thread (such as DS) or handling it itself.
- MS-SMS-DelQ :
Message Sender SMS Delay Queue. Queue of messages to be sent via SMS. When messages are dequeued, they get passed to a Message Sender for sending.
Discovery Delay Queue. Queue of heartbeat messages to be sent at the next interval. When messages are dequeued, they get passed to a Message Sender for sending.
- Monitor: Controls the usage of the "New" and "Old" API monitors.
New API Monitor. Utilizes the "new" Domino API for detecting changes to a database. If a change is detected in a database, calls Change Processor for further processing.
Old API Monitor. Utilizes the "old" Domino API for detecting changes to a database. If a change is detected in a database, calls Change Processor for further processing.
Change Processor. For the database that has been detected as changed, kicks off a primesync (on a PS thread) for all devices registered for that database, calculates any changes to the push change flags, and pushes (if change flags have changed) the action message to the device (which should then synchronize on a DS thread).