Debugging
Issues? We all have them, learn how to cope with them
Last updated
Issues? We all have them, learn how to cope with them
Last updated
Here's a general list of troubleshooting steps if you're getting errors. The log files are VERY important since the error Lucee throws doesn't always contain the information you need. You will have to crack open your Lucee logs to get the actual error out.
Look in the "out" and "err" logs for information. These are usually found in the servlet container's log directory. For instance, if you're using Tomcat, look in Tomcat's log directory. There are often messages logged there that never make it up to the CFML engine.
The Log4J output of the underlying Couchbase Java SDK will be redirected to your Lucee server's "Application" log. Adjusting the logging level for this log will affect how much information you get from Couchbase.
Always scroll to the bottom of Java stack traces to look for a "caused by" section which is the original error.
If you are getting connection errors or Null pointer exceptions, check the spelling of your hostnames and ports and make sure Couchbase is actually running with the bucket name you specified in the config.
Once the library connects, you should see lines in the "out" log showing the servers being connected to successfully.
Open up the Couchbase web admin on one of your nodes and watch the "Ops per second" graph while you hit your app. If you see spikes in the graph every time you hit the app, then it's working!
If you need any help related to our Couchbase Extension product, you can use our online help group at our . If you need any type of custom consulting or support package hours, please contact us at or visit us at .