Closed dannylamb closed 7 years ago
@dannylamb I have seen this issue with fcrepo-camel-toolbox
(so it's not really an API-X issue per se). The basic problem is that when the configuration for fcrepo-service-activemq
is changed, the service doesn't restart properly -- you have to manually stop/start the service. I think this is part of a larger issue with ActiveMQ 5.14.x and Camel 2.18.x, and so I have basically been ignoring it until AMQ/5.15 is released. The easy workaround is to put the customized org.fcrepo.camel.service.activemq.cfg
in place before starting the Karaf container.
@acoburn Thx. So helpful, as always. I'll see what I can do in claw_vagrant
to make it work until the appropriate upstream fixes land.
Closing for now since it's not really an api-x issue.
Apologies in advance for the wall of text on this one.
I'm working on adding API-X to CLAW's vagrant environment and am running into an issue. Before installing the
fcrepo-api-x
feature, mybundle:list
is all active.After
feature:install fcrepo-api-x
, I have:In my logs, I get this first:
Followed eventually by this:
And then eventually a cascade of other fails. Seems like the appropriate camel-jms feature is deployed for 2.17.3, which is the dependency the activemq component is trying to load. I'm stuck scratching my head on this one. Maybe this is a fcrepo-camel-toolbox compatability issue? Just seems strange that
fcrepo-service-activemq
fails when it's not referenced by api-x at all.