[
https://issues.apache.org/jira/browse/KARAF-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150604#comment-17150604
]
Amichai Rothman commented on KARAF-6776:
----------------------------------------
Trying to dig deeper, I think it's indeed related to the configadmin -
ConfigurationManager.canReceive returns false since the bundle location
(scheduler) does not match the given location (fileinstall) so the
configuration is never passed on to the service. I'm not familiar with the
location mechanism in CM, but something is off in how
karaf/fileinstall/configadmin are used together.
Also the fact that it's a race condition points to a problem. Since this seems
like a configuration update issue, it may cause problems in other
bundles/features as well, and not just limited to the scheduler, but any bundle
that has a config file in /etc.
> scheduler doesn't work in featuresBoot
> --------------------------------------
>
> Key: KARAF-6776
> URL: https://issues.apache.org/jira/browse/KARAF-6776
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.9
> Environment: Oracle JDK 1.8.0_202 64-bit on Ubuntu 18.04.
> Reporter: Amichai Rothman
> Priority: Major
>
> When the karaf scheduler feature is added to the featuresBoot configuration
> so that it will be installed automatically on startup, there is a race
> condition that causes it not to work around half of the time.
> Steps to recreate:
> # Extract stock apache-karaf-4.2.9.tar.gz.
> # Edit etc/org.apache.karaf.features.cfg, adding ",scheduler" to the end of
> the featuresBoot config option.
> # Start karaf. About half of the time you'll find that there are no
> scheduler shell commands available (that's the quickest check, see below for
> details). If it works ok, delete the karaf folder and repeat steps 1-3 again
> until you see the issue (in my case it happens about half of the time).
> I'm not sure what the problem is yet. The feature is installed successfully
> and the bundle status is Active, but it just doesn't work. The scheduler
> shell commands are unrecognized. There are no errors in the logs, but
> debug-level logs are missing the quartz initialization messages. If you add a
> test bundle that registers a scheduler job service (whiteboard), it doesn't
> get executed.
> I suspect the problem is related to config admin, maybe it gets initialized
> with an empty config and the updates from the default config file aren't
> applied properly or something like that... I'm not sure, it's more of a guess.
> I have not encountered this issue in 4.2.8 or any of the previous versions,
> the scheduler always just worked using the same configuration. It's a blocker
> for our upgrade :-/
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
