PK83337: Wrong WSDL file is returned if there are multiple applications deployed with the same display-name

PM08761; 6.1.0.31: A WSWS7054E error occurs while starting a JAX-WS application.

APAR status

• Closed as program error.

Error description

• In cases where there are multiple applications deployed to
  a WebSphere Application Server and the applications have
  the same application display-name as defined in the
  application.xml, attempting to retrieve the WSDL file
  associated with one of the applications may result in the wrong
  WSDL file being returned.
  

Local fix

• Stop WebSphere Application Server
  Delete the old wsdl from the wscache
  Start WebSphere Application Server
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of       *
  *                  Feature Pack for Web Services               *
  ****************************************************************
  * PROBLEM DESCRIPTION: The wrong WSDL file may be returned     *
  *                      in cases where multiple applications    *
  *                      are deployed with the same              *
  *                      application display-name.               *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack containing this APAR.    *
  ****************************************************************
  The WebSphere Application Server runtime uses a
  cache to store the WSDL associated with an application.
  The cache name uses application display-name in it's path.
  
  An application display-name is not guaranteed to be unique
  among applications.  The result is that if two applications
  with the same display-name are installed, there is only one
  WSDL cache associated with both applications.  Therefore, the
  wrong WSDL file will be returned for one of the applications.
  
  The invalid WSDL file will cause unpredictable exceptions in
  the user's application.
  

Problem conclusion

• The WebSphere Application Server runtime has been changed to
  ensure that each application has a unique cache. The cache
  naming convention now uses the application name, rather than
  the display name.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.29.  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:

  PK91951 PK92803

Fix information

• Fixed component name

  WEBSERVIC FEATU

• Fixed component ID

  5724J0850

Applicable component levels

• R610 PSY

     UP