LO43302: NEW STARTUP SEQUENCE; EXITING AND RELAUNCHING CLIENT TOO FAST HA NGS; PREVIOUS PROCESS HAD NOT TERMINATED

APAR status

• Closed as program error.

Error description

• Vaibhav Telang (26th Nov 08)
  Build:
  Notes: 20081125.0245 (Release 8.5) production build.
  
  Steps to reproduce the defect:
  Launch Notes cleanly.
  Open Mail, Symphony document from Home page.
  With focus on Symphony document, exit Notes (I do not have
  'prompt me at exit
  ....' enabled)'.  Keep an eye on the task manager Notes
  processes (nlnotes.exe,
  notes2.exe)
  Quickly relaunch Notes from desktop.
  
  Expected Behavior: Notes should exit cleanly before the next
  startup sequence
  is initiated. Once the new startup sequence is initiated, Notes
  should be
  launched.
  Defect: When user tries to re launch notes quickly, before
  nlnotes.exe and
  notes2.exe are cleaned up, user can see a new set of these
  processes in the
  Windows Task Manager. For a moment you may see three instances
  of notes2.exe.
  
  At this stage, even if user don't provide the password, all the
  notes2.exe
  processes will get cleaned up. The first instance of notes2.exe
  gets closed
  first followed by the new instance. You will see only
  nlnotes.exe is running in
  the Windows Task Manager. If user provides password the process
  bar will
  complete to 100%, splash screen will go off and nlnotes.exe will
  be running in
  the task manager. If user launches Notes again at this stage,
  notes gets
  launched fine as notes2.exe is kicked off again.
  
  Additional observations
  When there are multiple notes2.exe and nlnotes.exe processes in
  the Windows
  Task Manager, you can observe that in case of
  notes2: The old notes2.exe process exits first followed by the
  second instance.
  nlnotes: Similarly, the old nlnotes.exe process gets cleaned up
  fine, the
  second instance remains there in ready state.
  
  State I: Client launched again, you can see two nlnotes.exe and
  one notes2.exe
  (previous instance) process.
  State II: During the relaunch, you can see two nlnotes.exe and
  two notes2.exe
  (previous instance) process.
  State III: After a few seconds, both the notes2.exe instances
  will exit (first
  the previous instance followed by the new one). The new
  nlnotes.exe instance
  will remain there in the Windows Task Manager.
  Note: When we try the same scenario on 1125.0245 non production
  build, we see a
  crash. Complete NSD attached to the attachment DB.
  
  ############################################################
  ### FATAL THREAD 18/27 [  notes2:  144c:  02c4]
  ### FP=0x1e4bffb4, PC=0x7dcb3ec4, SP=0x1e4bff9c
  ### stkbase=1e4c0000, total stksize=12288, used stksize=100
  ### EAX=0x00000102, EBX=0x7c901005, ECX=0x7c8025f0,
  EDX=0x7c90eb94
  ### ESI=0x1dfa2990, EDI=0x00000000, CS=0x0000001b,
  SS=0x00000023
  ### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000
  Flags=0x00010202
  Exception code: c0000005 (ACCESS_VIOLATION)
  ############################################################
   [ 1] 0x7c80b683 kernel32.GetModuleFileNameA+436
  (7dd1718b,1dfa2990,0,c8)
  
  ############################################################
  ### PASS 2 : FATAL THREAD with STACK FRAMES 18/27 [  notes2:
  144c:  02c4]
  ### FP=1e4bffb4, PC=7dcb3ec4, SP=1e4bff9c
  ### stkbase=1e4c0000, total stksize=12288, used stksize=100
  Exception code: c0000005 (ACCESS_VIOLATION)
  ############################################################
  
  Dev analysis (Update from Shweta)
  On Relaunch, when we see two instances of nlnotes, and notes2
  [Step 4]
  a> What we are seeing is in this case, the previous instance of
  nlnotes exits
  in sometime, and the new nlnotes instance reaches a stable-ready
  state. This is
  why, when the next time User clicks on Notes Icon, Standard
  Notes Launches
  successfully.
  
  b> Previous instance of notes2w exits, also the new instance
  seems to hit a
  piece in code, which  possibly checks for a running instance,
  finds it, and
  also exits. As a result Splash Screen is just left and the
  Client is not
  launched.  It does not log any message, so we don't know where
  this happened.
  Checking ...
  
  With some additional instrumentation we received this stack in
  the trace logs
  SEVERE
  CLPAG0020W: ConnectException while connecting to daemon
  java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(Unknown Source)
   at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
   at java.net.PlainSocketImpl.connect(Unknown Source)
   at java.net.SocksSocketImpl.connect(Unknown Source)
   at java.net.Socket.connect(Unknown Source)
   at java.net.Socket.connect(Unknown Source)
   at java.net.Socket.<init>(Unknown Source)
   at java.net.Socket.<init>(Unknown Source)
   at
  com.ibm.rcp.core.internal.launcher.Main.sendParamsToDaemon(Unkno
  wn Source)
   at com.ibm.rcp.core.internal.launcher.Main.main(Unknown
  Source)
   at com.ibm.rcp.core.internal.launcher.Main.run(Unknown
  Source)
  
  com.ibm.rcp.core.internal.launcher
  com.ibm.rcp.core.internal.launcher.Main
  .sendParamNamesToDeamon(SidModel,String[])
  
  
  Original SPR
  Clean install on Windows XP of :
  IBM Lotus Notes 8.5
  Release 8.5
  Revision 20080418.1445 (Build V85_04172008)
  Standard Configuration
  
  Enable new startup sequence:
  ENABLE_EARLY_AUTHENTICATION=1
  
  
  
  Exiting and then relaunching too fast is a problem.
  If you exit the client wait a few seconds (say 30), then you
  relaunch the
  client, it wiill work fine.
  However, if you exit the client, then go directly to file
  manager and relaunch
  the client, it hangs.  I did a nsd -dumpandkill
  It's easily reproducible.
  
  
  
  nsd -dumpandkill output is below in  stack section
  

Local fix

Problem summary

• A programming error was found and will be corrected in a future
  

Problem conclusion

• A programming error was found and will be corrected in a future
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• NA
  

Fix information

• Fixed component name

  NOTES CLIENT

• Fixed component ID

  5724E6255

Applicable component levels

• R850 PSN

     UP