PI26314: VARIOUS SMALL BUG FIXES RELATED TO OSGI APPLICATIONS

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

• This APAR fixes various small bugs related to OSGi
  Applications
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of OSGi Applications on the WebSphere *
  *                  Application Server Liberty Profile          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Various small bug fixes related to OSGi *
  *                      Applications                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1. Rare NullPointerException in
  com.ibm.ws.eba.bundle.repository.internal.BundleRepositoryFactor
  y.updated
  2. No warning given when two Web Application Bundles
  shared the same Web-ContextPath
  3. OSGi Application could
  occasionally fail to start correctly, for lack of an internal
  NamespaceHandler
  4. JNDI lookup of some JMS resources within
  OSGi Applications could fail with an IllegalArgumentException
  5.
  Attempts to install two OSGi Applications with the same symbolic
  name and version fail silenty.
  6. Rare FFDC,
  'com.ibm.ws.webcontainer.webapp.WebAppErrorReport:
  java.lang.IllegalStateException: Module has been uninstalled'
  seen when stopping an OSGi Application containing a Web
  Application Bundle.
  7. Harmless
  'org.osgi.service.coordinator.CoordinationException:
  Coordination has failed' FFDC sometimes seen when uninstalling a
  feature containing a Web Application Bundle
  8.
  NullPointerException seen when quickly removing and re-adding a
  feature containing a Web Application Bundle.
  9. Failure to
  start Blueprint components within an OSGi Application.
  10.
  Possible deadlock while starting an OSGi Application.
  11.
  java.lang.NullPointerException at
  com.ibm.ws.eba.bundle.repository.internal.BundleRepositoryFactor
  y.updateRepositoryConfig() when starting an OSGi Application
  12.
  java.lang.NullPointerException at
  org.eclipse.equinox.coordinator.CoordinationImpl.end(Coordinatio
  nImpl.java:140) when starting an OSGi Application
  

Problem conclusion

• 1. Fixed thread synchronization logic in
  com.ibm.ws.eba.bundle.repository.internal.BundleRepositoryFactor
  y
  2. Warning now issued when two Web Application Bundles share
  the same Web-ContextPath
  3. Fixed a thread safey issue in
  org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImp
  l.java
  4. Fixed an issue with JNDI lookups of JMS resources in
  Apache Aries
  5. A warning message is now issued when an attempt
  is made to install two OSGi Applications with the same symbolic
  name and version.
  6. Fixed an internal issue that could
  occasionally cause an IllegalStateException when stopping a Web
  Application Bundle.
  7, 8: Overhauled the Web Application Bundle
  lifecycle management code.
  9, 10, 11: Improved OSGi Application
  lifecycle management code.
  12. Fixed the coordinator service in
  equinox to handle dereferenced coordination objects
  
  
  
  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

• Ensure that each OSGi Application has a unique symbolic name
  and/or version. Ensure that all Web Application Bundles have
  unique Web-ContextPath entries. All the other problems fixed in
  this APAR can be worked around by restarting the Liberty
  runtime, or by leaving more team between administrative
  operations.
  

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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP