8.5.1 is still broken for large applications
Category Lotus Notes Lotus Domino LotusScript
A while ago Erik Brooks blogged about a major problem introduced in Notes/Domino 8.5.1. IBM reacted to this quite fast and released a fix for the problem.
Erik has posted a summary of where we are with the issue here: 8.5.1 UNFAIL - Part 2: The Fix.
Basically the problem introduced in 8.5.1 is that the behaviour of all variants of GetSOMETHINGByKey (For instance GetAllDocumentsByKey) has changed compared to earlier releases of Notes/Domino. Now the LotusScript might fail with "The collection has become invalid" if the view used was updated while the LotusScript code was running.
If you have an application with "lots" of document updates, this issue will show up at your site.
A fix was released, but only available on request from Lotus Support. But at least you can have it.
Now it looks like the fix is actually only a half way fix. It apparently only addresses the issue when the LotusScript is executed on the Lotus Domino server. In an agent for instance. But the original problem is also seen when the GetSOMETHINGByKey is executed from a Lotus Notes client. Have a look in the comments on the original blog entry. Comments number 27, 28 and 29: 8.5.1 FAIL. Your code may just break.
Most of the organisations that I know who have Notes/Domino Applications will experience this problem. This is a major bug, and it does not sound like it is scheduled for a quick fix.
A while ago Erik Brooks blogged about a major problem introduced in Notes/Domino 8.5.1. IBM reacted to this quite fast and released a fix for the problem.
Erik has posted a summary of where we are with the issue here: 8.5.1 UNFAIL - Part 2: The Fix.
Basically the problem introduced in 8.5.1 is that the behaviour of all variants of GetSOMETHINGByKey (For instance GetAllDocumentsByKey) has changed compared to earlier releases of Notes/Domino. Now the LotusScript might fail with "The collection has become invalid" if the view used was updated while the LotusScript code was running.
If you have an application with "lots" of document updates, this issue will show up at your site.
A fix was released, but only available on request from Lotus Support. But at least you can have it.
Now it looks like the fix is actually only a half way fix. It apparently only addresses the issue when the LotusScript is executed on the Lotus Domino server. In an agent for instance. But the original problem is also seen when the GetSOMETHINGByKey is executed from a Lotus Notes client. Have a look in the comments on the original blog entry. Comments number 27, 28 and 29: 8.5.1 FAIL. Your code may just break.
Most of the organisations that I know who have Notes/Domino Applications will experience this problem. This is a major bug, and it does not sound like it is scheduled for a quick fix.
