So I'm told...
I love the Lotus Support Services RSS Feeds. I got a "Flash" hit today that appears to be related to my prior Sametime for iSeries problems I wrote about here and here.
The "Flash" regarding Sametime is here. The workaround is to (a) Remove awareness functionality for Names and (b) to add the following line to each Client notes.ini: IM_SHOW_STATUS=0. After I sent the Lotus Support tech the question if this is our problem, I was told that it appears to be. Now that 90+% of my Notes Clients are at 6.5.2 or higher because Lotus wants us to use integrated IM in the Client, I see that this can actually cause the server to hang. This is wonderful! Below is the text of the Flash:
Interaction between Notes client 6.5.2 and higher instant messaging (IM) and the IBM Lotus Instant Messaging and Web Conferencing (Sametime) server causes the CPU on both the Sametime server (STMux and STCommunity processes) and the Notes client (nlnotes process) to spike.
Symptoms of this problem include:
--The nlnotes process on the Notes client spikes to 100%.
--Stmux and StCommuntity processes on the Sametime server are pegged at above normal rates that will eventually reach 100%.
--Logging off from the Notes client instant messaging returns the CPU on the Nlnotes process to normal.
The technote titled "Integrated Awareness on Notes 6.5.2 and Higher Will Result in Server Outages" (#1206369), describes the symptoms, workaround, and fix information for this issue.