Uploaded image for project: 'CXF Distributed OSGi'
  1. CXF Distributed OSGi
  2. DOSGI-160

RemoteServiceAdmin shuts itself down during startup

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.5.0
    • Component/s: common
    • Labels:
      None
    • Environment:

      Oracle JDK 1.7.0_17, Karaf 2.3.1, DOSGi 1.4.0 (installed from Karaf feature)

    • Estimated Complexity:
      Unknown

      Description

      Every once in a while (quite often) the service export fails. Looking through the logs, I found the message "RemoteServiceAdmin Implementation is shutting down now" - during Karaf startup! It appears that the RSA is started, services exported properly etc., but then it suddenly commits suicide a few moments later with no other error or indication of who/what initiated the shutdown or why.

      Further investigation shows the DSW Activator is getting a ConfigurationAdmin updated event with null configuration (according to the OSGi specs, the callback is guaranteed to be called - either with an existing configuration or with null if none is available). The current implementation of the callback stops the bundle, shutting down the service and printing the above log message, but when the configuration is null it does not start it back up, resulting in the observed behaviour.

      There's also a race condition in the class since from my understanding of the specs the updated callback is called asynchronously from a separate thread, and since it stops and possibly starts the bundle, this might cause the start/stop methods to be run concurrently and more than once (the bundle lifecycle start/stop along with the update-triggered start/stop).

      Finally, while debugging and attempting to fix this I came across a third related issue - when the bundle is indeed started up again in the updated method (e.g. if removing the null check or if a configuration is available), the start method then re-registers the ManagedService, which causes the updated method to be called again, which restarts the bundle again, etc. - in an infinite loop. In practice I saw the server hang with 100% CPU usage indefinitely, and in a later session with a debugger the loop was confirmed.

      Attached is a fix for the 3 related issues - when applied together everything seems to work as expected. I'm new to this project, so please correct anything I've missed.

        Attachments

          Activity

            People

            • Assignee:
              cschneider Christian Schneider
              Reporter:
              amichai Amichai Rothman
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: