PI31313: In an HA Dmanager configuration, registering a Dmanager to a Job Manager can select the wrong Dmanager instance.

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

• After implementing HA for Deployment Manager as described in
  http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.i
  bm.websphere.nd.doc/ae/twve_xdsoconfig.html?lang=en,
  registering the active Deployment Manager to a Job Manager
  incorrectly specifies the host and port of the backup
  Deployment Manager.
  

Local fix

• test ifix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Network Deployment edition with a    *
  *                  High Availability (HA) Deployment Manager   *
  *                  configuration.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Registering a Deployment Manager to a   *
  *                      Job Manager can select the wrong        *
  *                      Job Manager instance.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Job Managers can be created as separate profiles. Deployment
  Managers also contain the Job Manager functionality.
  Using Job Manager to run jobs on a Deployment Manager
  first requires registering the Deployment Manager with a Job
  Manager.  Since the Deployment Manager contains a Job Manager,
  one way to do that is to  register the Deployment Manager with
  itself, instead of a separate Job Manager profile.
  When a Deployment Manager is registered with itself, and it is
  in an HA configuration, the host and port information of the
  backup Deployment Manager can be stored instead of the
  information from the active Deployment Manager.  As a result,
  the Deployment Manager cannot contact the Job Manager.
  

Problem conclusion

• The code is revised so that when the Deployment manager is
  registered with itself, it will select the HA Deployment
  Manager instance that is active when registration is performed.
  
  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

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP