CADP for Java Logging
Logs contain information about the events happening inside your application. Logs can be very helpful when trying to troubleshoot a problem. By default, CADP for Java generates a file called CADPLogs.txt (in the installation directory), that stores all the application logs.
Application logs: Capture implementation level details required by developers to understand what happened or how the application responded during a specific event. The application logs are printed in text format. See Format of Application Logs to know more.
Log Level: Specifies the level of logging to be performed by the application. Following table describes the supported log levels with their description.
| Log Level | Description |
|---|---|
| INFO | Records error messages, warnings, and informational messages. |
| WARN | Records error messages and warnings. |
| ERROR | Records only error messages. |
| DEBUG | Records diagnostic information. |
These log levels are configurable and can be changed from CipherTrust Manager.
Note
By default, the CADP for Java logs are rotated on daily basis. You can change the frequency of log rotation using the CipherTrust Manager's API Playground. At present, log rotation can't be modified through the CipherTrust Manager UI.
Format of Application Logs
The log format determines how the contents of a log should be interpreted. Below is the sample of an application log:
06-04-2025 13:17:28.744 [Thread-3] INFO ingrian.security.nae.CipherDoFinalListener - invoke0: setupHeartbeatScheduler: The client is in healthy state.
06-04-2025 13:17:28.790 [main] INFO ingrian.security.nae.FF1Encryption - invoke0: reveal: Trying to fetch ap access policy from Key Manager...
06-04-2025 13:17:28.819 [main] INFO ingrian.security.nae.FF1Encryption - invoke0: reveal: Trying to fetch user user set for userName from Key Manager...
If required, you can choose to format the timestamp in GMT. To do this, select the Log GMT checkbox when defining CADP for Java application.
