A new IBM technote has been released for XPages Partial Refresh Throwing CLFAD* Errors. As suspected, the cause was tightening up validation and, instead of falling back to reloading the page, it throws an error. I remember in 8.5.1 a similar issue where passing an error object to some logging started throwing an error because of greater validation.

For those who have not used it and have been hunting in the XPages logs for such errors, this is a good time to point people towards XPages OpenLog Logger, the code for which is also incorporated into OpenNTF Domino API. With a custom error page in your XPages application, this will ensure such uncaught errors are logged to OpenLog.

There is a workaround in the technote, setting an xsp.property. One option is to set this on an NSF-by-NSF basis. But it’s worth reminding people that this can be set server-wide, by adding an xsp.properties file in <Domino>\data\properties. There is a sample properties file to start you off. Presumably, because it’s loaded by the XPages runtime to define settings, it will only need a restart of HTTP (res t http) after changes.

NOTE: ADDING THIS SETTING TO XSP.PROPERTIES ON THE SERVER DOESN’T SEEM TO WORK, ONLY IN NSF.

1 thought on “XPages Partial Refresh and Server-Wide Xsp Properties”

  1. I’ve got an open ticket with IBM over this, but the workaround did not work (using server xsp.properties, xsp.error.disable.detection.set01=true).
    I didn’t try the NSF by NSF method, perhaps I will.
    Thanks Paul!

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.