camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Siepert (JIRA)" <>
Subject [jira] [Commented] (CAMEL-9313) CamelBlueprintTestSupport - timing problems with property placeholder
Date Tue, 01 Dec 2015 08:06:10 GMT


Andreas Siepert commented on CAMEL-9313:

Hi [~gzres] and sorry for the late response of mine. I was just writing the comment as yours
came in...

I mentioned a second problem I attached a patch ({{camel-9313.patch}}) based on git branch
{{camel-2.15.5}} which addresses the second problem and makes it visible. The problem is that
the string of the propertyplaceholder is taken as the value which works fine for strings but
not for int for example. Please have a look.

2015-12-01 08:57:37,415 [int Extender: 1] ERROR BlueprintContainerImpl         - Unable to
start blueprint container for bundle ConfigAdminLoadConfigurationFileTest/1.0.0
org.osgi.service.blueprint.container.ComponentDefinitionException: Error setting property:
PropertyDescriptor <name: counter, getter: class org.apache.camel.test.blueprint.MyCoolBean.getCounter(),
setter: [class org.apache.camel.test.blueprint.MyCoolBean.setCounter(int)]
	at org.apache.aries.blueprint.container.BeanRecipe.setProperty(
	at org.apache.aries.blueprint.container.BeanRecipe.setProperties(
	at org.apache.aries.blueprint.container.BeanRecipe.setProperties(
	at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(
	at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(
	at org.apache.aries.blueprint.di.AbstractRecipe$
	at org.apache.aries.blueprint.di.AbstractRecipe.create(
	at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(
	at org.apache.aries.blueprint.container.BlueprintRepository.createAll(
	at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(
	at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(
	at java.util.concurrent.Executors$
	at java.util.concurrent.Executors$
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
	at java.util.concurrent.ScheduledThreadPoolExecutor$
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.lang.NumberFormatException: For input string: "${counter}"
	at java.lang.NumberFormatException.forInputString(
	at java.lang.Integer.parseInt(
	at java.lang.Integer.valueOf(
	at org.apache.aries.blueprint.container.AggregateConverter.convertFromString(
	at org.apache.aries.blueprint.container.AggregateConverter.convert(
	at org.apache.aries.blueprint.container.BlueprintRepository.convert(
	at org.apache.aries.blueprint.utils.ReflectionUtils$PropertyDescriptor.convert(
	at org.apache.aries.blueprint.utils.ReflectionUtils$MethodPropertyDescriptor.internalSet(
	at org.apache.aries.blueprint.utils.ReflectionUtils$PropertyDescriptor.set(
	at org.apache.aries.blueprint.container.BeanRecipe.setProperty(
	... 23 more

> CamelBlueprintTestSupport - timing problems with property placeholder
> ---------------------------------------------------------------------
>                 Key: CAMEL-9313
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint
>    Affects Versions: 2.15.4
>            Reporter: Andreas Siepert
>            Assignee: Grzegorz Grzybek
>             Fix For: 2.16.2, 2.15.5, 2.17.0
>         Attachments: camel-9313.patch
> The bugfix CAMEL-8948 seems to make older timing problems related to property-placeholders
> To reproduce the problem i changed the test 
> org.apache.camel.test.blueprint.ConfigAdminNoReloadLoadConfigurationFileTest 
> from the component camel-test-blueprint a bit, respectively the context 
> "org/apache/camel/test/blueprint/configadmin-no-reload-loadfile.xml": 
> I added the trace Attribute to the camelContext:
> {code:xml}
> <camelContext xmlns="" trace="{{tracing}}">

> {code}
> and added also the property to the etc/stuff.cfg 
> {code}
> tracing=true 
> {code}
> Until 2.15.2 this worked fine. From 2.15.3 on the property cannot be 
> replaced any more.
> But, if setting a breakpoint in {{CamelBlueprintTestSupport#createBundleContext}} at
loadConfigAdminConfigurationFile() (Line 123 in 2.15.4) - the error occurs even in older versions
like 2.14 - so the timing problem seems to be there for a while but did not occur because
the loading of the configAdminFile seems to be faster than the event handling during service
registration triggered by the code some lines above.
> The issue can also be reproduced when replacing a property's String type 
> with int in the MyCoolBean class and setting its value by using the 
> placeholder like before but with an int value of course. The test run shows 
> that the placeholder "${..\}" will not be replaced and leads to a 
> NumberfFormatException. 
> The production code that is under test works fine in karaf. 

This message was sent by Atlassian JIRA

View raw message