The bug is nasty in that the usual log entries are not written before the crash making it very difficult to track it down. The NSD logs didn’t seem to work with the Lotus LND tool, I need to check if this is still valid.
The problem does occur in 9.01 FP2 FP3 on Linux but not in XPinC 9.01
Update 2 : It appears to have been fixed in 9.01 FP3 under and I can confirm that it does not fail in 9.01 FP4
YSAI9CCBYGFixes Domino Server crash when executing notesView.getColumnValues method, if there are many documents in a database.
Update 1 : NSD logs did point to the problem
Looking at the console_acme.com_2015_06_22@15_13_49.log I can see the following line in the “Stack Backtrace” section. This gives a good hint to the problem although the individual XPage is not listed. There may be other debug parameters that would help with that.
When we use JAR files such as DocX4J for exporting from XPages we need to store these within the git repositories so that the developer can add them to their /jvm/lib folder when building the XPage application. If the correct jars are not present the build fails.
The files are stored in a /jar folder away from the /notes folder where the Noes design elements are. We also use a /documentation folder for user guides etc..
When you add these jar or zip files to the repo they do not appear in SourceTree. In my case all that appeared was the /jars/readme.txt file.
The project specific .gitignore file was blank but the default settings in git are to ignore all compiled files and all zipped files. Given that we store documentation and artwork files int eh repo the .zip would also a problem for us.
You need to modify the global .gitignore file as shown below. The project specific .gitignore file is additive tot he global settings and does not replace them.
I am very honored to be speaking at the fantastic Engage User Group ( formerly known as BLUG ) this week.
The session is called “Seeing the Wood for the Trees” and is about how I and my colleagues use Domino Designer, Git Source Control and some mostly Atlassian products to manage our help tickets, project management, release management and billing.
The session is at 14:45 on Tuesday and is 50% slides / 50% live demo.
As I have learnt to my cost before it is difficult to go into Source Control in deep detail in 45 minutes so this session is a high level overview for both managers and Developers to show some of what can be achieved by using Source Control with Domino.
We waited a long time for Source Control in DDE and it got off to a shaky start but I am really pleased with what IBM has given us and how it works now. It really has allowed us to integrate the management of Notes / XPages code into our overall processes.
There is obviously more we want to do but this is a good story to share.
All suggestions welcomed. Apologies in advance for needing to moderate comments – my only disappointment in moving from Domino Blog has been how badly WP manages Spam – even with various plug-ins.