Kafka Minions with JMS disabled log errors loading JMS bundles
Description
29.0.5 Minion using Kafka for Sink/RPC/Twin
Roughly five minutes after startup completes:
2022-01-20T12:02:49,910 | ERROR | Blueprint Extender: 3 | BlueprintContainerImpl | 26 - org.apache.aries.blueprint.core - 1.10.3 | Unable to start container for blueprint bundle org.opennms.core.ipc.rpc.jms-impl/29.0.5 due to unresolved dependencies [(&(alias=opennms.broker)(objectClass=org.apache.camel.Component))]
java.util.concurrent.TimeoutException: null
at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:393) [!/:1.10.3]
at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45) [!/:1.10.3]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
2022-01-20T12:02:50,402 | ERROR | Blueprint Extender: 2 | BlueprintContainerImpl | 26 - org.apache.aries.blueprint.core - 1.10.3 | Unable to start container for blueprint bundle org.opennms.core.ipc.sink.camel.client/29.0.5 due to unresolved dependencies [(&(alias=opennms.broker)(objectClass=org.apache.camel.Component))]
java.util.concurrent.TimeoutException: null
at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:393) [!/:1.10.3]
at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45) [!/:1.10.3]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
2022-01-20T12:02:50,430 | ERROR | Blueprint Extender: 3 | BlueprintContainerImpl | 26 - org.apache.aries.blueprint.core - 1.10.3 | Unable to start container for blueprint bundle org.opennms.core.ipc.twin.jms.subscriber/29.0.5 due to unresolved dependencies [(&(alias=opennms.broker)(objectClass=org.apache.camel.Component))]
java.util.concurrent.TimeoutException: null
at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:393) [!/:1.10.3]
at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45) [!/:1.10.3]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
to featuresBoot.d/amq.boot, these exceptions are no longer logged and bundle:diag no longer shows timeout errors for these bundles.
This was not required in previous release versions (could not repro on 29.0.4), but I am not sure if this should be a documentation fix, or if this should be addressed by engineering.
29.0.5 Minion using Kafka for Sink/RPC/Twin
Roughly five minutes after startup completes:
2022-01-20T12:02:49,910 | ERROR | Blueprint Extender: 3 | BlueprintContainerImpl | 26 - org.apache.aries.blueprint.core - 1.10.3 | Unable to start container for blueprint bundle org.opennms.core.ipc.rpc.jms-impl/29.0.5 due to unresolved dependencies [(&(alias=opennms.broker)(objectClass=org.apache.camel.Component))] java.util.concurrent.TimeoutException: null at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:393) [!/:1.10.3] at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45) [!/:1.10.3] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] at java.lang.Thread.run(Thread.java:829) [?:?] 2022-01-20T12:02:50,402 | ERROR | Blueprint Extender: 2 | BlueprintContainerImpl | 26 - org.apache.aries.blueprint.core - 1.10.3 | Unable to start container for blueprint bundle org.opennms.core.ipc.sink.camel.client/29.0.5 due to unresolved dependencies [(&(alias=opennms.broker)(objectClass=org.apache.camel.Component))] java.util.concurrent.TimeoutException: null at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:393) [!/:1.10.3] at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45) [!/:1.10.3] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] at java.lang.Thread.run(Thread.java:829) [?:?] 2022-01-20T12:02:50,430 | ERROR | Blueprint Extender: 3 | BlueprintContainerImpl | 26 - org.apache.aries.blueprint.core - 1.10.3 | Unable to start container for blueprint bundle org.opennms.core.ipc.twin.jms.subscriber/29.0.5 due to unresolved dependencies [(&(alias=opennms.broker)(objectClass=org.apache.camel.Component))] java.util.concurrent.TimeoutException: null at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:393) [!/:1.10.3] at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45) [!/:1.10.3] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] at java.lang.Thread.run(Thread.java:829) [?:?]Similar errors are visible via bundle:diag
featuresBoot.d/amq.boot contains:
[root@29minion etc]# cat featuresBoot.d/amq.boot !minion-jms !opennms-core-ipc-rpc-jms !opennms-core-ipc-sink-camel !opennms-core-ipc-twin-jmsIf I add:
!opennms-core-ipc-jmsto featuresBoot.d/amq.boot, these exceptions are no longer logged and bundle:diag no longer shows timeout errors for these bundles.
This was not required in previous release versions (could not repro on 29.0.4), but I am not sure if this should be a documentation fix, or if this should be addressed by engineering.