Execution Service Logs

Execution Service Logs are server-side diagnostic logs generated by the NCache Execution Service. These logs help diagnose Execution Service activity related to background tasks such as Cache Startup Loader and Cache Refresher.

Use Execution Service Logs when the issue involves Cache Startup Loader activity, dataset refresh, or loader/refresher execution. For cache runtime behavior, cluster membership, state transfer, replication, or cache operation errors, use Cache Server Logs. For NCache Service startup, shutdown, or service-level messages, use Service Logs.

Execution Service Log Generation and Location

Execution Service logs are generated when the NCache Execution Service records service-level or task-level activity. These entries may be written when the Execution Service starts, when Cache Startup Loader activity begins, when Cache Refresher runs, or when a loader/refresher operation raises an error. If no Execution Service activity or loader/refresher activity occurs, no new diagnostic entries may be written.

To generate loader or refresher-related diagnostic entries, the relevant Cache Startup Loader and Refresher must be configured, and the Execution Service must be running. By default, NCache writes Execution Service logs under the NCache log directory:

Windows: %NCHOME%\log-files\ExecutionService
Linux: /opt/ncache/log-files/ExecutionService

Execution Service log file names can include the ExecutionService prefix, a timestamp, and the server IP address. For example:

ExecutionService.04-06-26_12-16-03_20.200.20.40.txt

In clustered caches, review Execution Service logs from the affected server nodes for the same time window, especially when loader or refresher behavior differs across nodes.

Execution Service Log Contents

Execution Service logs can help confirm whether the Execution Service was active and whether loader/refresher-related activity was recorded. Depending on the recorded activity, these logs may include Execution Service startup messages, loader task messages, refresher task messages, dataset refresh messages, or errors related to loader/refresher execution.

Execution Service log entries are written in a tabular text format. An entry can include the timestamp, application domain, logger name, thread name or thread ID, log level, and message. For example:

TIMESTAMP                   APPDOMAIN                          LOGGERNAME         THREADNAME   LEVEL   MESSAGE
2026-06-11 11:14:40,946     Alachisoft.NCache.ExecutionService ExecutionService   8            INFO    ExecutionService.StartLoader()          Execution service started successfully using IP info 127.0.0.1:9850
2026-06-11 12:02:05,581     Alachisoft.NCache.ExecutionService ExecutionService   8            INFO    LoaderServer.StartLoader()              Cache startup loader is started for cache name [demoCache] with dataset: products
2026-06-11 12:02:06,608     Alachisoft.NCache.ExecutionService ExecutionService   8            INFO    LoaderServer.StopLoader()               Cache startup loader stopped for cache name [demoCache] with dataset: products

The MESSAGE field contains the Execution Service message or error detail. Use the timestamp to compare the entry with the time when the cache was started, the loader was expected to run, or the dataset refresh was expected to occur.

See Also

Cache Startup Loader and Refresher
Configure Cache Startup Loader
Cache Server Logs
Service Logs
Management Center Logs