IT24511: N IBM SPECTRUM CONTROL CONTEXT ROOT NOT FOUND AFTER REBOOTING THE SYSTEM

IBM Spectrum Control V5.2.17 (May 2018)

APAR status

• Closed as program error.

Error description

• There is no retry mechanism implemented for Web server's GUI
  OSGI bundle on start when DB2 is not available.
  The GUI OSGi bundle just fails if DB2 is not ready yet to accept
  connections and it causes the Web UI to remain down showing:
  "Context root not found".
  
  
  The common situations where the Web UI display "Context root not
  found" because the Web server was not started properly and the
  workaround as follow :
  1. reboot the system running Spectrum Control and DB2, the SC
  servers start quicker and DB2 is not ready yet. It is needed
  restart Web server using the scripts once DB2 is up and running.
  2. have the SC servers running and restart only DB2. Once DB2
  has been restarted the Web server should be restarted too.
  
  Examples:
  messages.log
  00000044
  com.ibm.ws.app.manager.esa.internal.DeploySubsystemAction    A
  CWWKZ0402E: A bundle exception was generated when trying to
  install the application TPC-GUI-Application into an OSGi
  framework.  The error text from the OSGi framework is: Exception
  in com.ibm.tpc.gui.osgi.Activator.start() of bundle TPC-GUI.
  00000044
  .ibm.ws.http.whiteboard.SubsystemServletContextHelperFactory A
  CWWKN2001A: HTTP Whiteboard context root removed:
  http://<host_name>:9568/osgi/http/TPC-GUI-Application
  0000007d com.ibm.ws.app.manager.AppMessageHelper
  A CWWKZ0012I: The application TPC-GUI-Application was not
  started.
  
  
  traceDatabase_0.log
  [Default Executor-thread-30]
  [DBConnPoolDataSource.getPooledConnection] [ERROR] Error getting
  pooled connection com.ibm.db2.
  jcc.am.DisconnectNonTransientConnectionException:
  [jcc][t4][2043][11550][4.19.49] Exception
  java.net.ConnectException: Error opening socket to server
  <host_name>/<IP> on port
  50,000 with message: A remote host refused an attempted connect
  operation. (Connection refused). ERRORCODE=-4499, SQLSTATE=08001
  

Local fix

• The workaround is to manually re-start the scripts
  stopTPCWeb.sh / startTPCWeb.sh:
  >cd /opt/IBM/TPC/wlp/bin
  server stop webServer
  server start webServer --clean
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Control 5.2.x users experiencing "Context root  *
  * not found" in the web GUI                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IBM Spectrum Control didn't have a retry mechanism           *
  * implemented                                                  *
  * for web server's GUI OSGi bundle when DB2 is not available.  *
  *                                                              *
  * The GUI OSGi bundle simply fails if DB2 is not ready yet to  *
  * accept                                                       *
  * connections, and that causes the Spectrum Control web GUI to *
  *                                                              *
  * remain down showing: "Context root not found".               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available                         *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package:
  
  IBM Spectrum Control 5.2.17  |  refresh pack  |
  5.2-TIV-TPC-RP0017  |  May 2018
  
  http://www.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future releases do not represent a formal
  commitment by IBM. The dates are subject to change without
  notice.
  

Temporary fix

• The common situations where the Spectrum Control web
  GUI displays "Context root not found" is because the Web
  server was not started properly.
  
  Workarounds:
  
  1. Reboot the system running Spectrum Control and DB2, the
  Spectrum Control servers start quicker and DB2 is not ready
  yet. Restart the Web server manually using the Spectrum
  Control service scripts once DB2 is up and running.
  
  2. Have the Spectrum Control servers running and restart only
  DB2. Once DB2 has been restarted the Web server should be
  restarted too.
  

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

• Fixed component name

  TPC ADVANCED

• Fixed component ID

  5608TPCA0

Applicable component levels