Bundles are in state Waiting after restart of service bundle in Fabric

Issue

• Assume the following constellation: We have a blueprint bundle A that exports a JMS connectin factory in the OSGi service registry which is in turned used by bundles B and C to listen to specific queues via Camel's JMS component:

• Bundle A:

<service ref="pooledConnectionFactory" interface="javax.jms.ConnectionFactory">
        <service-properties>
            <entry key="broker" value="smw"></entry>
        </service-properties>
    </service>

• Bundles B & C:

  <reference id="mqConnectionFactory" interface="javax.jms.ConnectionFactory" filter="(broker=smw)"></reference>
  ...
  <bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">
      <property name="acceptMessagesWhileStopping" value="true"></property>
      <property name="cacheLevelName" value="CACHE_NONE"></property>
      <property name="connectionFactory" ref="mqConnectionFactory"></property>
      <property name="maxMessagesPerTask" value="10"></property>
  </bean>
  

• After a restart of bundle A e.g. by changing its configuration, the bundles B and C are forever in state Waiting. What's wrong?