PI37163: BUILD FORGE 7.1.3.X CONSOLE WEB UI UNAVAILABLE DUE TO "READ_TIMEOUT" UNDER SOLARIS WAS INTEGRATION

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

• When installing Build Forge 7.1.3.x under Solaris and integrated
  with WebSphere Application Server (WAS), attempts to access the
  console web UI hangs until a timeout error (ie: read_timeout) is
  produced.
  
  Steps to reproduce:
  
  - Configure Build Forge 7.1.3.5-iFix1 under Solaris 10 SRARC
  system with WebSphere Application Server 8.0.0.9.
  - Start up WebSphere Application Server and Build Forge
  appropriately.
  - Attempt to access the Build Forge web console UI using the web
  server based address.
  
  Expected result:
  
  - Users are redirected to the Build Forge logic page hosted
  under WebSphere Application Server running the Build Forge
  application (rbf-services.war).
  - After authenticating their username, users are redirected to
  the Build Forge web console.
  
  
  Actual result:
  
  - After several minutes, user will encounter a timeout error
  (read_timeout) and are never redirected to the login page.
  - If users attempt to access login page directly and
  authenticate their user name, the redirection to the Build Forge
  console UI will timeout.
  

Local fix

• Start Build Forge using the provided Tomcat Application Server
  under Solaris installations.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * BUILD FORGE 7.1.3.X CONSOLE WEB UI UNAVAILABLE DUE TO        *
  * "READ_TIMEOUT" UNDER SOLARIS WAS INTEGRATION                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The issue was fixed in Build Forge 8.0.0.3 release
  

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 EE

• Fixed component ID

  5724S2702

Applicable component levels

• R713 PSN

     UP