PI19874: MANAGEMENT CONSOLE DOES NOT START SERVICE LAYER CORRECTLY

Rational Build Forge Fix Pack 6 (7.1.3.6) for 7.1.3
Rational Build Forge Fix Pack 3 (8.0.0.3) for 8.0
Rational Build Forge Fix Pack 4 (8.0.0.4) for 8.0
Rational Build Forge Fix Pack 5 (8.0.0.5) for 8.0
Rational Build Forge Fix Pack 6 (8.0.0.6) for 8.0
Rational Build Forge Fix Pack 7 (8.0.0.7) for 8.0
Rational Build Forge Fix Pack 8 (8.0.0.8) for 8.0
Rational Build Forge Fix Pack 9 (8.0.0.9) for 8.0
Rational Build Forge Fix Pack 10 (8.0.0.10) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.10
Rational Build Forge Fix Pack 11 (8.0.0.11) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.11
Rational Build Forge Fix Pack 12 (8.0.0.12) for 8.0
Rational Build Forge Fix Pack 13 (8.0.0.13) for 8.0
Rational Build Forge Fix Pack 14 (8.0.0.14) for 8.0
Rational Build Forge Fix Pack 15 (8.0.0.15) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.15
Rational Build Forge Fix Pack 16 (8.0.0.16) for 8.0
Rational Build Forge Fix Pack 17 (8.0.0.17) for 8.0
Rational Build Forge Fix Pack 19 (8.0.0.19) for 8.0
Rational Build Forge Fix Pack 18 (8.0.0.18) for 8.0
Rational Build Forge Fix Pack 20 (8.0.0.20) for 8.0
Rational Build Forge Fix Pack 21 (8.0.0.21) for 8.0
Rational Build Forge Fix Pack 22 (8.0.0.22) for 8.0

APAR status

• Closed as program error.

Error description

• Restarting management console fails to start correctly.
  
  When you attempt to login to the management console, you will
  get the error:
  Console login failed with
  "BuildForge_Iterator_SocketException[0]: read timeout"
  
  At the same time db.log records the error message:
  CRRBF1388I: 6104: Services: Error Connecting to
  Build Forge Services [BuildForge::Ex::IOException: Read
  Timeout].
  
  This is the known issue of BIRT mentioned on PM54200 which was
  closed without fix.
  Through an escalation, development team reconsidered that this
  issue will be fixed by adopting the new version BIRT in the
  future release.
  

Local fix

• Disable BIRT (refer to the APAR PM54200)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users and environments are affected                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The issue is caused by the deadlock between BIRT class       *
  * loader and catalina app class loader. BuildForge is compiled *
  * with BIRT version 2.3.1. With this version of BIRT, deadlock *
  * happens intermittently on the starting stage of Build Forge  *
  * Service Layer. As a result Build Forge Service Layer doesn't *
  * completely start. When other components, such as Management  *
  * Console, connect to the Build Forge Service Layer, it        *
  * reports "Read Timeout" error. This happens more frequently   *
  * on Windows Operating System than                             *
  * others. In most cases, restarting Build Forge service will   *
  * solve the issue.                                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Build Forge 7.1.3.6                               *
  ****************************************************************
  http://www-01.ibm.com/support/docview.wss?uid=swg1PM54200
  

Problem conclusion

• When Build Forge starts,  Tomcat load the BIRT, there is a
  potential deadlock. BIRT fixed this potential deadlock
  

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:

Fix information

• Fixed component name

  BUILD FORGE SE

• Fixed component ID

  5724S2705

Applicable component levels

• R713 PSY

     UP