During the tests of Apache Karaf 4.0.2 I found a serious issue in blueprint.
See:
https://issues.apache.org/jira/browse/ARIES-1430
It is related to the fact that Aries JPA creates services references in
a ComponentDefinitionRegistryProcessor.
The timeout for service references is reset as soon as the bundle leaves
the Graceperiod. If a service reference is created later then it is not
reset anymore.
So the bundle runs into the timeout even if the services it waits for
are then already present.
The workaround I did was to check if we are actually waiting for
services when the timeout occurs. This is only a workaround though. The
proper fix would be to keep / or put back the bundle in Graceperiod
until all service references are available.
As the current situation without the workaround makes jpa unusable I
think we should release as is to provide a quick solution. Still we
should check if we can provide a better solution.
WDYT?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
