Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-10513

Start BlueprintCamelContext on BlueprintEvent.CREATED

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.19.0
    • Component/s: camel-blueprint
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      Currently the BlueprintCamelContext starts when the BlueprintContainer OSGi service is registered. Because of this, the startup of the BlueprintCamelContext can effect the startup of the BlueprintContainer itself, which can lead to infinite loops and make issues more difficult to resolve.

      The BlueprintCamelContext should be changed to start on the BlueprintEvent.CREATED, which is sent after the BlueprintContainer is fully initialized.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. CAMEL-10602 camel:run with simple blueprint project failed "waiting for BlueprintContainer" although the route is active

          • Major - Major loss of function.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CAMEL-12980 Bundle in 'Active' State but Camel Context not initialized

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          links to

          Web Link GitHub Pull Request #1297

            Activity

              People

              • Assignee:
                hqstevenson Quinn Stevenson
                Reporter:
                hqstevenson Quinn Stevenson
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: