Uploaded image for project: 'Red Hat Build of Apache Camel for Quarkus'
  1. Red Hat Build of Apache Camel for Quarkus
  2. CEQ-12204

BindToRegistry is being called twice with first call with uninitialized injected values for quarkus-bom 3.27.0.redhat-00002

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Moderate
    • 0
    • +

      When using BindToRegistry it is calling twice with the first time having uninitialized injected values for quarkus-bom 3.27.0.redhat-00002.This is a breaking change as it causes an exception when the config is null instead of populated. I have attached an example that counts the number of calls to the bind function. Below is what occurs for version 3.27.0.redhat-00002 of quarkus-bom:

      2025-12-01 11:40:01,631 INFO  [tes.TestRoute] (Quarkus Main Thread) Binding TestProcess instance number: 1
2025-12-01 11:40:01,631 INFO  [tes.TestRoute] (Quarkus Main Thread) Config is null
2025-12-01 11:40:01,815 INFO  [org.apa.cam.qua.cor.CamelBootstrapRecorder] (Quarkus Main Thread) Apache Camel Quarkus 3.27.0.redhat-00002 is starting
2025-12-01 11:40:01,818 INFO  [org.apa.cam.mai.MainSupport] (Quarkus Main Thread) Apache Camel (Main) 4.14.0.redhat-00009 is starting
2025-12-01 11:40:01,834 INFO  [org.apa.cam.mai.ProfileConfigurer] (Quarkus Main Thread) The application is starting with profile: dev
2025-12-01 11:40:01,873 INFO  [tes.TestRoute] (Quarkus Main Thread) Binding TestProcess instance number: 2
2025-12-01 11:40:01,874 INFO  [tes.TestRoute] (Quarkus Main Thread) Config someProperty: default-value

      Below is what occurs for version 3.20.3.redhat-00006 of quarkus-bom (This is the expected behaviour):

      2025-12-01 11:32:11,373 INFO  [org.apa.cam.mai.MainSupport] (Quarkus Main Thread) Apache Camel (Main) 4.10.3.redhat-00030 is starting
2025-12-01 11:32:11,380 INFO  [org.apa.cam.mai.ProfileConfigurer] (Quarkus Main Thread) The application is starting with profile: dev
2025-12-01 11:32:11,425 INFO  [tes.TestRoute] (Quarkus Main Thread) Binding TestProcess instance number: 1
2025-12-01 11:32:11,425 INFO  [tes.TestRoute] (Quarkus Main Thread) Config someProperty: default-value

          1.
          		 Provide a Fix for BindToRegistry is being called twice with first call with uninitialized injected values for quarkus-bom 3.27.0.redhat-00002 Sub-task Closed Undefined James Netherton
          2.
          		 Productization BindToRegistry is being called twice with first call with uninitialized injected values for quarkus-bom 3.27.0.redhat-00002 Sub-task To Do Undefined Unassigned
          3.
          		 Automate test for BindToRegistry is being called twice with first call with uninitialized injected values for quarkus-bom 3.27.0.redhat-00002 Sub-task Closed Undefined Viliam Kasala

              jnethert@redhat.com James Netherton
              rhn-support-xiwu Xiaohui Wu
              Viliam Kasala Viliam Kasala
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: