Error Logging

When running a cache, error messages can be helpful. These messages can be saved to a log file if required.

Enable Logs for .NET

Using NCache Manager

NCache Manager can be used to enable logging.

Go to Options tab of Cluster/Local Cache view window.
Check the Enable error logging checkbox. If you want to enable detailed error logging, check the Enable detailed error logging checkbox. Each time user enables error logging a new trace file is created in %NCHOME%/log-files folder with current time stamp.

Enabling error logging generates FATAL and NORMAL logs, while enabling detailed error logging generates a log file containing INFO, DEBUG and WARNING logs. By default, logging is disabled. Enabling "Detailed Error Logging" generates logs very frequently, which may affect the performance of cache/cluster. In case of an error, it is reported in the application's Event Log in system.

Manually Editing NCache Configuration

Important

Make sure the cache is stopped before making any configuration changes.

Enable/disable logs through config.ncconf by specifying the <logging> tag under the <cache-settings> tag:

 <cache-settings ...>
   <logging enable-logs="True" trace-errors="True" trace-notices="False" trace-warnings="False" trace-debug="False" log-path=""/>
</cache-settings>

For Client Logging, modify the values in client.ncconf of the client node:

<cache id="myreplicatedcache" load-balance="True" enable-client-logs="False" log-level="error">
      <server name="20.200.20.38"/>
</cache>

Once changes are made, start the cache and restart NCache service.

Enable logs for Java Client

Logging in the NCache Java client can be controlled by setting enableNCLogs property before initializing the cache.

System.setProperty("enableNCLogs", Level.INFO.toString());

Log file is generated in the application home directory. The above property will enable logging of all INFO messages. It will also enable logging of SEVERE and WARNING messages.

The Level class (Java.util.logging) defines a set of standard logging levels that can be used to control logging output. The logging Level objects are ordered and are specified by ordered integers. Enabling logging at a given level also enables logging at all higher levels. Clients should use the predefined Level constants such as Level.SEVERE. The levels in descending order are as follows:

SEVERE (highest value)
WARNING
INFO
CONFIG
FINE
FINER
FINEST (lowest value)