PM65673: AN OSGI APPLICATION USING A BUNDLE FROM A CONFIGURED BUNDLE REPO SITORY OCCASIONALLY FAILS TO RESOLVE.

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2

APAR status

• Closed as program error.

Error description

• Sometimes an OSGi application requiring bundles that are
  located in a configured bundle repository fail to resolve and
  start even when the bundle repository is correctly configured
  with the necessary bundle.
  
  The following error messages are displayed in the console.log.
  
  CWWKZ0304E: An exception was generated when trying to resolve
  the contents of the application <application name>.
  
  CWWKZ0012I: The application <application name> was not started.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile with an OSGi         *
  *                  application and a bundle repository.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: A resolver exception could occur        *
  *                      because the bundle repository           *
  *                      metadata XML is incorrect.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the CWWKZ0304E message is seen and the bundle repository is
  correctly configured and includes the correct bundle then the
  absence of the metadata of the needed bundle from the <server
  home>/workspace/platform/bundleRepositories/*.xml files is a
  good indication of this issue.
  Within the code the indicator of this issue is the return of
  an empty set of files from the call to fileset.getFileset() in
  the BundleRepositoryImpl despite the bundle repository already
  being configured.
  

Problem conclusion

• There was a timing issue where the bundle repository
  configuration could call for the list of files from a fileset
  before that fileset had been properly initialized by the file
  monitor. This resulted in an empty set of files being
  returned. To resolve this issue the call to get in the
  implementation of Fileset was made blocking on the
  initComplete notification from the file monitor so that the
  set of files is not returned until the fileset has been
  initialized.
  
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP