If you have enabled logging of slow pages, ColdFusion will track those here.FileZilla includes two ways of logging all communication with the server, which essentially consists of commands sent by the client and server replies. Server.log: When your server starts up, it will log details of that process here. To enable it, head over to the Mail Logging Settings. If enabled, this log will capture TO, FROM, and SUBJECT from all mail sent.
Mailsent.log: Its possible to keep a log of all mail sent by ColdFusion. You can adjust what is captured in the Mail Logging Settings. This your go-to log for any issues with sending mail from ColdFusion. Mail.log: Issues with the mail server can be tricky to debug, since it is sent (and can fail) in a background process. Note that Event Gateways are an Enterprise feature.Įxception.log: This is a more detailed version of the application.log, and includes stack trace information to help identify issues. Inspect this file periodically to ensure your application is not breaking in a way you were unaware of.Įventgateway.log: This log contains any errors or exceptions thrown by the Event Gateway. Note that you can specify log setting per application which is very helpful because you can have an application log for each application.Īpplication.log: A summary of most errors thrown by ColdFusion are captured here. Log files are one of the most powerful tools for debugging applications and are very useful for performance tuning. Trying to manipulate very large log files in the browser can be unwieldy. While it is convenient, we have found it much more productive to investigate these files in a dedicated log viewer or text editor. log files within your log directory (as specified in the Logging Settings). Here ColdFusion provides an interface to view and manage all. Optimizing, Tuning, & Scaling ColdFusion – Threading.
0 kommentar(er)
