PM65075: VMM READS INCORRECT DOMAIN NAME

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• When you have defined multiple domains on a single server,
  and you access the application domain (say appDomain1) from
  the ISC console and log out of WebSphere Application Server; On
  trying to re-login, virtual member manager (VMM) assumes the
  currentactive domain to be appDomain1 which is incorrect.
  While logging onto to WebSphere Application Server console,
  the VMM domain is the default security domain.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: VMM logins fail in Multi Security       *
  *                      Domain environments (MSD). All          *
  *                      subsequent calls are made on            *
  *                      the previous active domain from ISC.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  VMM is configured with multiple domains in single server,
  and a login is made to application domain and few activities
  are performed. After a while the user logs out of VMM. When
  another user tries to log in, VMM assumes it to be in the
  previous active domain. If fails to login the new user who is
  from the admin(default security) domain.
  

Problem conclusion

• VMM is now corrected and will not cache the active domain name.
  New logins will be performed to the defualt security domain.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.5, and 8.5.0.1.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP