I was recently working on an XPage, changing a number of things at the same time, and could not manage to get one of my fields with typeahead to work. It did not throw an error to the browser, the XPage code had compiled without error. When I looked at the Notes Log I found the following message returned:
HTTP JVM: SEVERE: CLFAD####E: Exception processing XPage request
After stripping down the page trying various things, I found that there was an error in the typeahead formula language – I had changed it from an @DbLookup to a keyword document to an @Unique(@DBColumn… on a view, but I had not removed the ‘key’ parameter, so I had too many parameters. The mistake had not been picked up when coding, so easily fixed. The actual error was identified when using the following try…catch block, using OpenLogXPages (as found in TaskJam).
try{
@Unique(@DbColumn(@DbName(),”vwQuotes”,”Status”,1));
} catch(e) {
log.logError(e.toString());
}}
What I got was:
com.ibm.jscript.InterpretException: Script interpreter error, line=1, col=13: Error while executing function ‘@DbColumn’
The key was to use log.logError(e.toString()), instead of log.logError(e) – e returned a Vector. With this accumulated knowledge, I’m sure if I encounter another error I will be able to isolate it more quickly.
