PI18498: CUSTOM WEB MODULE VIRTUAL HOST MAPPINGS LOST ON APP UPDATE WHEN GENERATE DEFAULT BINDINGS IS USED

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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

• 1. configure a custom WebSphere Application Server virtual
  host, other than the default_host
  
  2. in the web console deploy the ear using Detailed
  installation + Generate Default Bindings and map its web module
  to the custom virtual host
  
  3. update the ear using the Detailed installation + Generate
  Default Bindings again
  
  4. The virtual host is reset to default_host and has to be set
  to the desired custom virtual host again.
  

Local fix

• N.A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server versions 8.5 and 8.5.5.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When an installed application is        *
  *                      updated with an application using the   *
  *                      "merge new and existing bindings" and   *
  *                      "Generate Default Bindings" setting in  *
  *                      the administrative console, the         *
  *                      virtual host is not set correctly.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an installed application containing a web module mapping
  to a host other than the default_host is updated with a web
  module that has no virtual host bindings in it, the
  default_host is set as the virtual host for the updated web
  module if the "merge new and existing bindings" and "Generate
  Default Bindings" settings are used during the update in the
  administrative console.
  

Problem conclusion

• The logic has been fixed to use the correct virtual host during
  an application update.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.4.  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

• R850 PSY

     UP