You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by "BURN, James" <Ja...@oup.com> on 2014/03/21 14:32:41 UTC

"Configuration bound to bundle" error

Hello

I'm testing apache-servicemix-4.5.3 on Linux Redhat.

>From a fresh install of ServiceMix I have a blueprint camel route which refers to a list of variables from etc/variablelist.cfg using the <cm:property-placeholder persistent-id="variablelist"/>

This works fine and I can substitute the variables through ${properties:variablename} to messages in my route.

However on starting a second route (bundle no 210) which accesses the variable list using the same <cm:property-placeholder persistent-id="variablelist"/> I get the following error:

2014-03-21 10:39:54,344 | ERROR | pdate: pid=test) | configadmin                      | 5 - org.apache.felix.configadmin - 1.2.8 | Cannot use configuration variablelist for [org.osgi.service.cm.ManagedService, id=434, bundle=210]: Configuration bound to bundle blueprint:file:/opt/apache-servicemix-4.5.3/deploy/testTopTail.xml

It doesn't seem to affect the service - the route/variable substitution still works as expected. But the error is concerning!
Could this be an issue with felix: https://issues.apache.org/jira/browse/SMX4NMR-289

Should I worry about this? Apparently my colleague who has been doing the same work on a Windows server hasn't been getting any errors - this puzzles me even more.

Any thoughts/help will be well appreciated.

Thanks

James





Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.

RE: "Configuration bound to bundle" error

Posted by "BURN, James" <Ja...@oup.com>.
ServiceMix folks, a quick update before I finish today. This error appears when I'm using 2 blueprint DSLs accessing the variables file, as per:

<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0	http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd">

    <camelContext xmlns="http://camel.apache.org/schema/blueprint" id="test_transform"
        xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0">
        <cm:property-placeholder persistent-id="variablelist"/>    
        <route>
            <from uri="file:camel/input?delete=true"/>
            <transform>
                <simple>${properties:variablename}&lt;Root&gt;&lt;Record&gt;&lt;![CDATA[${in.body}]]&gt;&lt;/Record&gt;&lt;/Root&gt;</simple>
            </transform>
            <to uri="file:camel/testoutput"/>       
        </route>
    </camelContext>	
</blueprint>

When I have the equivalent using multiple Spring DSLs accessing the variables file, as per:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans 
    http://www.springframework.org/schema/beans/spring-beans.xsd
    http://camel.apache.org/schema/spring 
    http://camel.apache.org/schema/spring/camel-spring.xsd">
    <camelContext xmlns="http://camel.apache.org/schema/spring" id="test_transformSpr">
        <propertyPlaceholder location="file:etc/test.cfg" id="variablelist"/>
        <route>
            <from uri="file:camel/input?delete=true"/>
            <transform>
                <simple>{{variablename}}&lt;Root&gt;&lt;Record&gt;&lt;![CDATA[${in.body}]]&gt;&lt;/Record&gt;&lt;/Root&gt;</simple>
            </transform>
            <to uri="file:camel/testoutput"/>       
        </route>
    </camelContext>	
</beans>

all works fine... I'm puzzled. 

Cheers

James



-----Original Message-----
From: BURN, James [mailto:James.Burn@oup.com] 
Sent: 21 March 2014 13:33
To: users@servicemix.apache.org
Subject: "Configuration bound to bundle" error

Hello

I'm testing apache-servicemix-4.5.3 on Linux Redhat.

>From a fresh install of ServiceMix I have a blueprint camel route which refers to a list of variables from etc/variablelist.cfg using the <cm:property-placeholder persistent-id="variablelist"/>

This works fine and I can substitute the variables through ${properties:variablename} to messages in my route.

However on starting a second route (bundle no 210) which accesses the variable list using the same <cm:property-placeholder persistent-id="variablelist"/> I get the following error:

2014-03-21 10:39:54,344 | ERROR | pdate: pid=test) | configadmin                      | 5 - org.apache.felix.configadmin - 1.2.8 | Cannot use configuration variablelist for [org.osgi.service.cm.ManagedService, id=434, bundle=210]: Configuration bound to bundle blueprint:file:/opt/apache-servicemix-4.5.3/deploy/testTopTail.xml

It doesn't seem to affect the service - the route/variable substitution still works as expected. But the error is concerning!
Could this be an issue with felix: https://issues.apache.org/jira/browse/SMX4NMR-289

Should I worry about this? Apparently my colleague who has been doing the same work on a Windows server hasn't been getting any errors - this puzzles me even more.

Any thoughts/help will be well appreciated.

Thanks

James


Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.