PI40633: A 400 error code displays in the console when loading Admin Center

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When loading Admin Center, the console displays at least one
  400 error code
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the Administrative Center on       *
  *                  Standalone Servers.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: HTTP 400 error code issued in Browser   *
  *                      logs when using Admin Center on a       *
  *                      Standalone Server                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using the AdminCenter on a Standalone Server, HTTP 400
  failures will be displayed in the console of the browser, when
  the AdminCenter attempts to access the ClusterMember mbean.
  These errors are benign, as we're attempting to gather any
  cluster information, if it exists, and the 400 code is just
  indicating that there is no cluster defined.
  

Problem conclusion

• The code now gets the list of available MBeans and only attempts
  to use the ClusterMember mbean if it exists, and prevents the
  400 error from being issued.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.6.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• There is no workaround, because this is a benign failure. The
  process is working regardless of whether the 400 is issued or
  not.
  

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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP