PH60824: IBM EXPLORER FOR Z/OS V3.3 - HIGH CPU CONSUMPTION AFTER RUNNING IVP.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An IVP Daemon or an interrupted real connection may leave behind
  the ZosServerLogger's LogWriterThread per run and
  ServerUpdateHandler.  Stack trace shows that the ServerThread
  was exiting under the socket error condition caused by client
  terminated in an IVP DAEMON run.  The cleanup of the handler
  thread got an i/o socket exception when sending the client the
  last ack msg.  The handler threads are left over and likely
  consuming high CPU due to continuous attempts to process the
  message queue.
  
  
  ERROR: class
  org.eclipse.dstore.core.server.ConnectionEstablisher:
  java.net.SocketException: Socket output is already shutdown
  ERROR: com.ibm.jsse2.bj.getOutputStream(bj.java:127)
  ERROR:
  org.eclipse.dstore.core.server.ConnectionEstablisher.doHandShake
  (ConnectionEstablisher.java:743)
  ERROR:
  org.eclipse.dstore.core.server.ConnectionEstablisher.waitForConn
  ections(ConnectionEstablisher.java:345)
  ERROR:
  org.eclipse.dstore.core.server.ConnectionEstablisher.run(Connect
  ionEstablisher.java:670)
  ERROR:
  org.eclipse.dstore.core.server.ConnectionEstablisher.start(Conne
  ctionEstablisher.java:206)
  ERROR:
  org.eclipse.dstore.core.server.Server.run(Server.java:199)
  ERROR: java.lang.Thread.run(Thread.java:825)
  ERROR:
  org.eclipse.dstore.core.server.SecuredThread.run(SecuredThread.j
  ava:164)
  ERROR: class org.eclipse.dstore.core.server.ServerReceiver:
  java.lang.NullPointerException
  ERROR:
  org.eclipse.dstore.internal.core.util.XMLparser.readLine(XMLpars
  er.java:399)
  ERROR:
  org.eclipse.dstore.internal.core.util.XMLparser.parseDocument(XM
  Lparser.java:590)
  ERROR:
  org.eclipse.dstore.core.util.Receiver.handleInput(Receiver.java:
  155)
  ERROR:
  org.eclipse.dstore.core.util.Receiver.run(Receiver.java:127)
  ERROR: class org.eclipse.dstore.core.server.ServerReceiver:
  java.lang.NullPointerException
  ERROR:
  org.eclipse.dstore.internal.core.util.Sender.sendDocument(Sender
  .java:308)
  ERROR:
  org.eclipse.dstore.internal.core.server.ServerUpdateHandler.remo
  veSenderWith(ServerUpdateHandler.java:348)
  ERROR:
  org.eclipse.dstore.core.server.ConnectionEstablisher.finished(Co
  nnectionEstablisher.java:261)
  ERROR:
  org.eclipse.dstore.core.server.ServerReceiver.handleError(Server
  Receiver.java:144)
  ERROR:
  org.eclipse.dstore.core.util.Receiver.handleInput(Receiver.java:
  181)
  ERROR:
  org.eclipse.dstore.core.util.Receiver.run(Receiver.java:127)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1. All users                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. The user ServerThread connection     *
  *                      establisher may not handle properly     *
  *                      the socket exception conditions         *
  *                      caused by client socket closing when    *
  *                      the connection terminates.              *
  ****************************************************************
  1. Socket exception (due to client terminated abruptly) may
  leave user threads left over with no client holder at the
  Threadpool.
  

Problem conclusion

• 1. As socket exception is critical (and expected during IVP
  Daemon runs), it should be treated as error during the
  handshake message message exchange for a cleaner connection
  establishment shutdown.
  Exception handling is added for update handler to handle
  issues related to client socket closing.
  

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

• FEJENF70 FEJJCNFG FEJJJCL  FEJJMON  FEJTSO   FEK1SMPE FEK2RCVE
  FEK3ALOC FEK4ZFS  FEK5MKD  FEK6DDEF FEK7APLY FEK8ACPT FEK@CERR
  FEK@CONE FEK@CONF FEK@CUST FEK@DEB  FEK@DESC FEK@FLOW FEK@GEN
  FEK@GENW FEK@ISPF FEK@IVP  FEK@IVPD FEK@IVPW FEK@JCN1 FEK@JCNE
  FEK@JESJ FEK@MAIN FEK@MIGO FEK@OPTE FEK@OPTG FEK@OPTN FEK@PRIM
  FEK@RSE1 FEK@RSEO FEK@STRT FEK@TAB1 FEK@TAB2 FEK@TAB3 FEK@WRK1
  FEK@WRK2 FEK@WRK3 FEK@WRK4 FEK@WRK5 FEKAPPCC FEKAPPCL FEKAPPCX
  FEKATTR  FEKDSI   FEKEESX0 FEKFASIZ FEKFATT1 FEKFBLD  FEKFCIPH
  FEKFCLIE FEKFCMOD FEKFCMPR FEKFCMSG FEKFCOMM FEKFCOPY FEKFCOR6
  FEKFCORE FEKFDBG  FEKFDBG6 FEKFDBGM FEKFDIR  FEKFDIR6 FEKFDIVP
  FEKFDST0 FEKFDST1 FEKFDST2 FEKFENVF FEKFENVI FEKFENVP FEKFENVR
  FEKFENVS FEKFEPL  FEKFERRF FEKFGDGE FEKFICUL FEKFISPF FEKFIVP0
  FEKFIVPA FEKFIVPD FEKFIVPI FEKFIVPJ FEKFIVPT FEKFJESM FEKFJESU
  FEKFJLIC FEKFJSON FEKFJVM  FEKFLATR FEKFLDSI FEKFLDSL FEKFLEOP
  FEKFLOGS FEKFLPTH FEKFMAI6 FEKFMAIN FEKFMINE FEKFMNTL FEKFNTCE
  FEKFOMVS FEKFPATT FEKFPKCS FEKFPLUG FEKFPTC  FEKFRIVP FEKFRMSG
  FEKFRSES FEKFRSRV FEKFSCMD FEKFSEND FEKFSSL  FEKFSTUP FEKFT000
  FEKFT002 FEKFT003 FEKFT004 FEKFT005 FEKFT006 FEKFT007 FEKFT008
  FEKFTEAM FEKFTIVP FEKFTSO  FEKFUTIL FEKFVERS FEKFXITA FEKFXITL
  FEKFZOS  FEKHCONF FEKHCUST FEKHDEB  FEKHDESC FEKHFLOW FEKHGEN
  FEKHISPF FEKHIVP  FEKHIVPD FEKHJESJ FEKHMAIN FEKHMIGO FEKHOPTE
  FEKHOPTN FEKHPRIM FEKHRSE1 FEKHRSEO FEKHSTRT FEKHTAB1 FEKHTAB2
  FEKINIT  FEKKEYS  FEKLOCKA FEKLOGR  FEKLOGS  FEKM00   FEKM01
  FEKM02   FEKMKDIR FEKMOUNT FEKMSGC  FEKMSGS  FEKPKCS1 FEKRACF
  FEKRSED  FEKSAPF  FEKSAPPL FEKSBPX  FEKSCLAS FEKSCLOG FEKSCMD
  FEKSCPYM FEKSCPYU FEKSDSN  FEKSENV  FEKSETUP FEKSISPF FEKSJCFG
  FEKSJCMD FEKSJMON FEKSJWT  FEKSJWTU FEKSLPA  FEKSPROG FEKSPTKT
  FEKSRSED FEKSSERV FEKSSTC  FEKSSU   FEKSUSER FEKXCFGE FEKXCFGI
  FEKXCFGM FEKXCFGT FEKXMAIN FEKXML   HUHFCOR6 HUHFCORE
  

Fix information

• Fixed component name

  EXP FOR Z/OS HO

• Fixed component ID

  5655EXP23

Applicable component levels

• R330 PSY UI97198

     UP24/06/15 P F406

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.