Actually, it’s not the whole Karaf runtime which stop or restart: it’s the shell part.
The problem is that you install camel-stream not aligned in term of jline, and so the karaf shell is refreshed due to jline. Do you have a constraint to use a so old Camel version ??!!! Regards JB > Le 9 mars 2021 à 19:03, Michael Brohl <[email protected]> a écrit : > > Ok, I think I will provide the first example for the difficulties I face. > > I removed the /data folder and restarted Karaf, then: > > karaf@root()> feature:install -v -t camel-blueprint camel-stream > camel-blueprint camel-jms camel-http camel-saxon > Adding features: > camel-http/[2.24.1,2.24.1],camel-jms/[2.24.1,2.24.1],camel-blueprint/[2.24.1,2.24.1],camel-saxon/[2.24.1,2.24.1],camel-stream/[2.24.1,2.24.1] > Changes to perform: > Region: root > Bundles to uninstall: > org.jline.builtins/3.16.0 > org.jline.reader/3.16.0 > org.jline.terminal/3.16.0 > org.jline.terminal-jansi/3.16.0 > Bundles to install: > mvn:javax.servlet/javax.servlet-api/3.1.0 > mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.api/1.0.1 > mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.3.2 > mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.10.3 > mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0 > mvn:org.apache.aries.jmx/org.apache.aries.jmx.blueprint.api/1.2.0 > mvn:org.apache.aries.jmx/org.apache.aries.jmx.blueprint.core/1.2.0 > mvn:org.apache.aries.proxy/org.apache.aries.proxy/1.1.9 > mvn:org.apache.camel/camel-blueprint/2.24.1 > mvn:org.apache.camel/camel-commands-core/2.24.1 > mvn:org.apache.camel/camel-core/2.24.1 > mvn:org.apache.camel/camel-http/2.24.1 > mvn:org.apache.camel/camel-http-common/2.24.1 > mvn:org.apache.camel/camel-jms/2.24.1 > mvn:org.apache.camel/camel-saxon/2.24.1 > mvn:org.apache.camel/camel-stream/2.24.1 > mvn:org.apache.camel.karaf/camel-karaf-commands/2.24.1 > mvn:commons-codec/commons-codec/1.11 > mvn:commons-pool/commons-pool/1.6 > mvn:org.apache.geronimo.specs/geronimo-jms_2.0_spec/1.0-alpha-2 > mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1 > mvn:org.apache.karaf.bundle/org.apache.karaf.bundle.blueprintstate/4.3.1-SNAPSHOT > mvn:org.apache.karaf.deployer/org.apache.karaf.deployer.blueprint/4.3.0 > mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.command/4.3.1-SNAPSHOT > mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.config/4.3.1-SNAPSHOT > mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.modules/4.3.1-SNAPSHOT > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aopalliance/1.0_6 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-httpclient/3.1_7 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.11_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.saxon/9.9.0-2_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/5.2.13.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-beans/5.2.13.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context/5.2.13.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context-support/5.2.13.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/5.2.13.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-expression/5.2.13.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-jms/5.2.13.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-tx/5.2.13.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.xmlresolver/1.2_5 > mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/2.9.0 > mvn:org.jline/jline-builtins/3.19.0 > mvn:org.jline/jline-reader/3.19.0 > mvn:org.jline/jline-terminal/3.19.0 > mvn:org.jline/jline-terminal-jansi/3.19.0 > mvn:org.ow2.asm/asm/9.1 > mvn:org.ow2.asm/asm-commons/9.1 > mvn:org.ow2.asm/asm-tree/9.1 > mvn:org.ow2.asm/asm-analysis/9.1 > mvn:org.ow2.asm/asm-util/9.1 > mvn:org.codehaus.woodstox/stax2-api/3.1.4 > mvn:org.codehaus.woodstox/woodstox-core-asl/4.4.1 > Bundles to refresh: > org.apache.karaf.bundle.core/4.3.0 (Wired to > org.apache.karaf.shell.core/4.3.0 which is being refreshed) > org.apache.karaf.config.core/4.3.0 (Wired to > org.apache.karaf.shell.core/4.3.0 which is being refreshed) > org.apache.karaf.deployer.kar/4.3.0 (Wired to > org.apache.karaf.kar.core/4.3.0 which is being refreshed) > org.apache.karaf.diagnostic.core/4.3.0 (Wired to > org.apache.karaf.shell.core/4.3.0 which is being refreshed) > org.apache.karaf.event/4.3.0 (Wired to org.apache.karaf.shell.core/4.3.0 > which is being refreshed) > org.apache.karaf.features.command/4.3.0 (Wired to > org.jline.terminal/3.16.0 which is being refreshed) > org.apache.karaf.instance.core/4.3.0 (Wired to > org.apache.karaf.features.command/4.3.0 which is being refreshed) > org.apache.karaf.jaas.command/4.3.0 (Should be wired to: > org.apache.karaf.jaas.command/4.3.1.SNAPSHOT (through > [org.apache.karaf.jaas.command/4.3.0] osgi.wiring.package; > filter:="(&(osgi.wiring.package=org.apache.karaf.jaas.command.completers)(version>=4.3.0)(!(version>=5.0.0)))")) > org.apache.karaf.kar.core/4.3.0 (Wired to > org.apache.karaf.features.command/4.3.0 which is being refreshed) > org.apache.karaf.log.core/4.3.0 (Wired to > org.apache.karaf.shell.core/4.3.0 which is being refreshed) > org.apache.karaf.package.core/4.3.0 (Wired to > org.apache.karaf.shell.core/4.3.0 which is being refreshed) > org.apache.karaf.service.core/4.3.0 (Wired to > org.apache.karaf.shell.core/4.3.0 which is being refreshed) > org.apache.karaf.shell.commands/4.3.0 (Wired to org.jline.terminal/3.16.0 > which is being refreshed) > org.apache.karaf.shell.core/4.3.0 (Wired to org.jline.builtins/3.16.0 > which is being refreshed) > org.apache.karaf.shell.ssh/4.3.0 (Wired to > org.apache.karaf.shell.core/4.3.0 which is being refreshed) > org.apache.karaf.system.core/4.3.0 (Wired to > org.apache.karaf.shell.core/4.3.0 which is being refreshed) > org.jline.builtins/3.16.0 (Bundle will be uninstalled) > org.jline.reader/3.16.0 (Bundle will be uninstalled) > org.jline.terminal/3.16.0 (Bundle will be uninstalled) > org.jline.terminal-jansi/3.16.0 (Bundle will be uninstalled) > > When I install without -t -v , Karaf crashes and I'm in my shell: > > karaf@root()> feature:install camel-blueprint camel-stream camel-blueprint > camel-jms camel-http camel-saxon > Error executing command: Method > org/apache/karaf/shell/impl/console/JLineTerminal.getPalette()Lorg/jline/utils/ColorPalette; > is abstract > /Applications/Development/apache-karaf-4.3.0 > > Karaf cannot be startet again: > > /Applications/Development/apache-karaf-4.3.0 ./bin/karaf > __ __ ____ > / //_/____ __________ _/ __/ > / ,< / __ `/ ___/ __ `/ /_ > / /| |/ /_/ / / / /_/ / __/ > /_/ |_|\__,_/_/ \__,_/_/ > > Apache Karaf (4.3.0) > > Hit '<tab>' for a list of available commands > and '[cmd] --help' for help on a specific command. > Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf. > > Error executing command: Method > org/apache/karaf/shell/impl/console/JLineTerminal.getPalette()Lorg/jline/utils/ColorPalette; > is abstract > /Applications/Development/apache-karaf-4.3.0 > > It might have something to do with the jline upgrade performed during the > install. > > Is this the right place or does this warrant a Jira? > > Thanks, > > Michael > > > Am 09.03.21 um 18:46 schrieb Jean-Baptiste Onofre: >> Hi, >> >> Feature:install -v -t will directly output on the terminal (System.out). >> >> When you do feature:install, the resolver output goes into data/karaf.log >> (by default). >> >> Regards >> JB >> >>> Le 9 mars 2021 à 18:22, Michael Brohl <[email protected]> a écrit : >>> >>> Thank you JB, >>> >>> I was hoping there would be some general (and releatively easy) approach or >>> strategy to detect the requirements each feature needs or maybe some >>> compatibility list to study. >>> >>> I will try with your suggestions and come back with more data if this is >>> not successful. >>> >>> The resolver output would be the result of the feature:install dry-run or >>> ist it a specific logfile? >>> >>> Thanks and regards, >>> >>> Michael >>> >>> >>> Am 09.03.21 um 09:17 schrieb Jean-Baptiste Onofre: >>>> Hi Michael, >>>> >>>> It’s hard to say without the log messages. You can use feature:install -t >>>> -v to "simulate" the installation and get some details (like refresh) >>>> before actually installing a feature. >>>> >>>> I bet you have a refresh on hawtio caused by ActiveMQ. >>>> >>>> You can disable auto refresh to avoid such issue, or change the >>>> installation "order" to avoid the refresh. >>>> >>>> Can you please send the resolver output ? >>>> >>>> Thanks, >>>> Regards >>>> JB >>>> >>>>> Le 9 mars 2021 à 09:10, Michael Brohl <[email protected]> a écrit : >>>>> >>>>> Hi, >>>>> >>>>> I am struggling with a fresh setup on Karaf 4.3.0, trying to install >>>>> Apache Camel, ActiveMQ and Hawt.io in current versions. >>>>> >>>>> Depending on the order of installation, I get different errors leaving me >>>>> clueless what to do with errors like >>>>> >>>>> Singleton conflict. Unresolved requirements: [] >>>>> >>>>> Installing latest Hawt.io for example works and I can login to the web >>>>> UI. After installing ActiveMQ and getting errors, I am not able to login >>>>> to Hawt.io anymore. >>>>> >>>>> Before I start asking for help for specific errors: is there a guide or >>>>> strategy how to find out the correct versions of features/bundles, >>>>> necessary repos to add and features/bundles to install as prerequisites >>>>> of the feature/bundle to install? >>>>> >>>>> Thanks for any hint, >>>>> >>>>> Michael >>>>> >>>>>
