IV99202: TEMS HANGS DURING WARM SHUTDOWN

APAR status

• Closed as Permanent restriction.

Error description

• The Windows TEMS does not terminate following the ./CandleServer
  stop
  <temsname> command.
  
  The resulting TEMS debug log is missing the following text in
  the log
  entries,
  
  (599F1E7D.0007-4:kdsmacmd.c,3046,"StopTask") Calling task =
  WEBSQL with
  STOP
  (599F1E7D.0008-2D:kshstrt.cpp,405,"start_http_server_thread")
  Thread for
  hub SOAP is exiting with status 0
  (599F1E7D.0009-7:kdsmacmd.c,2928,"startedTask") Program WEBSQL
  with task
  id 6 ended
  (599F1E7D.000A-4:kdsmacmd.c,3058,"StopTask") Task = WEBSQL
  received
  STOP, waiting for task termination.
  
  Notably the trace line
  
  (599F1E7D.0008-2D:kshstrt.cpp,405,"start_http_server_thread")
  Thread for
  hub SOAP is exiting with status 0
  
  does not appear in the trace log. This implies that that the
  TEMS' SOAP
  Server did not shut down as requested in the TEMS Shutdown
  processing.
  
  RECREATE INSTRUCTIONS:
  Repeatedly issue CLI commands.
  With CLI users remaining logged onto the TEMS, stop the TEMS
  using the
  command itmcmd server stop <tems_name>
  

Local fix

• Stop the TEMS Service kmsmain using Task Manager
  

Problem summary

• The Monitoring Server that executes on a Windows system  may not
  perform an orderly shut down.
  

Problem conclusion

• The Monitoring Server may be waiting longer than 10 minutes for
  the orderly termination of embedded Websphere Application Server
  service.
  

Temporary fix

• Use the Windows Task Manager to manually terminate the kdsmain
  process.
  

Comments

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