Notes/Domino Fix List
 |  |
| SPR # SVRO5S6QZ6 | Fixed in 5.0.13 release | Regression in 5.0.12 |
Product Area: Client Technical Area: Networking & Dialup Platform: Cross Platform
Lotus Customer Support APAR: LO00547
SPR# SVRO5S6QZ6 - Fixed Sessions from not dropping. This problem was a regression introduced in 5.0.12.
Technote Number: 1106365
Problem:
This issue was reported to Lotus software Quality Engineering as SPR#
SVRO5S6QP3, and has been addressed in Domino 5.0.13 / 5.0.13a.
Excerpt from the Lotus Notes and Domino Release 5.0.13 / 5.0.13a MR fix list
(available at http://www.ibm.com/developerworks/lotus):
SPR# SVRO5S6QP3 - Fix to remove hung session problems. This was fixed in 5.0.13
and was a regression introduced in 5.0.12.
SPR# SVRO5S6QZ6 - Fixed Sessions from not dropping. This problem was a
regression introduced in 5.0.12.
Hung inactive sessions take a minimal amount of memory, less than a 1 kilobyte
per session. For this reason it is not likely that the hung sessions are
causing a performance problem and/or the "Server not responding" error.
Currently, the hung sessions are attributable to two causes:
Async New Mail Notification
[See document "Asynchronous New Mail Notifications Cause Higher CPU Consumption
in Domino 5.0.9 and Later" for details (#: 1087595 )]
and
Use of the Domino Administrator's live remote console
There were changes made in Domino 5.0.9 that were intended to restore
asynchronous mail notification over existing sessions for new mail
notification, console broadcast commands, and view updates. This functionality
had been lost in 5.0. A new mail check packet is sent every 10 seconds.
However, in some environments, it was found that NRPC sessions sometimes remain
open in a hung state and are unable to be dropped. Additional changes in
5.0.12 to improve remote console performance have increased the likelihood of
hung sessions. The changes implemented prior to 5.0.12 can be disabled via a
NOTES.INI parameter. The 5.0.12 changes cannot.
Disabling IOCP ASYNC Notification:
To disable IOCP ASYNC Notification, add the following parameter to the Domino
server's NOTES.INI and restart the Domino server:
IOCP_DISABLE_ASYNC_NOTIFICATION=1
NOTE: The use of this parameter will disable the following:
1. The functionality described in the document titled "'On Refresh' Option To
"Refresh Display" Does not Refresh Automatically" (#1099398).
2. Opportunistic New Mail notification. IMPORTANT: Client new mail polling
every X minutes still works, and end users still receive the normal New Mail
notification. Here is more detail:
Async Notification is a server feature that polls mail files every 10 seconds
for every existing server session. When new mail arrives, a notification is
sent to the client. This feature is not to be confused with the new mail
notification that is initiated by the client. You will still be able to use
the client polling feature located in User Preferences.
3. Being able to send a broadcast command from the server console using a
specific UserName; e.g., Broadcast "Message" [UserName]
If you are experiencing a performance issue that you suspect is related to many
hung sessions that will not drop, follow the steps outlined below. (Note that
it should not be necessary to follow these steps if you have only a limited
number of hung sessions, unless instructed by IBM Technical support. A session
takes up only a small amount of memory, and thus a limited number of hung
sessions should not have any adverse impact.)
1. Add the following to Domino server NOTES.INI and reboot Domino:
Debug_Threadid=1 (Logs each process and thread id for each server operation.)
Log_Sessions=1 (Will generate a message for every new and closed session.)
Debug_Show_Timeout=1 (Turns on semaphore timeout messages to the console and
creates a semaphore text file located in the program directory).
Debug_Capture_Timeout=10 (Time stamps each semaphore timeout message).
Debug_Outfile=X:\outfile.txt (Used to capture the Domino console output in a
text file. In place of "X:", specify a drive with sufficient space).
2. If Notes client(s) intermittently pause, showing an hour glass for a very
long time (more then a minute) before connecting to Domino and gaining access
to the particular database, then in addition to the above, add the following to
the client Notes.INI:
Client_Clock = 1
Debug_Console = 1
Debug_Outfile=X:\temp\client.txt
When hung sessions are causing a noticeable server problem, do the following:
1. Record the user(s) that are having the problem
2. Record what database the user(s) are having a problem with.
3. At the Domino console perform the following commands:
sho ta debug >ta.txt
sho user debug >user.txt
sho port (tcp port name) >port.txt
sh memory dump >memory.txt
drop all
4. Repeat console commands (give the output file a different name). The .txt
files should be in the Domino data directory.
5. From an operating system prompt, perform the following commands:
NSD (at the server and Notes Client workstation)
Netstat -a >netstat.txt (at the server and Notes Client workstation)
The above steps should be followed when users (1) are locked out of a
particular view, (2) get a long delay while accessing a database (hour glass),
or (3) receive the error "server not responding". Before we set an action plan
for performance-related problems, we need to know what that problem is; for
example, insufficient system resources, server hung (cannot type console
commands), high CPU utilization, etc. More >
Last Modified on 12/10/2013
Go back
|