[jira] [Commented] (KARAF-7843) It would be nice if the spifly feature was on a start-level other than the default
[ https://issues.apache.org/jira/browse/KARAF-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860644#comment-17860644 ] Steinar Bang commented on KARAF-7843: - I have created a pull request setting the spifly.dynamic.bundle start level to 20: https://github.com/apache/karaf/pull/1852 > It would be nice if the spifly feature was on a start-level other than the > default > -- > > Key: KARAF-7843 > URL: https://issues.apache.org/jira/browse/KARAF-7843 > Project: Karaf > Issue Type: Bug >Reporter: Steinar Bang >Priority: Major > > [Apache Aries SPI > Fly|https://aries.apache.org/documentation/modules/spi-fly.html] helps > translating SPI services into OSGi services. > SPI Fly looks for OSGi manifest headers and then tries > to satisfy them with services found by scanning for > headers. > The Liquibase database migration tool is built around SPI services. > As an OSGi bundle it utilizes SPI Fly to spin up its SPI services by adding > both a [ for the > services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L252] > as well as a [ for the same > services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L217] > in the liquibase-core manifest file. > But all of the SPI services of liquibase needs to be running before liquibase > is actually used and there is no way to know that all the required services > have been started. > So to make liquibase available on the default start level 80 (where e.g. > jdbc-config is running), liquibase and SPI Fly both has to be started on a > lower start level (e.g. 40). > And the built-in spifly feature of karaf starts SPI Fly on start level 80 > which is much too late for liquibase to make use of it (all SPI services will > be started, but much too late). > So it would be good to have the spifly feature start the spifly bundle at a > lower start level than the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KARAF-7843) It would be nice if the spifly feature was on a start-level other than the default
[ https://issues.apache.org/jira/browse/KARAF-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860639#comment-17860639 ] Steinar Bang commented on KARAF-7843: - When using [Dynamic Weaving Bundle|https://aries.apache.org/documentation/modules/spi-fly.html#_dynamic_weaving_bundle] the SPI Fly documentation recommends that it is started on a low start level, because the SPI Fly bundle needs to be active before all bundles it should start SPI services in. > It would be nice if the spifly feature was on a start-level other than the > default > -- > > Key: KARAF-7843 > URL: https://issues.apache.org/jira/browse/KARAF-7843 > Project: Karaf > Issue Type: Bug >Reporter: Steinar Bang >Priority: Major > > [Apache Aries SPI > Fly|https://aries.apache.org/documentation/modules/spi-fly.html] helps > translating SPI services into OSGi services. > SPI Fly looks for OSGi manifest headers and then tries > to satisfy them with services found by scanning for > headers. > The Liquibase database migration tool is built around SPI services. > As an OSGi bundle it utilizes SPI Fly to spin up its SPI services by adding > both a [ for the > services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L252] > as well as a [ for the same > services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L217] > in the liquibase-core manifest file. > But all of the SPI services of liquibase needs to be running before liquibase > is actually used and there is no way to know that all the required services > have been started. > So to make liquibase available on the default start level 80 (where e.g. > jdbc-config is running), liquibase and SPI Fly both has to be started on a > lower start level (e.g. 40). > And the built-in spifly feature of karaf starts SPI Fly on start level 80 > which is much too late for liquibase to make use of it (all SPI services will > be started, but much too late). > So it would be good to have the spifly feature start the spifly bundle at a > lower start level than the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KARAF-7843) It would be nice if the spifly feature was on a start-level other than the default
[ https://issues.apache.org/jira/browse/KARAF-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steinar Bang updated KARAF-7843: Description: [Apache Aries SPI Fly|https://aries.apache.org/documentation/modules/spi-fly.html] helps translating SPI services into OSGi services. SPI Fly looks for OSGi manifest headers and then tries to satisfy them with services found by scanning for headers. The Liquibase database migration tool is built around SPI services. As an OSGi bundle it utilizes SPI Fly to spin up its SPI services by adding both a [ for the services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L252] as well as a [ for the same services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L217] in the liquibase-core manifest file. But all of the SPI services of liquibase needs to be running before liquibase is actually used and there is no way to know that all the required services have been started. So to make liquibase available on the default start level 80 (where e.g. jdbc-config is running), liquibase and SPI Fly both has to be started on a lower start level (e.g. 40). And the built-in spifly feature of karaf starts SPI Fly on start level 80 which is much too late for liquibase to make use of it (all SPI services will be started, but much too late). So it would be good to have the spifly feature start the spifly bundle at a lower start level than the default. was: [Apache Aries SPI Fly|https://aries.apache.org/documentation/modules/spi-fly.html] helps translating SPI services into OSGi services. SPI Fly looks for OSGi manifest headers and then tries to satisfy them with services found by scanning for headers. The Liquibase database migration tool is built around SPI services. As an OSGi bundle it utilizes SPI Fly to spin up its SPI services by adding both a [ for the services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L252] as well as a [ for the same services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L217] in the liquibase-core manifest file. But all of the SPI services of liquibase needs to be running before liquibase is actually used and there is no way to know that all the required services have been started. So to make liquibase available on the default run level 80 (where e.g. jdbc-config is running), liquibase and SPI Fly both has to be started on a lower run level (e.g. 40). And the built-in spifly feature of karaf starts SPI Fly on run level 80 which is much too late for liquibase to make use of it (all SPI services will be started, but much too late). So it would be good to have the spifly feature start the spifly bundle at a lower run level than the default. > It would be nice if the spifly feature was on a start-level other than the > default > -- > > Key: KARAF-7843 > URL: https://issues.apache.org/jira/browse/KARAF-7843 > Project: Karaf > Issue Type: Bug >Reporter: Steinar Bang >Priority: Major > > [Apache Aries SPI > Fly|https://aries.apache.org/documentation/modules/spi-fly.html] helps > translating SPI services into OSGi services. > SPI Fly looks for OSGi manifest headers and then tries > to satisfy them with services found by scanning for > headers. > The Liquibase database migration tool is built around SPI services. > As an OSGi bundle it utilizes SPI Fly to spin up its SPI services by adding > both a [ for the > services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L252] > as well as a [ for the same > services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L217] > in the liquibase-core manifest file. > But all of the SPI services of liquibase needs to be running before liquibase > is actually used and there is no way to know that all the required services > have been started. > So to make liquibase available on the default start level 80 (where e.g. > jdbc-config is running), liquibase and SPI Fly both has to be started on a > lower start level (e.g. 40). > And the built-in spifly feature of karaf starts SPI Fly on start level 80 > which is much too late for liquibase to make use of it (all SPI services will > be started, but much too late). > So it would be good to have the spifly feature start the spifly bundle at a > lower start level than the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KARAF-7843) It would be nice if the spifly feature was on a start-level other than the default
[ https://issues.apache.org/jira/browse/KARAF-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steinar Bang updated KARAF-7843: Summary: It would be nice if the spifly feature was on a start-level other than the default (was: It would be nice if the spifly feature was on a run-level other than the default) > It would be nice if the spifly feature was on a start-level other than the > default > -- > > Key: KARAF-7843 > URL: https://issues.apache.org/jira/browse/KARAF-7843 > Project: Karaf > Issue Type: Bug >Reporter: Steinar Bang >Priority: Major > > [Apache Aries SPI > Fly|https://aries.apache.org/documentation/modules/spi-fly.html] helps > translating SPI services into OSGi services. > SPI Fly looks for OSGi manifest headers and then tries > to satisfy them with services found by scanning for > headers. > The Liquibase database migration tool is built around SPI services. > As an OSGi bundle it utilizes SPI Fly to spin up its SPI services by adding > both a [ for the > services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L252] > as well as a [ for the same > services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L217] > in the liquibase-core manifest file. > But all of the SPI services of liquibase needs to be running before liquibase > is actually used and there is no way to know that all the required services > have been started. > So to make liquibase available on the default run level 80 (where e.g. > jdbc-config is running), liquibase and SPI Fly both has to be started on a > lower run level (e.g. 40). > And the built-in spifly feature of karaf starts SPI Fly on run level 80 which > is much too late for liquibase to make use of it (all SPI services will be > started, but much too late). > So it would be good to have the spifly feature start the spifly bundle at a > lower run level than the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KARAF-7843) It would be nice if the spifly feature was on a run-level other than the default
Steinar Bang created KARAF-7843: --- Summary: It would be nice if the spifly feature was on a run-level other than the default Key: KARAF-7843 URL: https://issues.apache.org/jira/browse/KARAF-7843 Project: Karaf Issue Type: Bug Reporter: Steinar Bang [Apache Aries SPI Fly|https://aries.apache.org/documentation/modules/spi-fly.html] helps translating SPI services into OSGi services. SPI Fly looks for OSGi manifest headers and then tries to satisfy them with services found by scanning for headers. The Liquibase database migration tool is built around SPI services. As an OSGi bundle it utilizes SPI Fly to spin up its SPI services by adding both a [ for the services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L252] as well as a [ for the same services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L217] in the liquibase-core manifest file. But all of the SPI services of liquibase needs to be running before liquibase is actually used and there is no way to know that all the required services have been started. So to make liquibase available on the default run level 80 (where e.g. jdbc-config is running), liquibase and SPI Fly both has to be started on a lower run level (e.g. 40). And the built-in spifly feature of karaf starts SPI Fly on run level 80 which is much too late for liquibase to make use of it (all SPI services will be started, but much too late). So it would be good to have the spifly feature start the spifly bundle at a lower run level than the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KARAF-7605) Karaf BoM causes import of org.osgi.service.log to have lower bound 1.5.0 but only version 1.4.0 is available
Steinar Bang created KARAF-7605:
---
Summary: Karaf BoM causes import of org.osgi.service.log to have
lower bound 1.5.0 but only version 1.4.0 is available
Key: KARAF-7605
URL: https://issues.apache.org/jira/browse/KARAF-7605
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.4.2, 4.4.1, 4.4.0
Reporter: Steinar Bang
Using the karaf BoM for dependencies, maven-bundle-plugin will create an
import-package of org.osgi.service.log with lower bound 1.5.0, while the only
version of org.osgi.service.log provided by karaf is 1.4.0.
So you get errors like this:
{noformat}
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve
user-admin-with-testdb/0.0.0: missing requirement
[user-admin-with-testdb/0.0.0] osgi.identity;
osgi.identity=authservice-user-admin; type=karaf.feature [caused by: Unable to
resolve authservice-user-admin/0.0.0: missing requirement
[authservice-user-admin/0.0.0] osgi.identity;
osgi.identity=authservice-user-management-frontend; type=karaf.feature [caused
by: Unable to resolve authservice-user-management-frontend/1.14.7.SNAPSHOT:
missing requirement [authservice-user-management-frontend/1.14.7.SNAPSHOT]
osgi.identity; osgi.identity=no.priv.bang.authservice.web.users.frontend;
type=osgi.bundle; version="[1.14.7.SNAPSHOT,1.14.7.SNAPSHOT]";
resolution:=mandatory [caused by: Unable to resolve
no.priv.bang.authservice.web.users.frontend/1.14.7.SNAPSHOT: missing
requirement [no.priv.bang.authservice.web.users.frontend/1.14.7.SNAPSHOT]
osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.osgi.service.log)(version>=1.5.0)(!(version>=2.0.0)))"]]]
at
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 12 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (KARAF-7534) Add a way to get the path to the executing karaf in KarafTestSupport
Steinar Bang created KARAF-7534: --- Summary: Add a way to get the path to the executing karaf in KarafTestSupport Key: KARAF-7534 URL: https://issues.apache.org/jira/browse/KARAF-7534 Project: Karaf Issue Type: Improvement Reporter: Steinar Bang I would like to programmatically read the karaf.log file of an executed pax exam karaf integration test, to be able to assert if the file contains the text "Exception". So a convenient way for a subclass of the KarafTestSupport class, to find the "target/exam/" directory would be nice to have. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KARAF-3467) Create a BOM (Bill of Material) for Karaf
[ https://issues.apache.org/jira/browse/KARAF-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069320#comment-17069320 ] Steinar Bang commented on KARAF-3467: - [~jbonofre] Is it possible to get a back-port to 4.2.9? Alternatively: initially target it to 4.2.9 and merge it into master? > Create a BOM (Bill of Material) for Karaf > - > > Key: KARAF-3467 > URL: https://issues.apache.org/jira/browse/KARAF-3467 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.9 > > > Please also view KARAF-3466 for details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-6613) Paste doesn't work in ssh terminal
[
https://issues.apache.org/jira/browse/KARAF-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033015#comment-17033015
]
Steinar Bang commented on KARAF-6613:
-
I encountered this issue today when ssh'ing in to a karaf 4.2.8 running on
debian, and attempting to [copy/paste commands for adding a maven
repository|https://github.com/steinarb/ukelonn#kjapp-test-av-programvaren-uten-å-bygge-koden].
I encountered the problem both with cygwin64 bash as the terminal I did ssh
from, and with LXTerminal (running on cygwin X11) as the terminal I did ssh
from.
> Paste doesn't work in ssh terminal
> --
>
> Key: KARAF-6613
> URL: https://issues.apache.org/jira/browse/KARAF-6613
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.8
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.9
>
>
> An improvement has been done in jline (about pasting long line):
> {code:java}
> commit fea903cc9e78da64d66422f07db1b7890cf18b89
> Author: Guillaume Nodet
> Date: Mon Nov 25 20:45:30 2019 +0100
> Improve performances when pasting huge strings, fixes #479 {code}
> Unfortunately, it's causing an issue with pasting string in ssh (both openssh
> and Karaf bin/client).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KARAF-5572) The parent pom of the karaf manual module in 4.1.x still points to 4.1.3-SNAPSHOT
Steinar Bang created KARAF-5572:
---
Summary: The parent pom of the karaf manual module in 4.1.x still
points to 4.1.3-SNAPSHOT
Key: KARAF-5572
URL: https://issues.apache.org/jira/browse/KARAF-5572
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 4.1.4
Reporter: Steinar Bang
The parent pom reference of the karaf manual module wasn't bumped with the rest
of the pom versions in the 4.1.3 release, and is still (on 4.1.5-SNAPSHOT)
referencing 4.1.3-SNAPSHOT:
https://github.com/apache/karaf/blob/karaf-4.1.x/manual/pom.xml#L20
This caused things to break when I tried running [the debian mh_make
utility|https://gambaru.de/blog/2017/08/02/pdfsam-how-to-upgrade-a-maven-application-for-debian/]
on the apache-karaf 4.1.4 source tarball:
{noformat}
Checking the parent dependency in the sub project itests/pom.xml
Analysing manual/pom.xml...
Jan 20, 2018 11:12:01 AM org.debian.maven.packager.DependenciesSolver
resolveDependencies
SEVERE: Error while resolving ./manual/pom.xml: Dependency not found
org.apache.karaf:karaf:pom:4.1.3-SNAPSHOT
Jan 20, 2018 11:12:01 AM org.debian.maven.packager.DependenciesSolver
resolveDependencies
SEVERE:
org.debian.maven.repo.DependencyNotFoundException: Dependency not found
org.apache.karaf:karaf:pom:4.1.3-SNAPSHOT
at org.debian.maven.repo.Repository.registerPom(Repository.java:414)
at
org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:321)
at
org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:421)
at
org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:261)
at
org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:962)
{noformat}
The master version of the manual pom references version 4.2.0-SNAPSHOT
https://github.com/apache/karaf/blob/master/manual/pom.xml#L20
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5512) karaf:features-generate-descriptor should pick up feature dependencies from the features configuration
Steinar Bang created KARAF-5512: --- Summary: karaf:features-generate-descriptor should pick up feature dependencies from the features configuration Key: KARAF-5512 URL: https://issues.apache.org/jira/browse/KARAF-5512 Project: Karaf Issue Type: Improvement Components: karaf-tooling Reporter: Steinar Bang If the karaf:features-generate-descriptor could pick up and use the features in the ["features" configuration parameter defined on the AbstractFeatureMojo|https://github.com/apache/karaf/blob/master/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/AbstractFeatureMojo.java#L56] then I could get rid of most of my src/main/feature/feature.xml template files and handle feature file generation completly in the POMs. And that would be nice. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories
[
https://issues.apache.org/jira/browse/KARAF-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160074#comment-16160074
]
Steinar Bang commented on KARAF-5350:
-
Using the approach I outlined above should avoid trying to load a bundle in the
middle of deployment:
* The listener would do HTTP conditional GETs on the relevant
maven-metadata.xml and would do nothing on [304 Not
Modified|https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection]
responses except for waiting the configured interval and doing a new
conditional GET
* When the listener received a 200 response it would parse the file and extract
the new snapshot and compare it with the previous snapshot
That means the listener would not try to update a bundle, until:
# It had successfully loaded the maven-metadata.xml file
# It had successfully parsed the loaded maven-metadata.xml file and extracted
the newest snapshot in the file
# The extracted snapshot was different from the current snapshot
But the above idea was what I had for my own listener component.
A karaf cave based solution might be different. I don't know much about the
capabilities of cave, but from what little I have read the best approach might
be to create a local maven snapshot repository in cave shadowing a remote
repository, and then have karaf watch that in a similar way to how it watches
the local repository...?
> Get auto update functionality like "bundle:watch *" on snapshot artifacts
> from remote repositories
> --
>
> Key: KARAF-5350
> URL: https://issues.apache.org/jira/browse/KARAF-5350
> Project: Karaf
> Issue Type: Improvement
>Reporter: Steinar Bang
>
> I now have a continous deployment pipeline for [my
> project|https://github.com/steinarb/ukelonn] almost automated:
> # All changes I would like deployed, I merge to master and then push master
> to github
> # New pushes on master triggers a build on travis-ci
> # A successful build on travis-ci results in a new snapshot being deployed to
> a maven repository accessible via HTTP
> ## The bundles that make up my application have been installed from snapshots
> in the maven repository, like so (karaf consolle commands):
> {noformat}
> config:edit org.ops4j.pax.url.mvn
> config:property-append org.ops4j.pax.url.mvn.repositories ",
> https://maven.bang.priv.no/repository/@snapshots,
> http://maven.vaadin.com/vaadin-addons";
> config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
> config:update
> feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
> feature:install ukelonn-db-postgresql
> feature:install ukelonn
> {noformat}
> # The final step I have to do during a deployment, is to log in with ssh to
> the karaf console and give "bundle:update" on each bundle
> {noformat}
> bundle:update no.priv.bang.ukelonn.api
> bundle:update no.priv.bang.ukelonn.db.liquibase
> bundle:update no.priv.bang.ukelonn.db.postgresql
> bundle:update no.priv.bang.ukelonn
> {noformat}
> It is the final step I would like to have automated, so that new snapshots
> deployed to the remote repository is automatically picked up by karaf.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories
[
https://issues.apache.org/jira/browse/KARAF-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158718#comment-16158718
]
Steinar Bang edited comment on KARAF-5350 at 9/9/17 6:53 AM:
-
How costly is the "feature:install" operation on a feature consisting of
snapshot bundles from a remote repository?
(I'm thinking of just the ballpark numbers. Ie. is this so time consuming it
should only be run once a day? Or is this so low-cost it could be run once a
minute?)
Note that a dedicated "remote maven listener" can be made to be cheap in
network and CPU usage terms, simply by not doing anything until it has to,
first by using conditional HTTP GETs to watch the appropriate
maven-metadata.xml files, and after downloading them only do something when
there are new timestamps.
See [my outline of a possible karaf
component|https://groups.google.com/d/msg/ops4j/wbiFG6cLLps/PPRTW_SrAQAJ] on
the OPS4J mailing list.
was (Author: s...@dod.no):
How costly is the "feature:install" operation on a feature consisting of
snapshot bundles from a remote repository?
(I'm thinking of just the ballpark numbers. Ie. is this so time consuming it
should only be run once a day? Or is this so low-cost it could be run once a
minute?)
> Get auto update functionality like "bundle:watch *" on snapshot artifacts
> from remote repositories
> --
>
> Key: KARAF-5350
> URL: https://issues.apache.org/jira/browse/KARAF-5350
> Project: Karaf
> Issue Type: Improvement
>Reporter: Steinar Bang
>
> I now have a continous deployment pipeline for [my
> project|https://github.com/steinarb/ukelonn] almost automated:
> # All changes I would like deployed, I merge to master and then push master
> to github
> # New pushes on master triggers a build on travis-ci
> # A successful build on travis-ci results in a new snapshot being deployed to
> a maven repository accessible via HTTP
> ## The bundles that make up my application have been installed from snapshots
> in the maven repository, like so (karaf consolle commands):
> {noformat}
> config:edit org.ops4j.pax.url.mvn
> config:property-append org.ops4j.pax.url.mvn.repositories ",
> https://maven.bang.priv.no/repository/@snapshots,
> http://maven.vaadin.com/vaadin-addons";
> config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
> config:update
> feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
> feature:install ukelonn-db-postgresql
> feature:install ukelonn
> {noformat}
> # The final step I have to do during a deployment, is to log in with ssh to
> the karaf console and give "bundle:update" on each bundle
> {noformat}
> bundle:update no.priv.bang.ukelonn.api
> bundle:update no.priv.bang.ukelonn.db.liquibase
> bundle:update no.priv.bang.ukelonn.db.postgresql
> bundle:update no.priv.bang.ukelonn
> {noformat}
> It is the final step I would like to have automated, so that new snapshots
> deployed to the remote repository is automatically picked up by karaf.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories
[
https://issues.apache.org/jira/browse/KARAF-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158718#comment-16158718
]
Steinar Bang commented on KARAF-5350:
-
How costly is the "feature:install" operation on a feature consisting of
snapshot bundles from a remote repository?
(I'm thinking of just the ballpark numbers. Ie. is this so time consuming it
should only be run once a day? Or is this so low-cost it could be run once a
minute?)
> Get auto update functionality like "bundle:watch *" on snapshot artifacts
> from remote repositories
> --
>
> Key: KARAF-5350
> URL: https://issues.apache.org/jira/browse/KARAF-5350
> Project: Karaf
> Issue Type: Improvement
>Reporter: Steinar Bang
>
> I now have a continous deployment pipeline for [my
> project|https://github.com/steinarb/ukelonn] almost automated:
> # All changes I would like deployed, I merge to master and then push master
> to github
> # New pushes on master triggers a build on travis-ci
> # A successful build on travis-ci results in a new snapshot being deployed to
> a maven repository accessible via HTTP
> ## The bundles that make up my application have been installed from snapshots
> in the maven repository, like so (karaf consolle commands):
> {noformat}
> config:edit org.ops4j.pax.url.mvn
> config:property-append org.ops4j.pax.url.mvn.repositories ",
> https://maven.bang.priv.no/repository/@snapshots,
> http://maven.vaadin.com/vaadin-addons";
> config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
> config:update
> feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
> feature:install ukelonn-db-postgresql
> feature:install ukelonn
> {noformat}
> # The final step I have to do during a deployment, is to log in with ssh to
> the karaf console and give "bundle:update" on each bundle
> {noformat}
> bundle:update no.priv.bang.ukelonn.api
> bundle:update no.priv.bang.ukelonn.db.liquibase
> bundle:update no.priv.bang.ukelonn.db.postgresql
> bundle:update no.priv.bang.ukelonn
> {noformat}
> It is the final step I would like to have automated, so that new snapshots
> deployed to the remote repository is automatically picked up by karaf.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories
[
https://issues.apache.org/jira/browse/KARAF-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157581#comment-16157581
]
Steinar Bang commented on KARAF-5350:
-
The issue isn't about actually updating the bundles, just "bundle:update" is
sufficient for that.
The issue is about watchdogging the remote repository for new snapshots and
automatically reloading them.
See the recent threads on the ops4j and karaf-user mailing lists:
*
[karaf-user|http://karaf.922171.n3.nabble.com/Can-karaf-cave-be-used-to-watch-remote-repos-for-snapshot-updates-tp4051319p4051364.html]
* [ops4j|https://groups.google.com/d/msg/ops4j/wbiFG6cLLps/Ni_-GKyvAQAJ]
> Get auto update functionality like "bundle:watch *" on snapshot artifacts
> from remote repositories
> --
>
> Key: KARAF-5350
> URL: https://issues.apache.org/jira/browse/KARAF-5350
> Project: Karaf
> Issue Type: Improvement
>Reporter: Steinar Bang
>
> I now have a continous deployment pipeline for [my
> project|https://github.com/steinarb/ukelonn] almost automated:
> # All changes I would like deployed, I merge to master and then push master
> to github
> # New pushes on master triggers a build on travis-ci
> # A successful build on travis-ci results in a new snapshot being deployed to
> a maven repository accessible via HTTP
> ## The bundles that make up my application have been installed from snapshots
> in the maven repository, like so (karaf consolle commands):
> {noformat}
> config:edit org.ops4j.pax.url.mvn
> config:property-append org.ops4j.pax.url.mvn.repositories ",
> https://maven.bang.priv.no/repository/@snapshots,
> http://maven.vaadin.com/vaadin-addons";
> config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
> config:update
> feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
> feature:install ukelonn-db-postgresql
> feature:install ukelonn
> {noformat}
> # The final step I have to do during a deployment, is to log in with ssh to
> the karaf console and give "bundle:update" on each bundle
> {noformat}
> bundle:update no.priv.bang.ukelonn.api
> bundle:update no.priv.bang.ukelonn.db.liquibase
> bundle:update no.priv.bang.ukelonn.db.postgresql
> bundle:update no.priv.bang.ukelonn
> {noformat}
> It is the final step I would like to have automated, so that new snapshots
> deployed to the remote repository is automatically picked up by karaf.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories
[
https://issues.apache.org/jira/browse/KARAF-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steinar Bang updated KARAF-5350:
Environment: (was: I now have a continous deployment pipeline for [my
project|https://github.com/steinarb/ukelonn] almost automated:
# All changes I would like deployed, I merge to master and then push master to
github
# New pushes on master triggers a build on travis-ci
# A successful build on travis-ci results in a new snapshot being deployed to a
maven repository accessible via HTTP
## The bundles that make up my application have been installed from snapshots
in the maven repository, like so (karaf consolle commands):
{noformat}
config:edit org.ops4j.pax.url.mvn
config:property-append org.ops4j.pax.url.mvn.repositories ",
https://maven.bang.priv.no/repository/@snapshots,
http://maven.vaadin.com/vaadin-addons";
config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
config:update
feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
feature:install ukelonn-db-postgresql
feature:install ukelonn
{noformat}
# The final step I have to do during a deployment, is to log in with ssh to the
karaf console and give "bundle:update" on each bundle
{noformat}
bundle:update no.priv.bang.ukelonn.api
bundle:update no.priv.bang.ukelonn.db.liquibase
bundle:update no.priv.bang.ukelonn.db.postgresql
bundle:update no.priv.bang.ukelonn
{noformat}
It is the final step I would like to have automated, so that new snapshots
deployed to the remote repository is automatically picked up by karaf.)
Description:
I now have a continous deployment pipeline for [my
project|https://github.com/steinarb/ukelonn] almost automated:
# All changes I would like deployed, I merge to master and then push master to
github
# New pushes on master triggers a build on travis-ci
# A successful build on travis-ci results in a new snapshot being deployed to a
maven repository accessible via HTTP
## The bundles that make up my application have been installed from snapshots
in the maven repository, like so (karaf consolle commands):
{noformat}
config:edit org.ops4j.pax.url.mvn
config:property-append org.ops4j.pax.url.mvn.repositories ",
https://maven.bang.priv.no/repository/@snapshots,
http://maven.vaadin.com/vaadin-addons";
config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
config:update
feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
feature:install ukelonn-db-postgresql
feature:install ukelonn
{noformat}
# The final step I have to do during a deployment, is to log in with ssh to the
karaf console and give "bundle:update" on each bundle
{noformat}
bundle:update no.priv.bang.ukelonn.api
bundle:update no.priv.bang.ukelonn.db.liquibase
bundle:update no.priv.bang.ukelonn.db.postgresql
bundle:update no.priv.bang.ukelonn
{noformat}
It is the final step I would like to have automated, so that new snapshots
deployed to the remote repository is automatically picked up by karaf.
> Get auto update functionality like "bundle:watch *" on snapshot artifacts
> from remote repositories
> --
>
> Key: KARAF-5350
> URL: https://issues.apache.org/jira/browse/KARAF-5350
> Project: Karaf
> Issue Type: Improvement
>Reporter: Steinar Bang
>
> I now have a continous deployment pipeline for [my
> project|https://github.com/steinarb/ukelonn] almost automated:
> # All changes I would like deployed, I merge to master and then push master
> to github
> # New pushes on master triggers a build on travis-ci
> # A successful build on travis-ci results in a new snapshot being deployed to
> a maven repository accessible via HTTP
> ## The bundles that make up my application have been installed from snapshots
> in the maven repository, like so (karaf consolle commands):
> {noformat}
> config:edit org.ops4j.pax.url.mvn
> config:property-append org.ops4j.pax.url.mvn.repositories ",
> https://maven.bang.priv.no/repository/@snapshots,
> http://maven.vaadin.com/vaadin-addons";
> config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
> config:update
> feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
> feature:install ukelonn-db-postgresql
> feature:install ukelonn
> {noformat}
> # The final step I have to do during a deployment, is to log in with ssh to
> the karaf console and give "bundle:update" on each bundle
> {noformat}
> bundle:update no.priv.bang.ukelonn.api
> bundle:update no.priv.bang.ukelonn.db.liquibase
> bundle:update no.priv.bang.ukelonn.db.postgresql
> bundle:update no.priv.bang.ukelonn
> {noformat}
> It is the final step I would like to have automated, so that new snapshots
> deployed to the remote repository is automatically picked up by karaf.
--
This message was sent by At
[jira] [Created] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories
Steinar Bang created KARAF-5350:
---
Summary: Get auto update functionality like "bundle:watch *" on
snapshot artifacts from remote repositories
Key: KARAF-5350
URL: https://issues.apache.org/jira/browse/KARAF-5350
Project: Karaf
Issue Type: Improvement
Environment: I now have a continous deployment pipeline for [my
project|https://github.com/steinarb/ukelonn] almost automated:
# All changes I would like deployed, I merge to master and then push master to
github
# New pushes on master triggers a build on travis-ci
# A successful build on travis-ci results in a new snapshot being deployed to a
maven repository accessible via HTTP
## The bundles that make up my application have been installed from snapshots
in the maven repository, like so (karaf consolle commands):
{noformat}
config:edit org.ops4j.pax.url.mvn
config:property-append org.ops4j.pax.url.mvn.repositories ",
https://maven.bang.priv.no/repository/@snapshots,
http://maven.vaadin.com/vaadin-addons";
config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
config:update
feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
feature:install ukelonn-db-postgresql
feature:install ukelonn
{noformat}
# The final step I have to do during a deployment, is to log in with ssh to the
karaf console and give "bundle:update" on each bundle
{noformat}
bundle:update no.priv.bang.ukelonn.api
bundle:update no.priv.bang.ukelonn.db.liquibase
bundle:update no.priv.bang.ukelonn.db.postgresql
bundle:update no.priv.bang.ukelonn
{noformat}
It is the final step I would like to have automated, so that new snapshots
deployed to the remote repository is automatically picked up by karaf.
Reporter: Steinar Bang
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5284) Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
[
https://issues.apache.org/jira/browse/KARAF-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115382#comment-16115382
]
Steinar Bang commented on KARAF-5284:
-
I just tried the 4.1.2 release candate zip file from:
https://repository.apache.org/content/repositories/orgapachekaraf-1097/org/apache/karaf/apache-karaf/4.1.2/
This zip file's bourne shell file started karaf without a hitch on the exact
same cygwin where I had the problem from the 4.1.2-SNAPSHOT file:
{noformat}
sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2$ bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.2)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()>
{noformat}
> Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
>
>
> Key: KARAF-5284
> URL: https://issues.apache.org/jira/browse/KARAF-5284
> Project: Karaf
> Issue Type: Bug
> Environment: Karaf 4.1.2-SNAPSHOT, zip file assembly, built from a
> fresh pull.
> JDK 1.8_141
> CYGWIN_NT-10.0 mccoy 2.5.2(0.297/5/3) 2016-06-23 14:29 x86_64 Cygwin
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Labels: karaf-shell
>
> Starting karaf unpacked from a zip file, from a cygwin terminal works in
> karaf 4.1.1 (starting from the karaf.bat file doesn't work there).
> Starting karaf 4.1.2-SNAPSHOT unpacked from a freshly build zip file, does
> not work, when using the bin/karaf sh file. It does, however, work to start
> karaf using the karaf.bat file.
> Since karaf is startable from the cygwin window, which is the important thing
> (better copy/paste and window resizing features than cmd.exe), this isn't
> very important.
> But I'm reporting it anyway, since it is a change in behaviour since 4.1.1.
> Starting karaf using bin/karaf gave this error message
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> bin/karaf: line 18: $'\r': command not found
> bin/karaf: line 19: syntax error near unexpected token `$'{\r''
> 'in/karaf: line 19: `realpath() {
> {noformat}
> Since this is recognizable as a "problem with CR-LF" error message, I edit
> the bin/karaf in emacs, changing CRLF to just LF, but then I got these error
> messages:
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 18: $'\r':
> command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19: syntax
> error near unexpected token `$'{\r''
> 'cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19:
> `warn() {
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 18:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 26:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 33:
> $'\r': command not found
> bin/karaf: line 109: detectOS: command not found
> bin/karaf: line 112: unlimitFD: command not found
> bin/karaf: line 115: locateHome: command not found
> bin/karaf: line 118: locateBase: command not found
> bin/karaf: line 121: locateData: command not found
> bin/karaf: line 124: locateEtc: command not found
> bin/karaf: line 127: setupNativePath: command not found
> bin/karaf: line 130: locateJava: command not found
> bin/karaf: line 133: detectJVM: command not found
> bin/karaf: line 136: checkJvmVersion: command not found
> bin/karaf: line 142: setupDefaults: command not found
> bin/karaf: line 148: setupDebugOptions: command not found
> bin/karaf: line 165: convertPaths: command not found
> bin/karaf: line 243: KARAF_HOME: parameter null or not set
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5284) Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
[
https://issues.apache.org/jira/browse/KARAF-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114425#comment-16114425
]
Steinar Bang commented on KARAF-5284:
-
Was the karaf 4.1.2-SNAPSHOT where you couldn't reproduce built on windows? Or
was it built on linux/BSD/etc.?
The 4.1.2-SNAPSHOT that failed for me was built on windows (and that might
affect the line ending of the scripts).
> Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
>
>
> Key: KARAF-5284
> URL: https://issues.apache.org/jira/browse/KARAF-5284
> Project: Karaf
> Issue Type: Bug
> Environment: Karaf 4.1.2-SNAPSHOT, zip file assembly, built from a
> fresh pull.
> JDK 1.8_141
> CYGWIN_NT-10.0 mccoy 2.5.2(0.297/5/3) 2016-06-23 14:29 x86_64 Cygwin
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Labels: karaf-shell
>
> Starting karaf unpacked from a zip file, from a cygwin terminal works in
> karaf 4.1.1 (starting from the karaf.bat file doesn't work there).
> Starting karaf 4.1.2-SNAPSHOT unpacked from a freshly build zip file, does
> not work, when using the bin/karaf sh file. It does, however, work to start
> karaf using the karaf.bat file.
> Since karaf is startable from the cygwin window, which is the important thing
> (better copy/paste and window resizing features than cmd.exe), this isn't
> very important.
> But I'm reporting it anyway, since it is a change in behaviour since 4.1.1.
> Starting karaf using bin/karaf gave this error message
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> bin/karaf: line 18: $'\r': command not found
> bin/karaf: line 19: syntax error near unexpected token `$'{\r''
> 'in/karaf: line 19: `realpath() {
> {noformat}
> Since this is recognizable as a "problem with CR-LF" error message, I edit
> the bin/karaf in emacs, changing CRLF to just LF, but then I got these error
> messages:
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 18: $'\r':
> command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19: syntax
> error near unexpected token `$'{\r''
> 'cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19:
> `warn() {
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 18:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 26:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 33:
> $'\r': command not found
> bin/karaf: line 109: detectOS: command not found
> bin/karaf: line 112: unlimitFD: command not found
> bin/karaf: line 115: locateHome: command not found
> bin/karaf: line 118: locateBase: command not found
> bin/karaf: line 121: locateData: command not found
> bin/karaf: line 124: locateEtc: command not found
> bin/karaf: line 127: setupNativePath: command not found
> bin/karaf: line 130: locateJava: command not found
> bin/karaf: line 133: detectJVM: command not found
> bin/karaf: line 136: checkJvmVersion: command not found
> bin/karaf: line 142: setupDefaults: command not found
> bin/karaf: line 148: setupDebugOptions: command not found
> bin/karaf: line 165: convertPaths: command not found
> bin/karaf: line 243: KARAF_HOME: parameter null or not set
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KARAF-5284) Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
Steinar Bang created KARAF-5284:
---
Summary: Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in
cygwin
Key: KARAF-5284
URL: https://issues.apache.org/jira/browse/KARAF-5284
Project: Karaf
Issue Type: Bug
Environment: Karaf 4.1.2-SNAPSHOT, zip file assembly, built from a
fresh pull.
JDK 1.8_141
CYGWIN_NT-10.0 mccoy 2.5.2(0.297/5/3) 2016-06-23 14:29 x86_64 Cygwin
Reporter: Steinar Bang
Priority: Minor
Starting karaf unpacked from a zip file, from a cygwin terminal works in karaf
4.1.1 (starting from the karaf.bat file doesn't work there).
Starting karaf 4.1.2-SNAPSHOT unpacked from a freshly build zip file, does not
work, when using the bin/karaf sh file. It does, however, work to start karaf
using the karaf.bat file.
Since karaf is startable from the cygwin window, which is the important thing
(better copy/paste and window resizing features than cmd.exe), this isn't very
important.
But I'm reporting it anyway, since it is a change in behaviour since 4.1.1.
Starting karaf using bin/karaf gave this error message
{noformat}
sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
bin/karaf: line 18: $'\r': command not found
bin/karaf: line 19: syntax error near unexpected token `$'{\r''
'in/karaf: line 19: `realpath() {
{noformat}
Since this is recognizable as a "problem with CR-LF" error message, I edit the
bin/karaf in emacs, changing CRLF to just LF, but then I got these error
messages:
{noformat}
sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 18: $'\r':
command not found
/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19: syntax
error near unexpected token `$'{\r''
'cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19: `warn() {
/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 18:
$'\r': command not found
/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 26:
$'\r': command not found
/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 33:
$'\r': command not found
bin/karaf: line 109: detectOS: command not found
bin/karaf: line 112: unlimitFD: command not found
bin/karaf: line 115: locateHome: command not found
bin/karaf: line 118: locateBase: command not found
bin/karaf: line 121: locateData: command not found
bin/karaf: line 124: locateEtc: command not found
bin/karaf: line 127: setupNativePath: command not found
bin/karaf: line 130: locateJava: command not found
bin/karaf: line 133: detectJVM: command not found
bin/karaf: line 136: checkJvmVersion: command not found
bin/karaf: line 142: setupDefaults: command not found
bin/karaf: line 148: setupDebugOptions: command not found
bin/karaf: line 165: convertPaths: command not found
bin/karaf: line 243: KARAF_HOME: parameter null or not set
sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (KARAF-5115) Error while installing cxf
[
https://issues.apache.org/jira/browse/KARAF-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109681#comment-16109681
]
Steinar Bang edited comment on KARAF-5115 at 8/1/17 8:26 PM:
-
Verified fixed for me in karaf 4.1.2-SNAPSHOT on Windows 7, jdk 1.8_144.
Thanks!
was (Author: s...@dod.no):
Verified fixed for me on Windows 7, jdk 1.8_144.
Thanks!
> Error while installing cxf
> --
>
> Key: KARAF-5115
> URL: https://issues.apache.org/jira/browse/KARAF-5115
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows 10 64bit
> Java JDK 1.8.0_131
>Reporter: Massimo Bono
>Assignee: Christian Schneider
> Labels: features
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log, karaf_log_install_ukelonn.zip
>
>
> Hello,
> I was trying to create a REST application with karaf.
> I know there are examples over the internet showing how this can be achieved
> (like [this
> one|http://liquid-reality.de:8090/display/liquid/2011/12/22/Karaf+Tutorial+Part+4+-+CXF+Services+in+OSGi]),
> but usually they use blueprints as DI. My goal is to use Declarative Service
> instead.
> I followed this
> [guide|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=55153391]:
> it uses Karaf 3.0.3 and CXF 3.1.0, but I **think** it should work with 4.1.1
> as well.
> By doing the following:
> {code}
> karaf@root()> feature:install scr http pax-cdi-web-weld
> karaf@root()> feature:repo-add cxf 3.1.11
> Adding feature url mvn:org.apache.cxf.karaf/apache-cxf/3.1.11/xml/features
> karaf@root()> feature:install cxf/3.1.11 cxf-jaxrs-cdi/3.1.11
> {code}
> Karaf gives the following error:
> {code}
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {code}
> Furthermore, karaf *won't* return the console control to me, but remains
> stuck waiting nothing.
> It's highly possible that my procedure to install pax-cdi and cxf is flawed,
> but I still think that showing that error on the console and letting the
> shell going unresponsive are a bug of karaf (or a bug of the underlying OSGi
> framework, aka felix itself).
> Sorry if this behaviour is not a bug at all, but is just caused by my
> ignorance of the tool.
> Regards,
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109679#comment-16109679
]
Steinar Bang edited comment on KARAF-5174 at 8/1/17 8:26 PM:
-
Verified fixed for me in karaf 4.1.2-SNAPSHOT on Windows 7, jdk 1.8_144.
Thanks!
was (Author: s...@dod.no):
Verified fixed for me on Windows 7, jdk 1.8_144.
Thanks!
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log.gz, karaf.zip
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109679#comment-16109679
]
Steinar Bang commented on KARAF-5174:
-
Verified fixed for me on Windows 7, jdk 1.8_144.
Thanks!
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log.gz, karaf.zip
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5115) Error while installing cxf
[
https://issues.apache.org/jira/browse/KARAF-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109681#comment-16109681
]
Steinar Bang commented on KARAF-5115:
-
Verified fixed for me on Windows 7, jdk 1.8_144.
Thanks!
> Error while installing cxf
> --
>
> Key: KARAF-5115
> URL: https://issues.apache.org/jira/browse/KARAF-5115
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows 10 64bit
> Java JDK 1.8.0_131
>Reporter: Massimo Bono
>Assignee: Christian Schneider
> Labels: features
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log, karaf_log_install_ukelonn.zip
>
>
> Hello,
> I was trying to create a REST application with karaf.
> I know there are examples over the internet showing how this can be achieved
> (like [this
> one|http://liquid-reality.de:8090/display/liquid/2011/12/22/Karaf+Tutorial+Part+4+-+CXF+Services+in+OSGi]),
> but usually they use blueprints as DI. My goal is to use Declarative Service
> instead.
> I followed this
> [guide|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=55153391]:
> it uses Karaf 3.0.3 and CXF 3.1.0, but I **think** it should work with 4.1.1
> as well.
> By doing the following:
> {code}
> karaf@root()> feature:install scr http pax-cdi-web-weld
> karaf@root()> feature:repo-add cxf 3.1.11
> Adding feature url mvn:org.apache.cxf.karaf/apache-cxf/3.1.11/xml/features
> karaf@root()> feature:install cxf/3.1.11 cxf-jaxrs-cdi/3.1.11
> {code}
> Karaf gives the following error:
> {code}
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {code}
> Furthermore, karaf *won't* return the console control to me, but remains
> stuck waiting nothing.
> It's highly possible that my procedure to install pax-cdi and cxf is flawed,
> but I still think that showing that error on the console and letting the
> shell going unresponsive are a bug of karaf (or a bug of the underlying OSGi
> framework, aka felix itself).
> Sorry if this behaviour is not a bug at all, but is just caused by my
> ignorance of the tool.
> Regards,
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5115) Error while installing cxf
[
https://issues.apache.org/jira/browse/KARAF-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089523#comment-16089523
]
Steinar Bang commented on KARAF-5115:
-
I tried my steps for triggering the InterruptedException on
karaf-4.1.2-SNAPSHOT and the problem occurs on 4.1.2-SNAPSHOT as well.
The platform was windows 10 and java 1.8_102.
The karaf.log for this session is attached as karaf_log_ukelonn_install.zip
Here's what I did
# Cloned and built and started karaf-4.1.2-SNAPSHOT (see comment in KARAF-5174
for detailed explanation of what I did)
# Deleted the data directory resulting from the KARAF-5174 test
# Built the master branch of my application ukelonn
# Installed the ukelonn app:
{code:java}
c:\ProgramFiles\apache-karaf-4.1.2-SNAPSHOT>bin\karaf.bat debug
Listening for transport dt_socket at address: 5005
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.2-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> feature:repo-add
mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
Adding feature url mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
karaf@root()> feature:install liquibase-core
karaf@root()> feature:install ukelonn-db-derby-test
karaf@root()> feature:install ukelonn
Error executing command: java.lang.InterruptedException
{code}
At this point the karaf console is dead and doesn't even respon to Ctrl-C
> Error while installing cxf
> --
>
> Key: KARAF-5115
> URL: https://issues.apache.org/jira/browse/KARAF-5115
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows 10 64bit
> Java JDK 1.8.0_131
>Reporter: Massimo Bono
>Assignee: Jean-Baptiste Onofré
> Labels: features
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log, karaf_log_install_ukelonn.zip
>
>
> Hello,
> I was trying to create a REST application with karaf.
> I know there are examples over the internet showing how this can be achieved
> (like [this
> one|http://liquid-reality.de:8090/display/liquid/2011/12/22/Karaf+Tutorial+Part+4+-+CXF+Services+in+OSGi]),
> but usually they use blueprints as DI. My goal is to use Declarative Service
> instead.
> I followed this
> [guide|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=55153391]:
> it uses Karaf 3.0.3 and CXF 3.1.0, but I **think** it should work with 4.1.1
> as well.
> By doing the following:
> {code}
> karaf@root()> feature:install scr http pax-cdi-web-weld
> karaf@root()> feature:repo-add cxf 3.1.11
> Adding feature url mvn:org.apache.cxf.karaf/apache-cxf/3.1.11/xml/features
> karaf@root()> feature:install cxf/3.1.11 cxf-jaxrs-cdi/3.1.11
> {code}
> Karaf gives the following error:
> {code}
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {code}
> Furthermore, karaf *won't* return the console control to me, but remains
> stuck waiting nothing.
> It's highly possible that my procedure to install pax-cdi and cxf is flawed,
> but I still think that showing that error on the console and letting the
> shell going unresponsive are a bug of karaf (or a bug of the underlying OSGi
> framework, aka felix itself).
> Sorry if this behaviour is not a bug at all, but is just caused by my
> ignorance of the tool.
> Regards,
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-5115) Error while installing cxf
[
https://issues.apache.org/jira/browse/KARAF-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steinar Bang updated KARAF-5115:
Attachment: karaf_log_install_ukelonn.zip
> Error while installing cxf
> --
>
> Key: KARAF-5115
> URL: https://issues.apache.org/jira/browse/KARAF-5115
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows 10 64bit
> Java JDK 1.8.0_131
>Reporter: Massimo Bono
>Assignee: Jean-Baptiste Onofré
> Labels: features
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log, karaf_log_install_ukelonn.zip
>
>
> Hello,
> I was trying to create a REST application with karaf.
> I know there are examples over the internet showing how this can be achieved
> (like [this
> one|http://liquid-reality.de:8090/display/liquid/2011/12/22/Karaf+Tutorial+Part+4+-+CXF+Services+in+OSGi]),
> but usually they use blueprints as DI. My goal is to use Declarative Service
> instead.
> I followed this
> [guide|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=55153391]:
> it uses Karaf 3.0.3 and CXF 3.1.0, but I **think** it should work with 4.1.1
> as well.
> By doing the following:
> {code}
> karaf@root()> feature:install scr http pax-cdi-web-weld
> karaf@root()> feature:repo-add cxf 3.1.11
> Adding feature url mvn:org.apache.cxf.karaf/apache-cxf/3.1.11/xml/features
> karaf@root()> feature:install cxf/3.1.11 cxf-jaxrs-cdi/3.1.11
> {code}
> Karaf gives the following error:
> {code}
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {code}
> Furthermore, karaf *won't* return the console control to me, but remains
> stuck waiting nothing.
> It's highly possible that my procedure to install pax-cdi and cxf is flawed,
> but I still think that showing that error on the console and letting the
> shell going unresponsive are a bug of karaf (or a bug of the underlying OSGi
> framework, aka felix itself).
> Sorry if this behaviour is not a bug at all, but is just caused by my
> ignorance of the tool.
> Regards,
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089466#comment-16089466
]
Steinar Bang edited comment on KARAF-5174 at 7/17/17 8:06 AM:
--
Tried this with karaf 4.1.2-SNAPSHOT on Windows 10, java 1.8_102, and karaf
still crashes/hangs on "feature:uninstall liquibase-core".
The karaf.log file is attached as karaf.zip
Here's what I did:
# Cloned karaf, switched to the karaf-4.1.x branch, and built with "mvn
-Pfastinstall"
# Unpacked karaf/assemblies/apache-karaf/target/apache-karaf-4.1.2-SNAPSHOT.zip
and started with bin\karaf.bat
# Cloned liquibase-core and built with maven
# Installed liquibase-core and uninstalled it again (the first failed
repo-install was because I hadn't built liquibase-core on this machine)
{noformat}
c:\ProgramFiles\apache-karaf-4.1.2-SNAPSHOT>bin\karaf.bat debug
Listening for transport dt_socket at address: 5005
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.2-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> feature:repo-add
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Adding feature url
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Error executing command: Error resolving artifact
no.priv.bang.karaf:liquibase-core-karaf:xml:features:LATEST :
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
karaf@root()> feature:repo-add
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Adding feature url
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
{noformat}
Karaf hangs at the final prompt, takes no commands, and (on Windows) doesn't
even respond to Ctrl-C
was (Author: s...@dod.no):
Tried this with karaf 4.1.2-SNAPSHOT on Windows 10, java 1.8_102, and karaf
still crashes/hangs on "feature:uninstall liquibase-core".
The karaf.log file is attached as karaf.zip
Here's what I did:
# Cloned karaf and built with "mvn -Pfastinstall"
# Unpacked karaf/assemblies/apache-karaf/target/apache-karaf-4.1.2-SNAPSHOT.zip
and started with bin\karaf.bat
# Cloned liquibase-core and built with maven
# Installed liquibase-core and uninstalled it again (the first failed
repo-install was because I hadn't built liquibase-core on this machine)
{noformat}
c:\ProgramFiles\apache-karaf-4.1.2-SNAPSHOT>bin\karaf.bat debug
Listening for transport dt_socket at address: 5005
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.2-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> feature:repo-add
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Adding feature url
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Error executing command: Error resolving artifact
no.priv.bang.karaf:liquibase-core-karaf:xml:features:LATEST :
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
karaf@root()> feature:repo-add
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Adding feature url
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
{noformat}
Karaf hangs at the final prompt, takes no commands, and (on Windows) doesn't
even respond to Ctrl-C
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log.gz, karaf.zip
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the f
[jira] [Commented] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089466#comment-16089466
]
Steinar Bang commented on KARAF-5174:
-
Tried this with karaf 4.1.2-SNAPSHOT on Windows 10, java 1.8_102, and karaf
still crashes/hangs on "feature:uninstall liquibase-core".
The karaf.log file is attached as karaf.zip
Here's what I did:
# Cloned karaf and built with "mvn -Pfastinstall"
# Unpacked karaf/assemblies/apache-karaf/target/apache-karaf-4.1.2-SNAPSHOT.zip
and started with bin\karaf.bat
# Cloned liquibase-core and built with maven
# Installed liquibase-core and uninstalled it again (the first failed
repo-install was because I hadn't built liquibase-core on this machine)
{noformat}
c:\ProgramFiles\apache-karaf-4.1.2-SNAPSHOT>bin\karaf.bat debug
Listening for transport dt_socket at address: 5005
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.2-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> feature:repo-add
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Adding feature url
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Error executing command: Error resolving artifact
no.priv.bang.karaf:liquibase-core-karaf:xml:features:LATEST :
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
karaf@root()> feature:repo-add
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Adding feature url
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
{noformat}
Karaf hangs at the final prompt, takes no commands, and (on Windows) doesn't
even respond to Ctrl-C
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log.gz, karaf.zip
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steinar Bang updated KARAF-5174:
Attachment: karaf.zip
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log.gz, karaf.zip
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (KARAF-5115) Error while installing cxf
[
https://issues.apache.org/jira/browse/KARAF-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079305#comment-16079305
]
Steinar Bang edited comment on KARAF-5115 at 7/8/17 8:33 PM:
-
I'm seeing this behaviour now in [my
application|https://github.com/steinarb/ukelonn/tree/using-vaadin]:
* The application stops with a frozen console with the following output on the
console:
{noformat}
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
at org.apache.karaf.main.Main.doMonitor(Main.java:382)
at org.apache.karaf.main.Main.access$100(Main.java:75)
at org.apache.karaf.main.Main$3.run(Main.java:369)
{noformat}
* This only happens the first time the application is started, if I kill karaf
and start it again everything starts normal
I don't try loading anything cxf related (as far as I know). This application
is currently a [vaadin|] application that uses the pax whiteboard extender,
registering both a servlet and a filter handling the
authentication/authorization (uses shiro).
I figured it is caused by something I've done, but I don't know what.
The behaviour on Win10, karaf-4.1.1 and java 1.8.0_102-b14 is identical to
what's described over.
The behaviour on debian stretch, karaf-4.1.1 and openjdk 1.8.0_131 is slightly
different: the stack trace ends up in karaf.log instead of the console, and the
console seems to autorestart:
{noformat}
sb@lorenzo:~/skrot/apache-karaf-4.1.1$ bin/karaf debug
karaf: JAVA_HOME not set; results may vary
Listening for transport dt_socket at address: 5005
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.1)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> feature:repo-add
mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
Adding feature url mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
karaf@root()> feature:install liquibase-core
karaf@root()> feature:install ukelonn-db-derby-test
karaf@root()> feature:install ukelonn
karaf@root()>
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.1)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()>
{noformat}
To reproduce:
# Clone and build the application
{noformat}
mkdir -p ~/git
cd ~/git
git clone https://github.com/sbang/jsr330activator.git
cd jsr330activator
mvn clean install
cd ..
git clone https://github.com/steinarb/ukelonn.git
cd ukelonn
mvn clean install
{noformat}
# Start karaf and install the application with the following commands in the
karaf console
{noformat}
feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
feature:install liquibase-core
feature:install ukelonn-db-derby-test
feature:install ukelonn
{noformat}
# The console will be stuck (or on debian: restart) after this
was (Author: s...@dod.no):
I'm seeing this behaviour now in [my
application|https://github.com/steinarb/ukelonn/tree/using-vaadin]:
* The application stops with a frozen console with the following output on the
console:
{noformat}
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
at org.apache.karaf.main.Main.doMonitor(Main.java:382)
at org.apache.karaf.main.Main.access$100(Main.java:75)
at org.apache.karaf.main.Main$3.run(Main.java:369)
{noformat}
* This only happens the first time the application is started, if I kill karaf
and start it again everything starts normal
I don't try loading anything cxf related (as far as I know). This application
is currently a [vaadin|] application that uses the pax whiteboard extender,
registering both a servlet and a filter handling the
authentication/authorization (uses shiro).
I figured it is caused by something I've done, but I don't know what.
The behaviour on Win10, karaf-4.1.1 and java 1.8.0_102-b14 is identical to
what's described over.
The behaviour on debian stretch, karaf-4.1.1 and openjdk 1.8.0_131 is slightly
different: the stack trace end
[jira] [Commented] (KARAF-5115) Error while installing cxf
[
https://issues.apache.org/jira/browse/KARAF-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079305#comment-16079305
]
Steinar Bang commented on KARAF-5115:
-
I'm seeing this behaviour now in [my
application|https://github.com/steinarb/ukelonn/tree/using-vaadin]:
* The application stops with a frozen console with the following output on the
console:
{noformat}
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
at org.apache.karaf.main.Main.doMonitor(Main.java:382)
at org.apache.karaf.main.Main.access$100(Main.java:75)
at org.apache.karaf.main.Main$3.run(Main.java:369)
{noformat}
* This only happens the first time the application is started, if I kill karaf
and start it again everything starts normal
I don't try loading anything cxf related (as far as I know). This application
is currently a [vaadin|] application that uses the pax whiteboard extender,
registering both a servlet and a filter handling the
authentication/authorization (uses shiro).
I figured it is caused by something I've done, but I don't know what.
The behaviour on Win10, karaf-4.1.1 and java 1.8.0_102-b14 is identical to
what's described over.
The behaviour on debian stretch, karaf-4.1.1 and openjdk 1.8.0_131 is slightly
different: the stack trace ends up in karaf.log instead of the console, and the
console seems to autorestart:
{noformat}
sb@lorenzo:~/skrot/apache-karaf-4.1.1$ bin/karaf debug
karaf: JAVA_HOME not set; results may vary
Listening for transport dt_socket at address: 5005
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.1)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> feature:repo-add
mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
Adding feature url mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
karaf@root()> feature:install liquibase-core
karaf@root()> feature:install ukelonn-db-derby-test
karaf@root()> feature:install ukelonn
karaf@root()>
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.1)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()>
{noformat}
To reproduce:
# Clone and build the application
{noformat}
mkdir -p ~/git
cd ~/git
git clone https://github.com/sbang/jsr330activator.git
cd jsr330activator
mvn clean install
git clone https://github.com/steinarb/ukelonn.git
cd ukelonn
mvn clean install
{noformat}
# Start karaf and install the application with the following commands in the
karaf console
{noformat}
feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
feature:install liquibase-core
feature:install ukelonn-db-derby-test
feature:install ukelonn
{noformat}
# The console will be stuck (or on debian: restart) after this
> Error while installing cxf
> --
>
> Key: KARAF-5115
> URL: https://issues.apache.org/jira/browse/KARAF-5115
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows 10 64bit
> Java JDK 1.8.0_131
>Reporter: Massimo Bono
> Labels: features
> Attachments: karaf.log
>
>
> Hello,
> I was trying to create a REST application with karaf.
> I know there are examples over the internet showing how this can be achieved
> (like [this
> one|http://liquid-reality.de:8090/display/liquid/2011/12/22/Karaf+Tutorial+Part+4+-+CXF+Services+in+OSGi]),
> but usually they use blueprints as DI. My goal is to use Declarative Service
> instead.
> I followed this
> [guide|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=55153391]:
> it uses Karaf 3.0.3 and CXF 3.1.0, but I **think** it should work with 4.1.1
> as well.
> By doing the following:
> {code}
> karaf@root()> feature:install scr http pax-cdi-web-weld
> karaf@root()> feature:repo-add cxf 3.1.11
> Adding feature url mvn:org.apache.cxf.karaf/apache-cxf/3.1.11/xml/features
> karaf@root()> feature:install cxf/3.1.11 cxf-jaxrs-cdi/3.1.11
> {code}
> Karaf gives the following error:
> {code}
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLe
[jira] [Issue Comment Deleted] (KARAF-5104) karaf:run should support a features set
[
https://issues.apache.org/jira/browse/KARAF-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steinar Bang updated KARAF-5104:
Comment: was deleted
(was: I made a github pull request with a proposed fix for this issue:
https://github.com/apache/karaf/pull/318
The pull requests adds:
# A parameter to set a list of URLs to feature repositories to add to the karaf
started by karaf:run
# A parameter containing a comma separated list of features to install in the
karaf started by karaf:run
# If karaf:run is set up to deploy the current project artifact and if the
current project has packaging pom and an attached file with classifier
"features" and type "xml", that attachment will be installed as a feature
repository in the karaf started by the karaf:run goal
(i) _Note_: Even if you decide not to take this change, you might consider the
first commit of this pull request, because that is just as-is unit tests of the
RunMojo.deploy(BundleContext) method.)
> karaf:run should support a features set
> ---
>
> Key: KARAF-5104
> URL: https://issues.apache.org/jira/browse/KARAF-5104
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>
> Now, {{karaf:run}} can automatically install a bundle in started Karaf
> instance. The goal should be able to support features XML descriptors and a
> set of features.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5104) karaf:run should support a features set
[
https://issues.apache.org/jira/browse/KARAF-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046865#comment-16046865
]
Steinar Bang commented on KARAF-5104:
-
I made a github pull request with a proposed fix for this issue:
https://github.com/apache/karaf/pull/318
The pull requests adds:
# A parameter to set a list of URLs to feature repositories to add to the karaf
started by karaf:run
# A parameter containing a comma separated list of features to install in the
karaf started by karaf:run
# If karaf:run is set up to deploy the current project artifact and if the
current project has packaging pom and an attached file with classifier
"features" and type "xml", that attachment will be installed as a feature
repository in the karaf started by the karaf:run goal
(i) _Note_: Even if you decide not to take this change, you might consider the
first commit of this pull request, because that is just as-is unit tests of the
RunMojo.deploy(BundleContext) method.
> karaf:run should support a features set
> ---
>
> Key: KARAF-5104
> URL: https://issues.apache.org/jira/browse/KARAF-5104
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>
> Now, {{karaf:run}} can automatically install a bundle in started Karaf
> instance. The goal should be able to support features XML descriptors and a
> set of features.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045443#comment-16045443
]
Steinar Bang edited comment on KARAF-5174 at 6/10/17 7:45 AM:
--
I stopped the karaf 4.1.0 I had running (that caused the port collision
complaints in the previous comment) and tried installing and uninstalling the
liquibase-core feature, and this time karaf 4.2.0-SNAPSHOT crashed on uninstall
in the same way as on karaf 4.2.0:
{noformat}
sb@lorenzo:~/git/karaf/assemblies/apache-karaf/target/assembly$ bin/karaf
karaf: JAVA_HOME not set; results may vary
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.0-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State │ Lvl │ Version│ Name
───┼┼─┼┼─
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
karaf@root()> feature:install liquibase-core
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State│ Lvl │ Version│ Name
───┼──┼─┼┼───
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
58 │ Resolved │ 35 │ 2.0.0 │ liquibase-slf4j 2.0.0 made an OSGi
bundle fragment of org.liquibase.core, Hosts: 59
59 │ Active │ 40 │ 3.5.3 │ Liquibase Core, Fragments: 58
60 │ Active │ 40 │ 1.17.0 │ SnakeYAML
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:602)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:706)
at org.apache.karaf.main.Main.doMonitor(Main.java:379)
at org.apache.karaf.main.Main.access$100(Main.java:74)
at org.apache.karaf.main.Main$2.run(Main.java:366)
^C
sb@lorenzo:~/git/karaf/assemblies/apache-karaf/target/assembly$
{noformat}
(i) _Note_: It was necessary to press Ctrl-C to return to the bash prompt,
karaf was hanging and the end of the stack trace.
The karaf log from my use of karaf 4.2.0-SNAPSHOT has been attached as
[karaf.log.gz|https://issues.apache.org/jira/secure/attachment/12872411/karaf.log.gz]
was (Author: s...@dod.no):
I stopped the karaf 4.1.0 I had running (that caused the port collision
complaints in the previous comment) and tried installing and uninstalling the
liquibase-core feature, and this time karaf 4.2.0-SNAPSHOT crashed on uninstall
in the same way as on karaf 4.2.0:
{noformat}
sb@lorenzo:~/git/karaf/assemblies/apache-karaf/target/assembly$ bin/karaf
karaf: JAVA_HOME not set; results may vary
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.0-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State │ Lvl │ Version│ Name
───┼┼─┼┼─
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
karaf@root()> feature:install liquibase-core
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State│ Lvl │ Version│ Name
───┼──┼─┼┼───
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
58 │ Resolved │ 35 │ 2.0.0 │ liquibase-slf4j 2.0.0 made an OSGi
bundle fragment of org.liquibase.core, Hosts: 59
59 │ Active │ 40 │ 3.5.3 │ Liquibase Core, Fragments: 58
60 │ Active │ 40 │ 1.17.0 │ S
[jira] [Comment Edited] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045443#comment-16045443
]
Steinar Bang edited comment on KARAF-5174 at 6/10/17 7:42 AM:
--
I stopped the karaf 4.1.0 I had running (that caused the port collision
complaints in the previous comment) and tried installing and uninstalling the
liquibase-core feature, and this time karaf 4.2.0-SNAPSHOT crashed on uninstall
in the same way as on karaf 4.2.0:
{noformat}
sb@lorenzo:~/git/karaf/assemblies/apache-karaf/target/assembly$ bin/karaf
karaf: JAVA_HOME not set; results may vary
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.0-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State │ Lvl │ Version│ Name
───┼┼─┼┼─
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
karaf@root()> feature:install liquibase-core
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State│ Lvl │ Version│ Name
───┼──┼─┼┼───
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
58 │ Resolved │ 35 │ 2.0.0 │ liquibase-slf4j 2.0.0 made an OSGi
bundle fragment of org.liquibase.core, Hosts: 59
59 │ Active │ 40 │ 3.5.3 │ Liquibase Core, Fragments: 58
60 │ Active │ 40 │ 1.17.0 │ SnakeYAML
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:602)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:706)
at org.apache.karaf.main.Main.doMonitor(Main.java:379)
at org.apache.karaf.main.Main.access$100(Main.java:74)
at org.apache.karaf.main.Main$2.run(Main.java:366)
^C
sb@lorenzo:~/git/karaf/assemblies/apache-karaf/target/assembly$
{noformat}
The karaf log from my use of karaf 4.2.0-SNAPSHOT has been attached as
[karaf.log.gz|https://issues.apache.org/jira/secure/attachment/12872411/karaf.log.gz]
was (Author: s...@dod.no):
I stopped the karaf 4.1.0 I had running (that caused the port collision
complaints in the previous comment) and tried installing and uninstalling the
liquibase-core feature, and this time karaf 4.2.0-SNAPSHOT crashed on uninstall
in the same way as on karaf 4.2.0:
{noformat}
sb@lorenzo:~/git/karaf/assemblies/apache-karaf/target/assembly$ bin/karaf
karaf: JAVA_HOME not set; results may vary
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.0-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State │ Lvl │ Version│ Name
───┼┼─┼┼─
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
karaf@root()> feature:install liquibase-core
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State│ Lvl │ Version│ Name
───┼──┼─┼┼───
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
58 │ Resolved │ 35 │ 2.0.0 │ liquibase-slf4j 2.0.0 made an OSGi
bundle fragment of org.liquibase.core, Hosts: 59
59 │ Active │ 40 │ 3.5.3 │ Liquibase Core, Fragments: 58
60 │ Active │ 40 │ 1.17.0 │ SnakeYAML
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
[jira] [Commented] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045443#comment-16045443
]
Steinar Bang commented on KARAF-5174:
-
I stopped the karaf 4.1.0 I had running (that caused the port collision
complaints in the previous comment) and tried installing and uninstalling the
liquibase-core feature, and this time karaf 4.2.0-SNAPSHOT crashed on uninstall
in the same way as on karaf 4.2.0:
{noformat}
sb@lorenzo:~/git/karaf/assemblies/apache-karaf/target/assembly$ bin/karaf
karaf: JAVA_HOME not set; results may vary
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.0-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State │ Lvl │ Version│ Name
───┼┼─┼┼─
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
karaf@root()> feature:install liquibase-core
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State│ Lvl │ Version│ Name
───┼──┼─┼┼───
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
58 │ Resolved │ 35 │ 2.0.0 │ liquibase-slf4j 2.0.0 made an OSGi
bundle fragment of org.liquibase.core, Hosts: 59
59 │ Active │ 40 │ 3.5.3 │ Liquibase Core, Fragments: 58
60 │ Active │ 40 │ 1.17.0 │ SnakeYAML
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:602)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:706)
at org.apache.karaf.main.Main.doMonitor(Main.java:379)
at org.apache.karaf.main.Main.access$100(Main.java:74)
at org.apache.karaf.main.Main$2.run(Main.java:366)
^C
sb@lorenzo:~/git/karaf/assemblies/apache-karaf/target/assembly$
{noformat}
The karaf log from my use of karaf 4.2.0-SNAPSHOT has been attached as
!karaf.log.gz!
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
> Attachments: karaf.log.gz
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steinar Bang updated KARAF-5174:
Attachment: karaf.log.gz
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
> Attachments: karaf.log.gz
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045234#comment-16045234
]
Steinar Bang edited comment on KARAF-5174 at 6/9/17 11:47 PM:
--
Uninstalling the liquibase-core feature doesn't crash and hang karaf
4.2.0-SNAPSHOT, but it looks like karaf does a quick restart.
I don't know if this is caused by the version of karaf or if it is caused by
the way karaf is started, or if it is caused by me already having a karaf 4.1.0
running on the same machine (that's why the port numbers are taken)?
Here's the output from an uninstall:
{noformat}
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
Exception in thread "JMX Connector Thread
[service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root]"
java.lang.RuntimeException:
Port already in use: 4;
You may have started two containers. If you need to start a second container
or the default ports are already in use update the config file
etc/org.apache.karaf.management.cfg and change the Registry Port and Server
Port to
unused ports
at
org.apache.karaf.management.ConnectorServerFactory.lambda$init$0(ConnectorServerFactory.java:267)
at java.lang.Thread.run(Thread.java:748)
Exception in thread "JMX Connector Thread
[service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root]"
java.lang.RuntimeException:
Port already in use: 4;
You may have started two containers. If you need to start a second container
or the default ports are already in use update the config file
etc/org.apache.karaf.management.cfg and change the Registry Port and Server
Port to unused ports
at
org.apache.karaf.management.ConnectorServerFactory.lambda$init$0(ConnectorServerFactory.java:267)
at java.lang.Thread.run(Thread.java:748)
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.0-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State │ Lvl │ Version│ Name
───┼┼─┼┼───
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
karaf@root()>
{noformat}
was (Author: s...@dod.no):
Uninstalling the feature in this manner doesn't crash and hang karaf
4.2.0-SNAPSHOT, but it looks like karaf does a quick restart.
I don't know if this is caused by the version of karaf or if it is caused by
the way karaf is started, or if it is caused by me already having a karaf 4.1.0
running on the same machine (that's why the port numbers are taken)?
Here's the output from an uninstall:
{noformat}
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
Exception in thread "JMX Connector Thread
[service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root]"
java.lang.RuntimeException:
Port already in use: 4;
You may have started two containers. If you need to start a second container
or the default ports are already in use update the config file
etc/org.apache.karaf.management.cfg and change the Registry Port and Server
Port to
unused ports
at
org.apache.karaf.management.ConnectorServerFactory.lambda$init$0(ConnectorServerFactory.java:267)
at java.lang.Thread.run(Thread.java:748)
Exception in thread "JMX Connector Thread
[service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root]"
java.lang.RuntimeException:
Port already in use: 4;
You may have started two containers. If you need to start a second container
or the default ports are already in use update the config file
etc/org.apache.karaf.management.cfg and change the Registry Port and Server
Port to unused ports
at
org.apache.karaf.management.ConnectorServerFactory.lambda$init$0(ConnectorServerFactory.java:267)
at java.lang.Thread.run(Thread.java:748)
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.0-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State │ Lvl │ Version│ Name
───┼┼─┼┼───
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
karaf@root()>
{noformat}
> Uninstalling feature using liquibase-slf4j crashes karaf
> ---
[jira] [Commented] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045234#comment-16045234
]
Steinar Bang commented on KARAF-5174:
-
Uninstalling the feature in this manner doesn't crash and hang karaf
4.2.0-SNAPSHOT, but it looks like karaf does a quick restart.
I don't know if this is caused by the version of karaf or if it is caused by
the way karaf is started, or if it is caused by me already having a karaf 4.1.0
running on the same machine (that's why the port numbers are taken)?
Here's the output from an uninstall:
{noformat}
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
Exception in thread "JMX Connector Thread
[service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root]"
java.lang.RuntimeException:
Port already in use: 4;
You may have started two containers. If you need to start a second container
or the default ports are already in use update the config file
etc/org.apache.karaf.management.cfg and change the Registry Port and Server
Port to
unused ports
at
org.apache.karaf.management.ConnectorServerFactory.lambda$init$0(ConnectorServerFactory.java:267)
at java.lang.Thread.run(Thread.java:748)
Exception in thread "JMX Connector Thread
[service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root]"
java.lang.RuntimeException:
Port already in use: 4;
You may have started two containers. If you need to start a second container
or the default ports are already in use update the config file
etc/org.apache.karaf.management.cfg and change the Registry Port and Server
Port to unused ports
at
org.apache.karaf.management.ConnectorServerFactory.lambda$init$0(ConnectorServerFactory.java:267)
at java.lang.Thread.run(Thread.java:748)
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.0-SNAPSHOT)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State │ Lvl │ Version│ Name
───┼┼─┼┼───
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
karaf@root()>
{noformat}
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045225#comment-16045225
]
Steinar Bang commented on KARAF-5174:
-
I just tried loading the feature on karaf 4.2.0-SNAPSHOT built from git, and it
loaded without any error messages.
The platform I tried on was debian 9 "stretch", with openjdk 8u131-b11-1.
Here's what I did:
# Cloned and built the feature
{noformat}
cd ~/git
git clone https://github.com/steinarb/liquibase-karaf-feature.git
cd liquibase-karaf-feature
mvn install
{noformat}
# Updated and built and started karaf
{noformat}
cd ~/git/karaf
mvn clean
git checkout master
git pull
mvn
cd assemblies/apache-karaf/target/assembly
bin/karaf
{noformat}
# Added the feature repository and installed the feature
{noformat}
karaf@root()> feature:repo-add
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
Adding feature url
mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
karaf@root()> feature:install liquibase-core
karaf@root()> bundle:list -t 35
START LEVEL 100 , List Threshold: 35
ID │ State│ Lvl │ Version│ Name
───┼──┼─┼┼──
28 │ Active │ 80 │ 4.2.0.SNAPSHOT │ Apache Karaf :: OSGi Services :: Event
52 │ Resolved │ 35 │ 2.0.0 │ liquibase-slf4j 2.0.0 made an OSGi
bundle fragment of org.l
53 │ Active │ 40 │ 3.5.3 │ Liquibase Core, Fragments: 52
54 │ Active │ 40 │ 1.17.0 │ SnakeYAML
karaf@root()>
{noformat}
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043908#comment-16043908
]
Steinar Bang commented on KARAF-5174:
-
I will try to figure out the missing artifacts.
Is there a downloadable tar.gz/zip of the 4.2.0-SNAPSHOT somewhere?
Or do I need to build from git?
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steinar Bang updated KARAF-5174:
Description:
To reproduce:
# clone this project and build it with maven:
{noformat}
mkdir -p ~/git
cd ~/git
git clone https://github.com/steinarb/liquibase-karaf-feature/
cd liquibase-karaf-feature
mvn clean install
{noformat}
# start karaf and give the following commands to the karaf console:
{noformat}
feature:repo-add mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
feature:install liquibase-core
{noformat}
# uninstall the feature
{noformat}
feature:uninstall liquibase-core
{noformat}
Karaf will now output the following and hang:
{noformat}
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
at org.apache.karaf.main.Main.doMonitor(Main.java:382)
at org.apache.karaf.main.Main.access$100(Main.java:75)
at org.apache.karaf.main.Main$3.run(Main.java:369)
{noformat}
On karaf 4.0.7 the crash on uninstall doesn't happen.
If the liquibase-slf4j fragment bundle is removed from the liquibase-core
feature, the crash on uninstall doesn't happen.
was:
To reproduce:
# clone this project and build it with maven:
{noformat}
mkdir -p ~/git
cd ~/git
git clone https://github.com/steinarb/liquibase-karaf-feature/
cd liquibase-karaf-feature
mvn clean install
{noformat}
# start karaf and give the following commands to the karaf console:
{noformat}
feature:repo-add mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
feature:install liquibase-core
{noformat}
# uninstall the feature
{noformat}
feature:uninstall liquibase-core
{noformat}
Karaf will no output the following and hang:
{noformat}
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
at org.apache.karaf.main.Main.doMonitor(Main.java:382)
at org.apache.karaf.main.Main.access$100(Main.java:75)
at org.apache.karaf.main.Main$3.run(Main.java:369)
{noformat}
On karaf 4.0.7 the crash on uninstall doesn't happen.
If the liquibase-slf4j fragment bundle is removed from the liquibase-core
feature, the crash on uninstall doesn't happen.
> Uninstalling feature using liquibase-slf4j crashes karaf
>
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5174) Uininstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033432#comment-16033432
]
Steinar Bang commented on KARAF-5174:
-
I've verified the crash on both Windows 7 64bit, and debian 8 "jessie"
GNU/linux.
Karaf 4.1.1 and Java 1.8 in both places. Windows has Oracle 1.8 jdk and debian
has openjdk 1.8 jdk.
> Uininstalling feature using liquibase-slf4j crashes karaf
> -
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will no output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5174) Uininstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033426#comment-16033426
]
Steinar Bang commented on KARAF-5174:
-
The karaf.log messages from installing and uninstalling the feature (and the
shutdown/crash) that follows, are:
{noformat}
2017-06-01T20:04:56,291 | INFO | pipe-feature:install liquibase-core |
FeaturesServiceImpl | 9 - org.apache.karaf.features.core - 4.1.1 |
Adding features: liquibase-core/[3.5.3,3.5.3]
2017-06-01T20:04:56,685 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Changes to perform:
2017-06-01T20:04:56,685 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Region: root
2017-06-01T20:04:56,685 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Bundles to install:
2017-06-01T20:04:56,686 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
mvn:no.priv.bang.ukelonn.rebundled/liquibase-slf4j-osgi/2.0.0
2017-06-01T20:04:56,686 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
mvn:org.liquibase/liquibase-core/3.5.3
2017-06-01T20:04:56,686 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
mvn:org.yaml/snakeyaml/1.17
2017-06-01T20:04:56,687 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Installing bundles:
2017-06-01T20:04:56,687 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
mvn:no.priv.bang.ukelonn.rebundled/liquibase-slf4j-osgi/2.0.0
2017-06-01T20:04:56,702 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
mvn:org.liquibase/liquibase-core/3.5.3
2017-06-01T20:04:56,730 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
mvn:org.yaml/snakeyaml/1.17
2017-06-01T20:04:56,790 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Starting bundles:
2017-06-01T20:04:56,791 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | org.yaml.snakeyaml/1.17.0
2017-06-01T20:04:56,795 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | org.liquibase.core/3.5.3
2017-06-01T20:04:56,802 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Done.
2017-06-01T20:05:06,666 | INFO | pipe-feature:install liquibase-core |
FeaturesServiceImpl | 9 - org.apache.karaf.features.core - 4.1.1 |
Removing features: feature:liquibase-core/[3.5.3,3.5.3]
2017-06-01T20:05:06,884 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Changes to perform:
2017-06-01T20:05:06,884 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Region: root
2017-06-01T20:05:06,885 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Bundles to uninstall:
2017-06-01T20:05:06,885 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
no.priv.bang.ukelonn.rebundled.liquibase-slf4j-osgi/2.0.0
2017-06-01T20:05:06,885 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
org.liquibase.core/3.5.3
2017-06-01T20:05:06,885 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
org.yaml.snakeyaml/1.17.0
2017-06-01T20:05:06,886 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Stopping bundles:
2017-06-01T20:05:06,886 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | org.yaml.snakeyaml/1.17.0
2017-06-01T20:05:06,887 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | org.liquibase.core/3.5.3
2017-06-01T20:05:06,888 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 | Uninstalling bundles:
2017-06-01T20:05:06,888 | INFO | pool-3-thread-1 | FeaturesServiceImpl
| 9 - org.apache.karaf.features.core - 4.1.1 |
no.priv.bang.ukelonn.rebundled.liquibase-slf4j-osgi/2.0.0
2017-06-01T20:05:06,897 | INFO | pool-3-thread-1 | FeaturesServiceIm
[jira] [Updated] (KARAF-5174) Uininstalling feature using liquibase-slf4j crashes karaf
[
https://issues.apache.org/jira/browse/KARAF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steinar Bang updated KARAF-5174:
Description:
To reproduce:
# clone this project and build it with maven:
{noformat}
mkdir -p ~/git
cd ~/git
git clone https://github.com/steinarb/liquibase-karaf-feature/
cd liquibase-karaf-feature
mvn clean install
{noformat}
# start karaf and give the following commands to the karaf console:
{noformat}
feature:repo-add mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
feature:install liquibase-core
{noformat}
# uninstall the feature
{noformat}
feature:uninstall liquibase-core
{noformat}
Karaf will no output the following and hang:
{noformat}
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
at org.apache.karaf.main.Main.doMonitor(Main.java:382)
at org.apache.karaf.main.Main.access$100(Main.java:75)
at org.apache.karaf.main.Main$3.run(Main.java:369)
{noformat}
On karaf 4.0.7 the crash on uninstall doesn't happen.
If the liquibase-slf4j fragment bundle is removed from the liquibase-core
feature, the crash on uninstall doesn't happen.
was:
To reproduce:
# clone this project and build it with maven:
{noformat}
mkdir -p ~/git
cd ~/git
git clone https://github.com/steinarb/liquibase-karaf-feature/
cd liquibase-karaf-feature
mvn clean install
{noformat}
# start karaf and give the following commands to the karaf console:
{noformat}
feature:repo-add mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
feature:install liquibase-core
{noformat}
# uninstall the feature
{noformat}
feature:install liquibase-core
{noformat}
Karaf will no output the following and hang:
{noformat}
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
at org.apache.karaf.main.Main.doMonitor(Main.java:382)
at org.apache.karaf.main.Main.access$100(Main.java:75)
at org.apache.karaf.main.Main$3.run(Main.java:369)
{noformat}
On karaf 4.0.7 the crash on uninstall doesn't happen.
If the liquibase-slf4j fragment bundle is removed from the liquibase-core
feature, the crash on uninstall doesn't happen.
> Uininstalling feature using liquibase-slf4j crashes karaf
> -
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
> GNU/linux 64bit
>Reporter: Steinar Bang
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will no output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core
> feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (KARAF-5174) Uininstalling feature using liquibase-slf4j crashes karaf
Steinar Bang created KARAF-5174:
---
Summary: Uininstalling feature using liquibase-slf4j crashes karaf
Key: KARAF-5174
URL: https://issues.apache.org/jira/browse/KARAF-5174
Project: Karaf
Issue Type: Bug
Affects Versions: 4.1.1
Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie"
GNU/linux 64bit
Reporter: Steinar Bang
To reproduce:
# clone this project and build it with maven:
{noformat}
mkdir -p ~/git
cd ~/git
git clone https://github.com/steinarb/liquibase-karaf-feature/
cd liquibase-karaf-feature
mvn clean install
{noformat}
# start karaf and give the following commands to the karaf console:
{noformat}
feature:repo-add mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
feature:install liquibase-core
{noformat}
# uninstall the feature
{noformat}
feature:install liquibase-core
{noformat}
Karaf will no output the following and hang:
{noformat}
karaf@root()> feature:install liquibase-core
karaf@root()> feature:uninstall liquibase-core
karaf@root()>
java.lang.IllegalStateException: No inital startlevel yet
at
org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
at
org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
at org.apache.karaf.main.Main.doMonitor(Main.java:382)
at org.apache.karaf.main.Main.access$100(Main.java:75)
at org.apache.karaf.main.Main$3.run(Main.java:369)
{noformat}
On karaf 4.0.7 the crash on uninstall doesn't happen.
If the liquibase-slf4j fragment bundle is removed from the liquibase-core
feature, the crash on uninstall doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
