lekkimworld.comtechnote

Windows 2008 64-bit can cause a significant CPU increase and I/O degradation when Domino opens many databases

Fri, 10 Feb 2012 10:52:24 GMT

Had a customer report the above issue and have it fixed by IBM so I thought others might benefit from it. The issue has been fixed as IBM SPR# KBRN8AKKA9. The technote is 1449825 and contains a lot of good info. Setting notes.ini "Disable_Random_RW_File_ATTR=1" fixes the issue.

"After Domino opens many NSF files in quick succession during a backup, the Virtual Address Space of the OS system cache may be completely used up (for example, 1TB of data may be used in this OS cache). Successive calls into the OS cache manager to get memory from the OS system cache then results in mapping/unmapping of views from the system cache. These mapping/unmapping operations takes a lot of CPU time and as a result shows as high OS CPU usage. In addition, because the large OS system cache may now reside on the disk (the RAM is not large enough to hold the OS system cache) this results in significant I/O on the system."

Useful RnrMgr technote

Mon, 09 Nov 2009 20:51:32 GMT

Technote 1391768: How to hide the description of private Calendar entries in the Resource & Reservations database

Differences between Notes/Domino Maintenance Releases, Fix Packs and Cumulative Client Hotfixes

Thu, 18 Jun 2009 12:47:00 GMT

Technote 1368141: Differences between Notes/Domino Maintenance Releases, Fix Packs and Cumulative Client Hotfixes

Will Notes be supported on Windows 7?

Thu, 18 Jun 2009 07:09:00 GMT

Check out technote 1385293: Lotus Notes support of Microsoft Windows version 7. Although the technote doesn't clarify anything it's nice to know that Lotus is aware of this upcoming OS release and is monitoring the situation and working with Microsoft as we would expect.

Do not run both the CA process and ID Vault at the same time

Thu, 28 May 2009 08:13:47 GMT

Be aware of running both CA process and ID Vault at the same time as the ID stored in the vault hasn't been certified yet. The limitation is understandable but why it's possible (i.e. the checkbox is available in the UI) to store a newly registered ID when using CA process can be confusing.

For more info see technote 1367969: ID Vault upload during registration fails when using Certificate Authority

Allowing diagnostic data to be sent to IBM

Fri, 24 Apr 2009 05:08:22 GMT

What if the CRASH_SENDTOIBM notes.ini setting was set for all new Domino Server installations; imagine how much diagnostic information that IBM would gather that would make the product better for all of us? I know there are privacy concerns and test servers but still...

"When the Notes.INI setting CRASH_SENDTOIBM=1 is set on the server, no additional configuration is required. When the server restarts after a server crash, diagnostic information is collected and an email is sent to IBM."

Technote 1321120: Allowing diagnostic data to be sent to IBM

Doing Java in Notes? - make sure you know about JavaCompilerTarget

Thu, 16 Oct 2008 12:25:53 GMT

I blogged about the JavaCompilerTarget back in August last year when Notes 8 came out as you needed it to enable Java 5 in Domino Designer. Last week some nice new info on this notes.ini setting came my way in the Design Partner forum for Domino NEXT. If you're doing Java development in Notes you would want to read on.

And yes - I did check with IBM whether it was okay to blog it. Since this info is on its way out in technote (technote 1320401) it was fine that I blogged it.

JavaCompilerTarget

In Notes/Domino 8.5, you can set the JavaCompilerTarget INI variable to any value from 1.1 through 1.6. Here is a draft of the documentation (Note: In the following text, we refer to JDK 1.6, which is also known as JDK 1.6.0 and JDK 6.0.)

By default, Notes/Domino 8.5 utilizes JDK 1.6 to compile and run agents, but it limits language features to maintain backwards compatibility through JDK 1.2, to allow agents to run on earlier Notes/Domino installations (and, more generally, with any JVM version earlier than the target flag), regardless of whether the new language features are actually used in the agent's code (e.g., setting JavaCompilerTarget=1.6 could introduce the possibility of having an agent recompiled and replicated to a V8.0 server, and then failing to run). Additionally, problems could arise editing and saving agents compiled in Notes/Domino installations that are not using the same INI setting.

Developers must override the default behavior if they wish to use features specific to different JDKs. The default behavior is equivalent to the setting JavaCompilerTarget=1.2

In Notes/Domino V8.5, the developer may specify any JavaCompilerTarget from 1.1 to 1.6. (In each case, the -source flag is the latest source that can be specified with a particular -target flag.)

The developer may also specify JavaCompilerTarget=CurrentJavaVersion which means the target flag will be synced to the version in future Notes/Domino releases (e.g., if some future Notes/Domino version were to include JDK 1.9, then "JavaCompilerTarget=CurrentJavaVersion" would create "-target 1.9").

JavaCompilerTarget	Resulting compiler flags	Agent would run on Notes/Domino versions
1.1	-source 1.3 -target 1.1	V5.0 or later
1.2	-source 1.3 -target 1.2	V6.0 or later
1.3	-source 1.3 -target 1.3	V6.0 or later
1.4	-source 1.4 -target 1.4	V7.0 or later
1.5	-source 1.5 -target 1.5	V8.0 or later
1.6	-source 1.6 -target 1.6	V8.5 or later
CurrentJavaVersion	-source 1.6 -target 1.6	V8.5 or later

Remember that these settings may prevent compiled agents from running on some earlier Notes/Domino installations. Therefore, it is suggested that organizations use a consistent setting across machines.

Developers who will not be using language features specific to recent JDKs are encouraged to keep the default Notes/Domino behavior to maximize backward compatibility.

Technote 1096316

Tue, 18 Mar 2008 06:19:00 GMT

Technote 1096316: Documents copied using CopyToDatabase method reuse same UNID