PM55326: OSGI ERROR LOGGING IS INSUFFICIENT

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
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

• The current level of logging for OSGi errors does not include
  the package name, forcing users to manually sift through
  .xml files to find the offending bundle.
  
  The change will help to enhance the logging to appear similar to
  the following...
  
  "An error occurred parsing Bundle mybundle_1.0.0"
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Difficult to determine which bundle     *
  *                      fails to deploy.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In a situation where an asset import fails due to a error
  modelling the application (such as invalid syntax in the
  blueprint.xml file), the error message did not report which
  bundle encountered the error. For a large application with
  many bundles, this would require the developer to manually
  check every bundle for a syntax error.
  

Problem conclusion

• The error message when a bundle fails during modelling now
  includes information on the name and version of the bundle in
  the for mybundle_1.0.0. This means the developer may target
  their investigation to just one bundle within an EBA.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.3.  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:

  PM55136

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP