Understand the Problem
We document the symptoms, incident history, affected services and troubleshooting already performed.
Understand the Problem
We document the symptoms, incident history, affected services and troubleshooting already performed.
Review the Environment
Our engineers examine the relevant ColdFusion, Java, application, web-server, database and infrastructure components.
Analyze the Evidence
We correlate logs, metrics, errors, diagnostic files, configuration and recent changes.
Recommend a Correction
We explain our findings and provide clear next steps for correcting the issue and reducing the chance of recurrence.
Logs and diagnostic files must be interpreted in the context of the application and its environment. A large log or dump file may contain thousands of events unrelated to the incident.
Heap analysis can help locate objects retaining excessive amounts of memory. ColdFusion logs can reveal out-of-memory conditions and other errors that occurred around the crash.
Common areas to investigate include errors in jvm.config, special JVM arguments, Java compatibility, the CFStart utility and an unavailable Tomcat service.
The visible error is not always the root cause. Recent updates, configuration changes, file permissions and service-account access may all need to be reviewed.