LO55378: CLIENT CRASH NSD FILES ALL SHOW "CANCELING THREAD #### AFTER 300 SECONDS", NSD.EXE HANGS

APAR status

• Closed as Permanent restriction.

Error description

• In a VM environment, after a client crash, nsd.exe hits
  about 100% CPU.   Users are able to restart and use the client,
  however
  performance is poor since nsd.exe is using all the CPU.
  
   Often when the client crashes, the NSD screen appears and
  then hangs.    In each case at the bottom of the NSD is:
  
  ERROR (0): canceling thread 4912 after 300 seconds
  
  (the thread number changes, but they all say canceling after 300
  seconds).
  
  In this case, no javacore was created.
  

Local fix

• Temporary fix - kill NSD process.
  

Problem summary

• A programming error was found but will not be corrected. It
   will be a permanent restriction.
  

Problem conclusion

• A programming error was found but will not be corrected. It
   will be a permanent restriction.
  

Temporary fix

Comments

• This APAR is associated with SPR# JSTN89YUST.
  

APAR Information

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

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

Fix information

Applicable component levels