Hmmmm… The Domino server is a little special when it comes to Java. All code/design is also contained in the NSF (Notes database). So you don’t have a “normal” Java deployment environment. As far as I know there is no default logger - but I’ll check if it can be configured.
Is there a better way to force a “correct” read after an update has been performed? I had the issue some time back and ideally just wanted to force the re-scan relevant for that single save. But the only way I found was to raise a flag and let that hit the next read… This approach feels wrong - but I couldn’t find another way that worked. But the SDK has been updated since so perhaps there is a better way…? If not, then I suppose I could improve my “mechanism” to include the type of information and only add it to the query parameters on the next read of that type…
Also note that I really use QueryScanConsistency.REQUEST_PLUS sparsely - so absolutely not on every save - only when the application depends on having the latest updates available…
This functionality has been used for at least a couple of years - and we have not seen these issues before. I had to re-do some of the logic when I installed SDK 3.1 (e.g. when getting the collection etc.) - but that is still a while back. The system should not really be heavily used at the moment (it’s an “angler’s app” and not highest season right now). But perhaps some timings etc. have changed with version 7.0 that is now tipping us over the top?