PM70234: BLUEPRINT FEATURES CAN FAIL TO START CORRECTLY WHEN ADDED DYNAMI CALLY.

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

• When adding any of the blueprint-1.0, wab-1.0, or osgi.jpa-1.0
  features after the server has already started some runtime
  bundles may fail to start and FFDC reports will be issued with
  various exceptions having been caused by the following:
  Caused by: java.lang.ClassFormatError: Unexpected error from
  weaving hook.
  ...
  Caused by: java.lang.ClassCircularityError:
  org/apache/aries/proxy/impl/weaving/WovenProxyGenerator
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V8.5       *
  *                  Liberty profile users adding any of the     *
  *                  blueprint-1.0, wab-1.0, or osgi.jpa-1.0     *
  *                  features after the server has already       *
  *                  started.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: FFDC when adding features after         *
  *                      server start containing Caused          *
  *                      by java.lang.ClassFormatError:          *
  *                      Unexpected error from weaving hook      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The classes of runtime bundles required by the blueprint
  features can become corrupted during load when the the
  blueprint feature bundles are started in the wrong order.
  The bytecode enhancement required by the blueprint features
  can operate on itself when the start ordering is incorrect.
  This problem occurs when any of the features that include
  blueprint-1.0 (blueprint-1.0, wab-1.0, osgi.jpa-1.0) are added
  to the server.xml after the server has already started. It is
  required that the com.ibm.ws.eba.proxy.control bundle is
  started before the com.ibm.ws.org.apache.aries.proxy.0.4.1*
  bundle so that the proxy control service is in place before
  the WeavingHook that performs the bytecode modifications.
  

Problem conclusion

• The bundle start order was different on different JVMs when
  features were added dynamically. The start-phase attribute of
  the feature manifest was incorrectly only honoured at server
  start and not being used when features were added dynamically.
  The fix was to always sort the BundleInstallStatus list of
  bundles so that the Provisioner/FeatureManager have consistent
  ordering honouring the start-phase attributes defined by
  features. Additionally the proxy weaving controller
  registration was moved to a BundleActivator instead of a DS
  activate method so as to avoid any unnecessary delay in
  registering the controller.
  
  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